Appendix B - CAD Detailed Requirements.xlsx
XLSX spreadsheet 177 KB Posted
- Attached to
- Cary Computer Aided Dispatch System Replacement 2025 State and local contract opportunity
- Solicitation number
- 354-PD25-34
- Issued by
- Wake County, Cleveland Town, North Carolina
About this file
This document is a detailed Computer Aided Dispatch (CAD) system requirements specification for the Town of Cary, North Carolina, covering its 9-1-1 Communications Center and multiple public safety agencies including police, fire, and emergency medical services. The document comprehensively outlines functional, non-functional, and technical requirements for a new CAD system, with a focus on replacing the existing system. The requirements are organized into multiple categories including administration, resource management, call handling, mapping and mobility, business support, and external interfaces. The specification provides extensive details on desired system capabilities, with requirements ranging from user interface configuration and resource deployment to security, messaging, and integration with multiple external systems.
The requirements specification indicates the system must support 100 concurrent users in the communications center and 600 concurrent mobile users, with an anticipated 1.5 million calls for service annually and potential 10% year-over-year growth. The system is expected to be cloud-compatible, geo-redundant, and maintain 99.999% availability with minimal service interruption. Key integration requirements include compatibility with existing systems such as Niche RMS, Intrado Vesta 9-1-1 telephony, Axon body cameras, Motorola Astro P25 radio systems, and various city databases and utility systems. The document emphasizes the need for robust security, multi-factor authentication, comprehensive audit logging, and the ability to support complex multi-jurisdictional emergency response scenarios.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| 354-PD25-34 Cary Computer Aided Dispatch System Replacement 2025.pdf | ||
| Q&A Addendum CAD Replacement Project 8May2025.pdf | ||
| Appendix A - Operational Use Cases.pptx | PPTX presentation | |
| Appendix C - CAD Technical Requirements Response .docx | DOCX document | |
| Appendix D - CAD Services Requirements Response Form.docx | DOCX document | |
| Appendix F - Bidder Cost Proposal Template.xlsx | XLSX spreadsheet | |
| Appendix E - CAD Interfaces List.docx | DOCX document | |
| Appendix G - Glossary of Terms.docx | DOCX document |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Introduction
Version 1.0
| Introduction |
| The purpose of this document is to describe the Town of Cary's requirements for a replacement Computer Aided Dispatch (CAD) system. This document contains the following components: |
| CAD Capabilities Summary: This worksheet contains a CAD Capabilities Context Model that summarizes the major areas of functionality the Town of Cary expects to receive from a new CAD solution. The functions within this model have been used to create the hierarchy of both the Functional Requirements, Non-Functional Requirements and External Interfaces (the three supporting worksheets within this document). It should be noted that the Town of Cary does not intend for this model to be prescriptive and limiting in nature. The Town of Cary is interested in considering any other functionality a solution may have to offer above this minimum threshold described in the model (or minimum viable product). |
| Functional Requirements: This worksheet contains the detailed Functional CAD Requirements (also often referred to as Business requirements), which describe the Town of Cary's expectations of the functional capabilities that will support the needs of its users and the Town of Cary 9-1-1 operation. Functional requirements describe what the Town of Cary expects the CAD can "do". |
| Non-Functional Requirements: This worksheet contains the detailed Non-Functional CAD Requirements (also often referred to as Technical requirements), which describe the Town of Cary's expectations of the technical capabilities of the CAD. Non-Functional requirements describe how the Town of Cary expects the CAD to "perform". |
| External Interfaces: This worksheet contains a discrete set of technical requirements, related to the Non-Functional Requirements, but specifically articulated to describe the Town of Cary's expectations of the new CAD system's interfacing capabilities with external systems and data sources. |
Computer Aided Dispatch Requirements CAD Replacement Project
Vendor Response Instructions
| Vendor Response Instructions and Legend |
| Proponents are to follow the instructions below. Insert the appropriate response code within the ‘Proponent Response’ column for each of the requirements within the 'Functional Requirements', 'Non-Functional Requirements' and 'External Interfaces' worksheets. |
Further to that:
| An omitted response will be assumed to be the same as a response code of “N”. |
| Only one (1) response per requirement will be accepted. Multiple responses will be re-coded at the discretion of the Town of Cary. |
| Any deviation from the response codes will be re-coded at the discretion of the Town of Cary. |
| Due to the large number of requirements, there exists a possibility of repeated, similar, or closely similar requirements. The evaluation score will be on all the responses to all entry including these possible duplicates. |
| Requirements are assigned a relative Prioritization: '1, 2 or 3' where 1 = Highest (Most Important to the Town of Cary), '3' is the lowest priority. |
Requirements are further categorized by 'Solution Type' as being assumed to be Cloud-only, On-Premise only or Common (to both)
| Response Code Options | Capabilities | Definition | Additional Notes | |
| Y | ||||
| (Yes - Out of the Box) | Functionality provided as standard. | The Proponent provides the functionality from its own code base (i.e., ‘out of the box’). No customizing, working around, or configuration is required to enable this functionality. | The functionality must be installed and operational at other sites and can be demonstrated to the Town of Cary. Functionality must not be forecast in a future release. | |
| G | ||||
| (Yes - via Configuration) | Functionality provided by the Proponent, but requires configuration. | The functionality can be accomplished with the Proponent’s product, with some configuration of the solution (e.g., the requirement will be met through configuration changes to settings of tables, switches, rules, user experience, etc. without modification or customization to the source code). | N/A | |
| C | ||||
| (Yes - via Customization) | Functionality provided by the Proponent, but requires customization. | The functionality can be accomplished with the Proponent’s products, with some custom code, customization or other non-configuration change is required. (e.g. including custom code developed to perform specific functions or validations outside the standard OOTB functionality, e.g. including the creation of a new report, query or workflow that does not exist within the current application OOTB as standard). | For this response option, you must indicate the following, in the comments column next to this response: | |
| - Description of customization | ||||
| - Party who will perform the work (Agency / Town of Cary or Proponent) | ||||
| - Estimated level of complexity (High, Medium, Low) | ||||
| - Any specific costs included within the Proponent's proposal for the customization(s) | ||||
| I | ||||
| (Yes - via Integration) | Functionality provided, but requires integration with third-party solution. | The Proponent has established a relationship (for example, as an OEM) with a business partner to provide this functionality, which is fully integrated (data, process, application) with the proposed solution. | For this response option, you must indicate the following, in the comments column next to this response: | |
| - Name of the proposed third-party software package | ||||
| - Interface / integration services being proposed, including if it requires customization or custom integration development. | ||||
| - If licensing and support is covered under your proposal. If not, the Proponent is to provide complete details. | ||||
| F | ||||
| (Future Release) | Functionality provided by the Proponent, but in a future release. | The functionality will be met with a particular feature that is in development. | For this response option in the comments column next to this response, you must indicate: | |
| A. Explanation of the new feature. | ||||
| B. Expected date that such a feature will be made available. | ||||
| C. If the feature will be included within the scope of this project. | ||||
| N | ||||
| (No - not supported) | Functionality not provided. | The Proponent's solution is unable to satisfy this requirement by any means. | Not even via configuration or custom development. |
CAD Capabilities Summary Cary's CAD System Capabilities Summary (Context Model )
Legend:
| Category Name |
| Capability / Functional Area Name |
Functional Requirements
| Category | Capability (Functional Area) | Req. ID | Requirements Descriptions | Priority | Solution Type | Proponent's Response | Proponent's Comments (for C, N and F response codes) | |
| Administration | UI Configuration Tools | Administration - 001 | The system shall enable users and agencies to easily configure the User Interface to meet individual or agency requirements. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 002 | The system shall provide the ability for the application to be viewed in a day and night mode. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 003 | The system shall provide the ability for the User to open new windows without restrictions on functionality for new windows. In addition the system shall allow the user to easily return to the specific fields such as address field, without multiple mouse clicks. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 004 | The system shall provide the ability for the Town of Cary to define its own visual and audible alerts (from a range of different alert type options) to notify field Units and other appropriate Dispatch and Records Management system Users of city defined activities and supplemental information. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 005 | The system shall provide the ability for the User to store User-specific customizations to the workstation environment, including font, font size, font color, window locations, display sort orders, tab orders and number of windows. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 006 | The system shall provide the ability for a Dispatcher the ability to change the dispatch community (Police, Fire, EMS) without moving to another physical location OR launching a separate CAD iteration (for example currently all live separate environments, to include Cary PD to Raleigh Wake EMS, Apex Fire, and Morrisville Fire or Cary, Apex and Morrisville PD by practice should open to a different CAD tabbed screen). (Note: Town of Cary 9-1-1 serves multiple agencies of each type - police, fire, and medical transfers). | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 007 | The system shall provide the ability for the Call Taker to choose to perform all of the functions of a Call Taker and Dispatcher or to transfer a call to a separate Dispatcher or bordering communications center PSAP for dispatching. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 008 | The system shall provide the ability for the Administrator to use predefined notes or quick notes (abbreviation that becomes a phrase or sentence) to enter information quickly. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 009 | The system shall provide the ability for the User to distinguish notes entered by other Users from their own, so the User can visualize an accurate description of how the Event was handled. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 010 | The system shall provide the ability for the User to easily distinguish high priority notes from lower routine notes so the User can air important information quickly. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 011 | The system shall provide the ability for the User to flag key information in Dispatch and Records Management system such as occupant in building, caution notes, previous calls so that it is easily seen and available. Alerts should auto-populate on the main dispatch screen, eliminating the need for additional clicks to view critical data. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 012 | The system functionality to allow data fields to be easily configured on the fly to collect data for special and/or temporary use cases . It is recommended that The system shall have up to 12 such configurable data fields. Examples of uses: 1 Alcohol Screening (MAS), Standardized Field Sobriety Testing (SFST). | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 013 | All records should have the ability to be classified as per CPD info security classification model and displayed where appropriate (on screen and on print). | 3 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 014 | The system provides a police Patrol Dashboard that at a minimum provides: 1) an overview of active and pending calls in the officer's work area, 2) a map displaying the location of all activities in the officer's general area 3) automatic and easily viewable real-time information updates on the call(s) an officer is currently dispatched to, 4) buttons/shortcuts for commonly performed functions (e.g. messaging, stops, enroute, arrive), 5) Traffic / Subject stop self-dispatching button, self dispatch button should be available but NOT in use, but should be configurable for each agency needs. 6) LEADS (Law Enforcement Automated Data System) NCIC capability to remotely run subject, license plate, or property information) AVL response navigation. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 015 | The system should provide a police Supervisor Dashboard that at a minimum provides: 1) an overview of active and pending calls in your work area, 2) a map displaying the location of all officers and the status of each unit, 3) ability to easily see active units and dispatchers and obtain contact info / message units 4) buttons/shortcuts to common supervisory functions. | 3 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 016 | Whiteboard (Sharable Media) | |||||
| A sharable whiteboard (Media) on a new CAD system would be beneficial. The ability to share intelligence (house diagrams, layouts etc.) on high-risk calls would be invaluable. The ability to share photos of buildings and access doors to other members on the call. This intelligence gap helps commanders make decisions on tactical considerations during high-risk calls. This information should be shared through the call in the CAD system so that all units on the scene can see the same information. | 3 | Common | Please Select a Response | |||||
| Administration | UI Configuration Tools | Administration - 017 | The system shall capture and display all the important times from all units associated with the call, such as Dispatch time, enroute time, on-scene time, transport times, status changes, required on-scene situational times, address changes, and Clearance of unit's time. This information should be displayed in an easily digestable manner for analytical purposes | 3 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 018 | The system shall include "Back and Forward Button" to navigate back and forth between previously viewed information. | 3 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 019 | The system shall include "Split Screen Operation". The system shall show live map and the call screen at the same time. These two screens must auto update and provide adequate functionality to manipulate and operate on both screens in real time. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 020 | NCIC | |||||
| When conducting NCIC inquiries, have an intuitive and filterable window. The system should allow police officers to search previously completed database queries (e.g., NCIC/CCH) by name, time of query, etc. | 1 | Common | Please Select a Response | |||||
| Administration | UI Configuration Tools | Administration - 021 | The system shall provide the ability for the User to run a report using dates in an annual calendar, including an ability to run a report on future date. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 022 | The system shall display ETA for from all units associated with the call, including partner agencies. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 023 | The system shall have the ability to filter messages based on source. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 024 | The system shall have the ability to provide multiple views: Event information view, Map information view; and screen split with both views. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 025 | The system shall provide the standard touch/zoom gestures. | 1 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 026 | The system shall have Spell Check feature. | 3 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 027 | ||||||
| The system shall have the ability to manage a single login across all devices associated with the Unit ID/Apparatus ID; i.e.. MDT and Mobile App. | 3 | Common | Please Select a Response | |||||
| Administration | UI Configuration Tools | Administration - 028 | The system shall have a test (UAT) environment that mirrors the production environment with no*********. The test environment should be automatically updated with any information entered into the production envirnment and visa versa. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 029 | The system shall allow the user to correct typing errors in the remarks field prior to the event being accepted. | 3 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 030 | The system shall allow the user to enter a command into the command line using either uppercase or lowercase letters. | 2 | Common | Please Select a Response | ||
| Administration | UI Configuration Tools | Administration - 031 | The system shall allow the command line to save all entries, even those which generated an error message due to user mistakes. Command line entries should be searchable from a historical perspective for that user until they log out for the day. | 2 | Common | Please Select a Response | ||
| Administration | Security | Administration - 032 | The system shall adhere to local and regional compliance (Specific compliance list provided in the RFP). | 1 | Common | Please Select a Response | ||
| Administration | Security | Administration - 033 | The system should support multi factor authentication (MFA). | 1 | Common | Please Select a Response | ||
| Administration | Security | Administration - 034 | The system should support role based access control (RBAC). | 2 | Common | Please Select a Response | ||
| Administration | Security | Administration - 035 | The system shall provide the ability to store a log of all personnel who have printed, accessed, or viewed certain reports or executed certain queries. | 1 | Common | Please Select a Response | ||
| Administration | Security | Administration - 036 | The system shall provide the ability to compartmentalize data based on role, agency, or other criteria. The data should be extractable relevant to reporting and compliance requirements. | 2 | Common | Please Select a Response | ||
| Administration | Security | Administration - 037 | The system shall demonstrate the ability to handle multiple ORIs. | 1 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 038 | The system shall enable enhanced incident and event logging with GPS replay. | 1 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 039 | The system's audit and event logging shall interface with other systems such as audio and video recording systems. | 1 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 040 | The system shall provide the ability for each agency to configure individual 1) event types 2) event subtypes 3) out-of-service codes 4) unit/call signs 5) mapping boundaries (geocodes, districts, zones, wards) 6) Commonplace names 7) disposition codes 8) event flags 9) officer/firefighter safety timers 10) unit statuses 11) officer skills or specific teams 12) officer/firefighter equipment 13) address based alerts/flags 14) types of units/apparatus 15) hydrant serviceability, 16) Traffic response restrictions. | 2 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 041 | The system shall provide the ability to automatically record the Date/Time and User ID when any searches are performed against external data sources. | 2 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 042 | The system shall provide the ability to automatically acknowledge that an update to an Event record was completed. | 2 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 043 | The system shall provide the ability to automatically prompt when a User is about to lose any unsaved data by performing an action (e.g., when logging out of the system without closing an Event record correctly). The system shall maintain an Administrative recovery option based upon an unintended action. | 2 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 044 | The system shall provide the ability for the User, with the right permission to see who has made changes to any of the configuration files through an audit trail. | 2 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 045 | The system shall provide the ability for the User to attach the results of a query to an external system to any report or record within the system and an ability to export the results of a query. | 1 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 046 | The system shall provide the ability to automatically send reminders for any maintenance that must be performed (e.g., such as purging or backing up data). | 2 | Common | Please Select a Response | ||
| Administration | System/Event Logging | Administration - 047 | The system shall provide the ability to run updates at sign-in. | 1 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 048 | The system shall provide the ability to automatically utilize a Master Time Clock that utilizes Network Time Protocol (NTP) to synchronize time throughout all system components. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 049 | The system shall provide the ability to concurrently enter Events both manually and automatically without system degradation. | 1 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 050 | The system shall provide the ability for all information to be entered without any restrictions, and times/dates changed to reflect the actual time that notice of the CFS (Call for service) event was received. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 051 | The system shall be able to automatically synchronize Event numbers and mobile-initiated calls for service with the Records Management system Incident records. This synchronization should occur regardless of RMS system | 1 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 052 | The system security features should provide ability to compartmentalize data based on role, agency or other criteria. | 1 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 053 | The system shall provide the ability to automatically assign unique sequential IDs for each Event record created. IDs must be configurable by agency and ID parameters must be able to be reconfigured (e.g. addition of prefix, change in string length). | 1 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 054 | The system shall provide the ability for the User to supplement a closed Event without requiring that the state/status of the Event be changed. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 055 | The system shall provide the ability for the User to run a report on preventative maintenance that has been performed on the system. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 056 | The system shall provide the ability to denote the manually-entered Event, so there is a record that the CFS event was not entered when it was received. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 057 | The system shall provide the ability to log the Event creation time and creator of manual event records. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 058 | The system shall provide the ability to automatically denote that an Event record was created automatically. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 059 | The system shall provide the ability for the User to manually select the first Event number when restarting after an outage. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 060 | The system shall provide the ability to restrict the User from closing an Event record without first entering an Event Source, location, or Event type code. | 2 | Common | Please Select a Response | ||
| Administration | CAD Catch-up/Sync | Administration - 061 | The system shall have the ability to have different user lists, i.e.. active vs inactive staff/users. | 3 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 001 | The system shall provide the ability for the User to manage and automate the scheduling of Units for designated periods of time (e.g., two breaks per shift). | 3 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 002 | The system shall provide the ability for the User to define multiple deployment and response plans within agency and patrol areas. | 2 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 003 | The system shall provide the ability for the User to define an unlimited number of posts, core stations, etc. (e.g., static locations to where resources may be assigned/staged). | 2 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 004 | The system shall provide ability for the User to assign resources to locations on a temporary basis (e.g., due to flooding, road closures, etc.) and for unlimited time frames. | 2 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 005 | The system shall be able to provide an unlimited list of resources by incident (personnel, assigned apparatus, unit ID, equipment). | 1 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 006 | The system shall provide an Incident Management system. | 1 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 007 | The system shall provide the ability to search equipment, personnel and skill sets. | 1 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 008 | The system shall provide an advanced search option, by address, business/personnel name, time, date, phone number, involved names / vehicles etc. All data fields should be searchable either on their own or in combination. and provide auto-complete search suggestions. | 1 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 009 | The system shall have the capability to provide situational data related to the incident location, including details about the structure, such as wither it is residential, commercial, a family dwelling, or involves a suppressed infrastructure. | 2 | Common | Please Select a Response | ||
| Resource Management | Deployment Planning | Resource Management - 010 | The system shall be able to provide an apparatus equipment report of all equipment when selecting a specific unit. | 2 | Common | Please Select a Response | ||
| Resource Management | Move Ups | Resource Management - 011 | The system shall provide the ability for the User to be alerted by the system to move Units to other locations (Auto Move-Ups) for coverage during Events when resources are down to a minimum level. | 1 | Common | Please Select a Response | ||
| Resource Management | Move Ups | Resource Management - 012 | The system shall provide the ability for the User to get audible or visual alerts when staffing changes are due, including when a person's shift has ended but the person is still showing as on duty. | 1 | Common | Please Select a Response | ||
| Resource Management | Move Ups | Resource Management - 013 | The system shall provide the ability for the User to recognize resource gaps that will likely result in response performance under prescribed standards. | 1 | Common | Please Select a Response | ||
| Resource Management | Move Ups | Resource Management - 014 | The system shall allow the User to change/move a new or existing piece of equipment or substitutions, which may have the same or different capabilities from an alternative unit or location. | 2 | Common | Please Select a Response | ||
| Resource Management | Move Ups | Resource Management - 015 | The system shall provide the ability for the User to provide a visual indicator when a priority post needs a resource. | 1 | Common | Please Select a Response | ||
| Resource Management | Move Ups | Resource Management - 016 | The system shall provide the ability for the User to track, retain, search and report all history of move ups for each Unit. | 2 | Common | Please Select a Response | ||
| Resource Management | Roster / Scheduling | Resource Management - 017 | The system shall provide the ability for the User to upload multiple new Units to the system in a batch. | 2 | Common | Please Select a Response | ||
| Resource Management | Roster / Scheduling | Resource Management - 018 | The system shall provide the ability for the User to load resource scheduling information. | 1 | Common | Please Select a Response | ||
| Resource Management | Roster / Scheduling | Resource Management - 019 | The system shall provide the ability for the User to generate and print an overall personnel roster containing any city/municipality defined information associated with personnel. | 1 | Common | Please Select a Response | ||
| Resource Management | Roster / Scheduling | Resource Management - 020 | The system shall provide the ability for the User to define when scheduled resources should be logged on/off, with an alert to the Field Supervisor or a Dispatcher if resources that are supposed to be logged on/off have not done so within a defined timeframe. | 2 | Common | Please Select a Response | ||
| Resource Management | Roster / Scheduling | Resource Management - 021 | The system shall provide the ability for the User to search for and retrieve information about personnel assigned to a particular Unit using one or more search criteria (e.g., personal name or ID, capabilities, Unit type, Event type, Units assigned, date/time, location, etc.). | 1 | Common | Please Select a Response | ||
| Resource Management | Roster / Scheduling | Resource Management - 022 | The system shall provide the ability for the User to enter and maintain Unit equipment and personal information and make changes as needed throughout a shift (e.g., personnel assigned, vehicle numbers, equipment numbers, etc.). | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 023 | The system shall provide the ability for the User to distinguish Unit types by personnel or call sign to ensure the appropriate Units are dispatched based on type of Event and response. | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 024 | The system shall provide the ability for the User to determine the quantity and type of Units required, and will recommend multiple Units, including from other partner agencies, to an Event, when appropriate. | 1 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 025 | The system shall provide the ability for the User to view which Units will be recommended should a call escalate from the current type to a different type or priority level. | 1 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 026 | The system shall provide the ability for the User to redirect assigned resources to a new higher priority Event based on defined criteria and based on ana indivudual resource availability. | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 027 | The system shall provide the ability for the User to see special or different Unit recommendations for the same type code based on location or area and the need for additional / different resources. | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 028 | The CAD system shall provide the ability to create new Unit recommendations based on a change in Units' statuses (e.g., a Unit closer to an emergency has become available or an individual's availability). | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 029 | The system shall provide the ability to interrupt non-emergency status or interrupt select out of service codes depending on severity of call typ | 1 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 030 | The system shall take drive time and access into consideration when making equipment recommendations for freeway or rural responses. | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 031 | When an officer activates an officer in need of immediate assistance alert, the current GPS location of the unit is displayed and transmitted to dispatch regardless of whether or not an officer is currently assigned to a call for service. | 1 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 032 | The system shall have a Keyword Voice Activation feature These functions would include reading of NCIC results (indicate if a person is wanted or vehicle is stolen), reading of critical details of a call for service ex. Suspect description. The ability to run plates or people using text-to-speech technology while driving would enhance officer and public safety by keeping officers' eyes on the road. | 2 | Common | Please Select a Response | ||
| Resource Management | Resource Recommendations | Resource Management - 033 | The system shall have the ability to manually alter or change response coding for specific incidents. (i.e. accident types and apparatus needed). | 2 | ||||
| Resource Management | Resource Recommendations | Resource Management - 034 | The system shall have a Self-Generating Calls feature. This functionality would have to be conducted pursuant to policy created around this capability to ensure officer safety. | 2 | Common | Please Select a Response | ||
| Resource Management | Personnel Qualifications | Resource Management - 035 | The system shall provide the ability to automatically send an alert when a Unit has inadequate personnel whether in numbers or skill set qualifications. | 1 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 036 | The system shall provide the ability for the system to incorporate Unit certifications and skills when making resource recommendations. | 2 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 037 | The system shall provide the ability for the User to create a multi-jurisdictional response, and shall allow a User to forward/copy the Event record without having to re-enter the Event information for the partnering agency. Each agency should have access to active mapping that allows them to view available and responding units during multi-agency responses | 2 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 038 | The system shall provide the ability for the User to create a linked Event record (using defined parameters) for each required agency and route the Event record to the appropriate dispatch positions when an Event involves more than one agency Event(s). | 3 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 039 | The system shall provide the ability for the User to create Event records with a single entry for each jurisdiction responding to a multi-jurisdiction Event. | 2 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 040 | The system shall be able to create run card assignments of multifunctional responses based on apparatus capability. (i.e. Quint Unit) | 2 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 041 | The system shall provide the ability for the User to transfer an active Event record to another agency without closing the Event record within the originating agency. | 2 | Common | Please Select a Response | ||
| Resource Management | Multi-Jurisdiction Operations | Resource Management - 042 | The system shall provide the ability for the User to dispatch Units from multiple jurisdictions to respond to a single Event. This needs to be able to happen without a new call for service being generated for the assisting agency if they are from another neighboring jurisdiction | 2 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 043 | The CAD system shall provide the ability to define multiple mutual aid and automatic aid agreements with agreement-specific business rules for utilization and various levels of response for each agreement. | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 044 | MFA authentication capability is a requirement, and specific agency may require an exception. Please list MFA options, single sign on options and list which Identity Providers (IDP) your solution supports (e.g. Microsoft, Google, etc.). | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 045 | The system shall provide the ability to display and track the status of mutual aid and automatic aid partner agency Units on full situational awareness. | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 046 | The system shall provide the ability to support the NENA Emergency Incident Document Object (EIDO) and its conveyance. | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 047 | The vendor shall share their roadmap for support of applicable NENA i3 standards and functional elements such as IDX, EIDO, ADR (Additional Data Repository) and IS-ADR (Identity Searchable Additional Data Repository) and i3 Logging Service. | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 048 | The system shall support the use of digital certificates from the PCA (PSAP credentialing agency) to represent the identity of the PSAP, CAD Equipment and/or CAD operator. | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 049 | The system shall provide the ability for the User to recognize the resources, capabilities, and location of each agency’s Units when generating dispatch recommendations for Event within mutual aid and automatic aid jurisdictions. | 1 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 050 | The system shall provide the ability for the User to make cross staffed units unavailable when one of the two units is in service. | 2 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 051 | The system shall provide the ability to incorporate estimated drive time into closest unit recommendation. This also needs to include shoot times from the stations and to be able to have that calculate based on the data from the system of shoot time history. This also needs to take into account and have the ability for units to place themselves out inspecting, house to house hydrants and base that recommendation on the shoot times. | 2 | Common | Please Select a Response | ||
| Resource Management | Auto Aid / Mutual Aid | Resource Management - 052 | The CAD system shall provide the ability to support the Joint NENA/APCO Emergency Event Data Document (EIDD) or similar CAD-to-CAD functionality for Event information as required by mutual aid agreements. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Rotation | Resource Management - 053 | The system shall provide the ability for the User to make personnel changes to Units without having to take the Unit out of service (e.g., move a person from one Unit to another or remove an individual from a unit). | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Rotation | Resource Management - 054 | The system shall provide the ability for the User to select the next Unit in the rotation list regardless of supplemental Unit's ability to respond to the request. | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Rotation | Resource Management - 055 | The system shall provide the ability for the User to replace a Unit at the top of the rotation list when the User cancels the request (e.g., through no fault of the supplemental Unit). | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 056 | The system shall provide the ability for the User to view information regarding a Unit, including but not limited to: agency, Unit beat, district, division, name, Unit ID/call sign, special note or comments, special notes, specials skills, Unit type, current location, current assigned call(s), current status, and elapsed time in status. | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 057 | The CAD system shall provide the ability for the User to set up zones and track which Units are in each zone at all times. Command units, organized by discipline, should have the capability to view all units within each designated response zone. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 058 | The system shall provide the ability for the User to initiate status changes via multiple methods, including but not limited to: command line, function key, map, selecting an icon or other operation from the User interface. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 059 | The system shall provide the ability for the User to know whether a Unit is moving or not within a designated timeframe (e.g., 30 seconds) after Unit responds as being “en route”. This system should also be have auto enrive and auto arrive funcitonality. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 060 | The system shall provide the ability for the User to view the schedule and location for all personnel. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 061 | The system shall allow the User to drill down on Unit detail by jurisdictional/agency-defined criteria (e.g., resource, and time of day). | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 062 | The system shall provide the ability to automatically assign a default availability based on status (e.g., Unit available when in particular status). | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 063 | The system shall provide the ability for the User to place a roster of Units on-duty with Units remaining unavailable or not recommended for calls until they notify the user that they are in service. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 064 | The system shall provide the ability for the User to modify a Unit's availability regardless of status (e.g., on-scene, but available). | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 065 | The system shall provide the ability for the User to modify the status of multiple Units at the same time. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 066 | The system shall provide the ability for the User to associate personnel with any mobile Unit (e.g., vehicle, apparatus, bicycle, etc.). | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 067 | The system shall provide the ability for the User to associate Units with the Event for as long as they are at the Event. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 068 | The system shall provide the ability for the User to associate multiple individuals with a Unit. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 069 | The system shall provide the ability for the User to track the activity of a field Unit by Unit ID. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 070 | The system shall allow for the automatic tracking of times for each Unit/Individual assigned to a given Event separately. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 071 | The system shall provide the ability to automatically calculate the duration of the assignment when a Unit is assigned to an Event. | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 072 | The system shall provide the ability for the User to make a Unit available for only certain types of calls. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 073 | The system shall provide the ability to automatically identify field Units who have cleared for other activities. | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 074 | The system shall enable individual tracking through various mobile devices, such as body-worn cameras, smartphones, and smart dog collars. | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 075 | The system shall provide the ability for the User to log apparatus/equipment into service without tying it to an individual. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 076 | The system shall provide the ability for the User to keep vehicles on duty (e.g., 24x7) and change personnel associated with the vehicles (e.g., on shift changes). | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 077 | The system shall provide the ability to automatically track Units waived off and their arrival times. | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 078 | The system shall provide the ability to calculate response times from the time of dispatch to on-scene arrival times and using pre-determined response times, notification should be sent to the user that the response time has exceeded i.e. 7:59 required time, 8:00 still not on scene notification should be sent. (Logging is required where there are instances of response times exceeding predefined limits. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 079 | The system shall provide an incident timer that will start after the first unit arrives on the scene of an incident or notification given by command, and after an agency-defined amount of time, i.e. 10 minutes, send an urgent message to the CAD User that the timer has expired and document the incident with the urgent message information (as defined by the agency) and can be canceled/stopped by the CAD User with a user-defined command, i.e. "C4 or OK". | 1 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 080 | The system shall provide the User the ability to turn off or reset all timers for a single, multiple, or all units, related to a single incident in a single command. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 081 | The system shall provide the ability to provide an active window to display units whose timers have expired, once the timers are reset, the units should disappear from this active window. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 082 | The system shall provide the User the ability to set or cancel all timers associated with an incident, if necessary, with a single action or command. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 083 | The system shall provide the ability to record all incident and unit timers, including tracking times, separately for the primary and all secondary units assigned to a call. | 3 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 084 | The system shall provide the ability for Incident timers to have priority over unit timers. | 3 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 085 | The system shall provide Users the ability to start and stop the timer for an incident, without limit, for the duration of the incident. The amount of time should be adjustable based on the incident type and have the default value set by the agency. Users need to have the ability to adjust the time on the fly, based on the current situation. I.e., a default value of 10 minutes for a police or fire incident is acceptable; but if there is a weapon involved or extrication, 5 minutes may be more appropriate. In the later stages of the incident, 20 minutes, or longer, may be desired. | 2 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 086 | The system shall provide a dynamic display for the incident timer. I.e., a digital clock that counts down and expires at zero. | 3 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 087 | The system shall provide the ability for the User to configure the timer to being initiated automatically, based on incident type, or manually by a user. | 3 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 088 | The system shall provide the ability of the text of the message to be configurable by the agency and, include the elapsed time since the first unit arrived on scene. | 3 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 089 | The system shall provide the ability to provide a fully user-configurable status table for both units and incident related statuses. | 3 | Common | Please Select a Response | ||
| Resource Management | Unit Status / Updates | Resource Management - 090 | The system shall provide the ability for Users on Dispatch workstations and/or MDTs to assign a status to a unit or incident by use of hot keys, mouse, or use of a command line function to complete each of the defined statuses. Specific Requirements for a few status changes are defined below. | 1 | Common | Please Select a Response |
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 .