RFP NSP7149 Z1 Tyler Technologies File 4 of 5 (2).xlsx
XLSX spreadsheet 312 KB Posted
- Solicitation number
- NSP7149 Z1
- Issued by
- Blaine County, Nebraska
About this file
This document is a Tyler Technologies Exhibit A comprehensive compliance matrix for a Computer Aided Dispatch (CAD) system Request for Proposal (RFP) issued by the Nebraska State Patrol (NSP) for RFP Number NSP7149 Z1. The proposal covers a statewide CAD solution designed to support multiple dispatch centers with advanced technological capabilities including real-time incident dispatching, unit status tracking, mapping, routing, reporting, and system administration. The contract term is five years with the option to renew for five additional one-year periods, and requires conversion of seven years of historical incident and premise data from the existing legacy system. The solution must integrate with over 20 existing interfaces and comply with NENA NG-911 standards, supporting approximately 350 mobile users across multiple communication centers.
The evaluation process for this procurement includes 100 points (potentially 120 with interviews), with 25 points for Corporate Overview, 65 points for Technical Approach, and 10 points for Cost Proposal. While specific budget ranges are not disclosed, the proposal requires comprehensive pricing covering software subscriptions, interface software, professional services, and third-party integrations. The system must seamlessly integrate with existing infrastructure including the Niche Records Management System, Motorola APX Next System, and various state and national databases. Seven vendors have submitted bids, including Tyler Technologies, ProPhoenix Corporation, SmartCOP, Inc., Motorola Solutions, Inc., 10-8 Systems LLC, Central Square, and 22nd Century Technologies. Proposals are due on July 22, 2024, at 2:00 PM Central Time, with the state reserving the right to contract for similar services from other sources.
View the file
Other files
Show 40 more
Latest 50 of 102 listed here. See the rest on GovTribe.
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
CAD
| Tyler Technologies | ||||||
| Exhibit A | ||||||
| Item Number | Module/Description of Requirement | Currently Complies | Does not Comply | Partially Comply | Will Comply | Comments |
| General CAD Requirements | ||||||
| 1.00 | The solution should have the ability to support a statewide CAD environment with multiple dispatch centers | X | Communications Centers can easily set up Enterprise CAD based on the responsibilities of their personnel and their unique operational requirements. The application suite can be configured to support any combination of call taker, dispatcher, area and responding disciplines. | |||
| 2.00 | The solution should have the ability to support dispatch centers on the same CAD instance that operate in different time zones, and maintains accurate time stamps for all CAD and mobile activity | X | The CAD system uses Universal Time Code (UTC). All times are stored on the CAD server in UTC and time zone conversions for display are handled within the CAD client. The CAD system will display the correct time to each CAD user according to the time zone offset for their location. All call activity is date and time stamped and available for viewing in the Call and Unit Logs. | |||
| 3.00 | The solution should have the ability to support and dispatch for multiple agencies simultaneously | X | The proposed solution was designed from the start to support multi-agency operations. CAD can operate with one CFS controlling all agencies (and the associated incident numbers) or with multiple CFS based on the agency or discipline. | |||
| 4.00 | The solution should have the ability to comply and maintain compliance with published NENA NG-911 standards | X | Tyler takes an active role in the ongoing development of NG911 standards. As NG911 standards continue to evolve and expand, Tyler will update our solutions to meet all relevant requirements. | |||
| 5.00 | The solution should have the ability to dispatch only law units from a specific Troop area from a single CAD window (the ability to filter out other agencies from non-relevant unit recommendations) | X | Tyler's proposed solution supports configurable user workspaces based on individual or template configuration. The layout of CAD is driven completely by the agency to include which windows/screens display, where they display, how those windows are configured (grid/filters/sort/column order), etc. This will allow filtering to dispatch law units only from specific troops. | |||
| 6.00 | The solution should have the ability to capture all CAD transactions in an audit log | X | The Logs tab of the CFS window records information about the entry and editing of all CFS data. The system also logs all unit activity such as status changes, location entries, and timers. Administrative activity undertaken in the CAD module is logged in the Maintenance application. | |||
| 7.00 | The solution should have the ability to support multiple monitors | X | Tyler's proposed solution supports multiple monitors. | |||
| 8.00 | The solution should allow for agency administrators to set a default profile using multiple windows and monitors that are accessible by all users | X | Tyler Enterprise CAD uses templates. Templates allow users and/or administrators to save specific user workspace configurations, so they do not need to set them up every time the application is launched. Templates can be shared across the system, so dispatch can have separate call taker and dispatcher templates or police and fire dispatch templates, etc. | |||
| 9.00 | The solution should allow users with appropriate permissions to set multiple profiles using multiple monitors and windows that can be saved and shared with other users | X | Tyler Enterprise CAD uses templates. Templates allow users and/or administrators to save specific user workspace configurations, so they do not need to set them up every time the application is launched. Templates can be shared across the system, so dispatch can have separate call taker and dispatcher templates or police and fire dispatch templates, etc. | |||
| 10.00 | The solution should have the ability for the system to automatically generate a case/incident number from the Niche RMS application | X | Tyler's proposal includes a custom CFS export to send CFS data to Niche RMS. This will facilitate case/incident number generation. | |||
| 11.00 | The solution should have the ability for each agency to have a unique identifier regarding incident numbers | X | Tyler Enterprise CAD uses Call For Service numbers and CFS Types to create and manage calls. Each individual agency on the system can have their own unique incident number and Incident Type based upon the original call. | |||
| 12.00 | The solution should have the ability to support remote access to the CAD (e.g., via VPN or other secure connection) | X | Tyler's proposed solution supports remote access via standard methods provided by the agency's IT department. | |||
| 13.00 | The solution should have the ability to perform the following via remote access: | -- | -- | -- | -- | -- |
| 13.01 | Monitor and create calls | X | Tyler's proposed solution supports full CAD function during a remote access session. | |||
| 13.02 | Monitor units and unit statuses | X | Tyler's proposed solution supports full CAD function during a remote access session. | |||
| 13.03 | Create and dispatch calls | X | Tyler's proposed solution supports full CAD function during a remote access session. | |||
| 13.04 | Run queries | X | Tyler's proposed solution supports full CAD function during a remote access session. | |||
| 14.00 | The solution should include an "offline" mode so users may continue to perform basic CAD functions if network connectivity is lost | X | Tyler’s Enterprise CAD application provides offline call entry functionality as part of the base solution. The CAD client can operate in “stand-alone” mode wherein an individual workstation operates as an independent CAD system. | |||
| 15.00 | The system should include a "back up" or "catch up" mode to allow users to input CAD information following a CAD system outage | X | Call information entered while offline is automatically queued up for supervisor approval. When the client can connect again to the server, the CFS information approved by the supervisor updates the system automatically. | |||
| Application User Interface | ||||||
| 16.00 | The solution should have the ability to configure the graphical user interface at the following levels: | -- | -- | -- | -- | -- |
| 16.01 | User | X | Templates can be configured and saved at the user level. | |||
| 16.02 | PSAP | X | Templates can be configured and saved at the PSAP level. | |||
| 16.03 | Agency | X | Templates can be configured and saved at the agency level. | |||
| 17.00 | The solution should have the ability to customize the following, including but not limited to: (If certain features are customizable at only the user or agency level, indicate as such in the "Comments" field) | -- | -- | -- | -- | -- |
| 17.01 | Font types, sizes and colors | X | Enterprise CAD has adjustable font sizes for certain functions and features, such as the call for service narrative. A font size picker can be accessed via the settings button on the narrative field. The font can be adjusted by the user. Font colors and types are not user adjustable. | |||
| 17.02 | Window background color, sizes, and locations | X | Users have the ability to rearrange the windows of the Dispatch Client interface. Users have several methods at their disposal to arrange the windows in their workspace, such as floating, dockable, or tabbed view. Window background color customization is not supported. | |||
| 17.03 | The order in which fields are displayed | X | The CAD layout is driven completely by individual agencies to include which windows/screens display, where they display, and how those windows are configured (grid/filters/sort/column order), etc. | |||
| 17.04 | The ability to configure field names for display (e.g., "Troop Area" instead of "Beat", etc). | X | CAD call entry and State/NCIC have configurable entry screens where the administrator can select from an existing “pool” of data elements and add/configure field labels. | |||
| 18.00 | The solution should have the ability for administrators to define which options are configurable by the user | X | The proposed solution does not support this functionality. | |||
| 19.00 | The solution should have the ability for administrators to define fields that are required to display in status windows | X | Administrators can configure templates for use by individual users. | |||
| 20.00 | The solution should have the ability for user to enlarge and shrink columns in their status windows | X | The sort and filter functions allow users to customize their views within grids and lists. | |||
| 21.00 | The solution should allow users to detach, move, and resize all windows | X | Users have the ability to rearrange the windows of the Dispatch Client interface. Users have several methods at their disposal to arrange the windows in their workspace, such as floating, dockable, or tabbed view. | |||
| 22.00 | The solution should have the ability to save CAD layout configurations based on user IDs (e.g., not workstation-specific) | X | Templates allow users to save specific user workspace configurations to their user profile, so they do not need to set them up every time they launch the application. Once a user sets up the windows of the application a certain way, that setup can be saved for use each time the application is launched. | |||
| 23.00 | The solution should have the ability to reset their current layout configuration to default settings | X | Administrators can configure "Default" templates. If needed, a user can simply select the appropriate template to change the CAD layout across one or multiple monitors. | |||
| 24.00 | The solution should have the ability to maintain configuration settings during upgrades (user screen templates and layouts are not lost after software upgrades) | X | All application configuration and settings are preserved with any Tyler update. | |||
| 25.00 | The solution should have the ability to support MS Windows functionality, including but not limited to: | -- | -- | -- | -- | -- |
| 25.01 | Minimize/maximize windows | X | The system supports the ability to minimize/maximize windows as desired. | |||
| 25.02 | The ability to have multiple windows open simultaneously | X | The system supports the ability to have multiple windows open at the same time. | |||
| 25.03 | Tile/cascade windows | X | The system supports the ability to rearrange windows as desired. | |||
| 26.00 | The solution should have the ability to display system messages without affecting a user's work in progress | X | Messages and notifications are designed to display in such a way that progress is not interrupted. | |||
| 27.00 | The solution should have the ability to display multiple call windows simultaneously, allowing for each to be configured differently (if desired by the user) | X | Users can open more than one call window and configure each differently (i.e., list displays, sort/filter, etc.). | |||
| 28.00 | The solution should have the ability to display multiple unit status windows simultaneously | X | Users can display more than one unit status window at a time. | |||
| 29.00 | The solution should allow for users to configure each unit status window uniquely (e.g., sorting, filtering, choosing which desired columns to view) | X | Each window can be configured differently based on user preference and workflow needs. | |||
| General Data Entry | ||||||
| 30.00 | The solution should have the ability to support data entry via: | -- | -- | -- | -- | -- |
| 30.01 | Mouse and Keyboard if required | X | Data entry via mouse and keyboard is supported. | |||
| 30.02 | Command line entry | X | Data entry via command line is supported, as well as the ability to open multiple command lines simultaneously. | |||
| 30.03 | Function keys/hot keys that provide preformatted data entry screens (e.g., designated data fields) | X | The command line can be used to open preformatted data forms such as NCIC query forms, towing entry forms, etc. | |||
| 31.00 | The solution should have the ability to click on the map and transfer the location into the address field in a call for service | X | The solution supports the ability to create a call by selecting a location on the map. | |||
| 32.00 | The solution should have the ability to provide type-ahead capability where the user can continue entering data while the system is processing a previous transaction | X | When entering information, type-ahead functionality allows users to refine lists as they type. | |||
| 33.00 | The solution should have the ability to support drop-down menus and auto completion | X | Type-ahead functionality allows users to type a few characters and refine drop-down lists as they enter information. | |||
| 34.00 | The solution should sort/filter any pick list by type and description | X | Type-ahead functionality allows users to type a few characters and refine drop-down lists as they enter information. | |||
| 35.00 | The solution should allow for the selection of items from a pick list by keyboard navigation and mouse (point and click) | X | Users can use keyboard or mouse navigation to select items in drop-down lists. | |||
| 36.00 | The solution should have the ability to provide word processing capabilities on narrative and comment fields including text wrap, spell check, and copy/paste | X | The system supports standard, familiar word processing functionality. | |||
| 37.00 | The solution should have the ability for new call narrative/notes to appear at the top of the call narrative section, with the ability to quickly switch to chronological view | X | Most recent information appears at the top of the list; users can sort/filter items in the grid as desired. | |||
| Command Line | ||||||
| 38.00 | The solution should allow for multiple command lines that can be placed anywhere on the user's screens | X | The system supports multiple command lines. | |||
| 39.00 | The solution should provide command help or fields the user can tab into to enter information | X | As users enter commands, the command syntax highlights the particular parameter of the command the user is currently entering. Using a space after each parameter of the command moves the command to the next parameter entry point. | |||
| 40.00 | The solution should have the ability to string multiple commands together for a single command line entry, executing both commands when the user selects the "Enter" key (e.g., for unit statuses: One unit is at scene and another unit is enroute) | X | Complex commands can be "strung" in the command line box to conduct multiple transactions such as change location, status, add comments, add mileage, etc. These command strings are limited to one unit at a time. | |||
| 41.00 | The solution should allow for hot keys to execute commonly used commands (e.g., typing the unit number, location, plate, and state, then selecting a function key that is specific to a traffic stop) | X | Users can configure commands and associated keyboard shortcuts so that the command can be executed without requiring use of the Command Line. | |||
| 42.00 | The solution should allow the users to enter either the unit or the actual desired command first. | X | Command line commands are structured and require the information to be entered in a specific order. The command line entry box displays a syntax prompt above the command line entry field that guides the user in the completion of a command. | |||
| 43.00 | The solution should allow for a drop-down list of previous commands and allow users to select from the list to populate the command line with that command string | X | A history of all commands that have been sent since initial login can be displayed by clicking the down arrow on the keyboard. History commands are in reverse chronological sequence, with the last command executed displayed at the top of the list. | |||
| 44.00 | The solution should allow users to open, close, and toggle between command lines with a single keystroke | X | Toggling between multiple command lines requires a mouse or pointing device. This functionality is not supported. | |||
| 45.00 | The solution should allow the agency to configure their desired command format/syntax | X | The Command Maintenance window in Enterprise CAD allows users to enter and maintain commands that are then entered on the Command Line in order to perform a function. | |||
| 46.00 | The solution should include commands that combine multiple status updates simultaneously (e.g., dispatched and enroute or dispatched and at scene) and log appropriate time stamps for each | X | Complex commands can be "strung" in the command line box to conduct multiple transactions such as change location, status, add comments, add mileage, etc. | |||
| 47.00 | The solution should include a call-specific command line or have the ability to default a command to the selected call for service | X | The command line is associated to the call for service number by entering the command, a space, and designating the CFS number, then entering the command syntax to complete the transaction. For example, the command to suppress tones on call for service number 197 is "SUPT 197 Yes" <enter>. | |||
| 48.00 | The solution should provide the ability for the command line to allow for updates of all units on a call simultaneously using call for service number (e.g., all units at scene at the same time, all units in service at the same time) | X | The system includes a mapped command to change the status of all units on a call. Additionally, users can configure commands to accommodate agency workflow. | |||
| 49.00 | The solution should provide the ability for the command line to allow for all commands to be executed using a unit number or call for service number (where applicable) | X | Users can configure commands to accommodate agency workflow. | |||
| 50.00 | The solution should allow agency administrators to alias vendor commands | X | Basic default commands are included with the Enterprise CAD solution. Agency users can customize commands as needed to accommodate agency workflow. | |||
| Timers and Time Stamps | ||||||
| 51.00 | The solution should have the ability to automatically time stamp all activities. Time stamps should include the date/time, unit numbers, and the user(s) performing the function/activity | X | Enterprise CAD tracks user activity down to a field/column level. CAD audit logging is part of every call for service (CFS), which automatically includes both call and unit logging. The Logs tab of the CFS window records information about the entry and editing of all CFS data. The system also logs all unit activity such as status changes, location entries and timers. | |||
| 52.00 | The solution should have the ability to configure timers and alerts based upon agency-defined parameters to include any and all combinations of the following: Unit status, call status, call priority, and call type | X | Call type and unit status timers can be configured in Enterprise CAD Maintenance. | |||
| 53.00 | The solution should automatically reset timers as unit and call statuses change | X | Call type timers start automatically as the first assigned unit changes status to on scene. Call type timers stop automatically as the call for service is closed/cleared. The call type timer will reset when the check in button is pressed in Enterprise Mobile or when the timer is reset manually by a CAD user. | |||
| 54.00 | The solution should have the ability to associate timers with: | -- | -- | -- | -- | -- |
| 54.01 | Unit status updates | X | Administrators can attach a unit timer to a unit status. | |||
| 54.02 | Call type timers | X | Timers can be defined for call types so when those call types are assigned to a call and the specified time passes, a timer would display in the Call Type Timer Overdue column in the Call List grid. | |||
| 54.03 | Agency-defined time in current unit or call status | X | When a unit is in a given status, the unit status timer defines the intervals at which a unit must check in with dispatch. | |||
| 54.04 | Call priority | X | Administrators can designate the priority of the call for service to which a status timer applies. | |||
| 55.00 | The solution should allow for timers to be configured at the agency level (e.g., each agency on the system may have their own timers) | X | The system supports agency-defined timers. | |||
| 56.00 | The solution should allow for timers to be configured for any agency- defined statuses | X | The system supports unit status timers. | |||
| 57.00 | The solution should allow for timers to be set automatically and manually for calls and units | X | Timers are automatic based on configuration and can also be set manually from the command line or right-click menu options. | |||
| 58.00 | The solution should allow for a "generic" timer that can be set by a user for any reason and time | X | The system does not support generic timers. Timers are configured in Enterprise CAD Maintenance and can be managed in the Dispatch Client. | |||
| 59.00 | The solution should allow users the option to clear and snooze timers | X | Users can Start (manually start a timer), Stop (stop the timer and display the time it was stopped in the call), and Acknowledge (stops the current alert and returns the cell to a normal state while the timer continues to run). | |||
| 60.00 | The solution should have the ability to alert users to the expiration of timers via: | -- | -- | -- | -- | -- |
| 60.01 | Audible alert | X | Administrators can configure an audible alarm to play in conjunction with the timer. | |||
| 60.02 | Visual alert | X | The corresponding cell in the timer alert column blinks and displays the time elapsed based on settings configured in CAD Maintenance. | |||
| 61.00 | The solution should include the ability for agency administrators to configure whether timers are audible, visual or both | X | Administrators can configure the visual and/or audible settings for timers in Enterprise CAD Maintenance. | |||
| 62.00 | The solution should have the ability to automatically present visual and/or audible alerts/flags associated with the address, upon entering an address, including but not limited to: | -- | -- | -- | ||
| 62.01 | Alert/hazard information | X | The Alerts tab allows users to view information pertaining to any alerts associated with the current CFS. | |||
| 62.02 | Premise history information | X | Prior Incident alerts are displayed in the Alerts tab of the CFS, and can be split into their own sub-tab (Priors) based on agency configuration. | |||
| 63.00 | The solution should have the ability to enter an apartment, lot, or suite number in a separate designated field for address verification | X | The system supports qualifiers in dedicated fields for location verification. | |||
| 64.00 | The solution should have the ability to log when dispatchers have viewed alerts | X | The system captures when users have viewed alerts in the Call Log for the CFS. | |||
| 65.00 | The solution should have the ability when querying a name for users to be notified of an associated alert (e.g., if a person was flagged in the RMS, if a person is wanted via NCIC) | X | Enterprise CAD has a local search feature that allows the agency to build a local search that is sent at the same time as an NCIC query. A name query return via the CAD NCIC query will alert the CAD user to any wanted or other priority NCIC flag according to normal state and NCIC functionality. Alerts that have been created via the CAD system and are associated with a person will appear in the local search return. | |||
| 66.00 | The solution should have the ability for flags/alerts to be dynamic (e.g., users can click on flag for additional information) | X | Clicking the Detail button corresponding to an alert opens up the Global Alert Details dialog listing all relevant information for the selected alert. | |||
| 67.00 | The solution should have the ability to provide a call history at an address when creating a call | X | Prior Incident alerts are displayed in the Alerts tab of the CFS, and can be split into their own sub-tab (Priors) based on agency configuration. | |||
| 68.00 | The solution should have the ability for users to sort a summary of previous calls by: | -- | -- | -- | -- | -- |
| 68.01 | Chronological order (most or least recent) | X | Users can sort and/or filter by any of the columns in the grid. | |||
| 68.02 | Call type | X | Users can sort and/or filter by any of the columns in the grid. | |||
| 69.00 | The solution should have the ability to alert users of previous calls for service at a specific location within an agency-defined timeframe, based on specified call types | X | Call types can be set to generate prior incident alerts and a duration can be set in number of days (30, 60, 90, 365, etc.). | |||
| 70.00 | The solution should have the ability for user to add a new alert/flag | X | Users can enter location, person, vehicle, and phone alerts by clicking the Enter Alert button on the Dispatch tab's ribbon to open the Alert Entry window. | |||
| 71.00 | The solution should have the ability to associate an expiration with a alert/flag | X | Effective and Expiration Dates can be captured in the entry of an alert. | |||
| 72.00 | The solution should have the ability to include alert information with dispatches sent to responding units | X | Information pertaining to any alerts associated with the current CFS is viewable by dispatch and Mobile users. | |||
| 73.00 | The solution should include the ability to alert/flag based on a specific address and unit/apartment number | X | The solution supports location alerts, including the ability to place an alert on a specific unit/apartment. | |||
| Call Taking | ||||||
| 74.00 | The solution should have the ability to receive call data from: | -- | -- | -- | -- | -- |
| 74.01 | E-911 Phone system | X | Tyler's proposal includes a standard E911 interface to support this functionality. | |||
| 74.02 | Private alarm companies (via ASAP to PSAP interface) | X | Tyler's proposal includes a standard ASAP interface to support this functionality. | |||
| 74.03 | TDD/TTY | X | The proposed solution does not support this functionality. | |||
| 75.00 | The solution should have the ability to enter calls using pre-formatted screens | X | The Default CFS Entry window allows users to enter CFS information when calls are received. | |||
| 76.00 | The solution should have the ability for an agency to determine the order of fields and the tab order in pre-formatted screens | X | Administrators can define a custom design for the CFS Entry window or Quick Call Entry window using the Custom View Editor, a drag-and-drop design, and resizing tool that allows users to customize the upper area of the CFS Entry window or Quick Call Entry window. A customized window may use a different order for the entry fields, or add or remove fields altogether. | |||
| 77.00 | The solution should have the ability for an agency to determine what data elements are captured as part of the pre-formatted screen | X | The Custom View Editor allows administrators to re-order entry fields or add/remove fields. | |||
| 78.00 | The solution should have the ability to automatically populate the call entry screen with information from the E9-1-1 application (no manual intervention required) | X | Enterprise CAD has a create CFS feature that allows a CAD user to right click on the E911 caller information card and select the create CFS from the menu. When a CFS is created from the E911 Caller Card, the caller information and location is automatically used to create the call for service. | |||
| 79.00 | The solution should have the ability to populate the CAD screen with information from the E9-1-1 application via manual intervention (e.g., function key, mouse click) | X | When E911 calls are received, a caller card is created and positioned in a queue on the left side of the window. It is also logged in the grid and contains columns for critical call information such as PSAP number, Class of Service, Location, Latitude, Longitude, Elevation, Nearest Address for wireless callers, Uncertainty distance, and Confidence%. Right-click options on the caller card allow users to create or update a CFS, among other actions. | |||
| 80.00 | The solution should have the ability for narrative fields to allow for an unlimited number of characters | X | There is no Tyler-imposed restriction on the narrative field, although an upper limit on the narrative characters may be imposed by the Windows operating system. The character restriction is virtually unlimited. | |||
| 81.00 | The solution should have the ability to enter standard information in defined fields for the following: | -- | -- | -- | -- | -- |
| 81.01 | Persons (callers, witnesses, suspects), including description(s) | X | The People tab enables users to enter and maintain information on people involved with a call for service such as witnesses, callers, and suspects. Clicking the People tab displays a grid listing people associated with the CFS as well as controls allowing the entry of additional associated persons. | |||
| 81.02 | Vehicles (including license plate and vehicle description) | X | The Vehicles tab allows for the entry and maintenance of vehicles associated with a Call for Service. Clicking the Vehicles tab displays a grid listing vehicles associated with the CFS as well as controls allowing the entry of additional vehicles, performing a global search, manually initiating an NCIC query, and viewing plate history for a vehicle. | |||
| 81.03 | Location | X | Verified locations are captured in the Call Location fields. | |||
| 82.00 | The solution should have the ability to alert dispatchers that the call taker has added information by means of: | -- | -- | -- | -- | -- |
| 82.01 | Audible alert | X | Audible alerts are not supported for all updates on a call, as doing so would result in a high number of sounds being played. | |||
| 82.02 | Visual alert | X | When a change is made to a CFS by another user, a CFS Change Indicator icon shows up next to that CFS # in the Default Call List on all other dispatch personnel systems. A colored box displays within its respective quadrant of the icon and offers a “hover over” feature that lists the area of the CFS that was updated. | |||
| 83.00 | The solution should allow the agency to configure whether call update alerts will be audible, visual, or both | X | Visual alerts notify users of updates to CFS information. | |||
| 84.00 | The solution should have the ability for agency-defined fields to automatically query the Nebraska state and NCIC systems (if applicable), and attach returns to the call record | X | Enterprise CAD Maintenance allows agency administrators to create and maintain NCIC form used in CAD. Enterprise Mobile uses pre-configured base NCIC forms, but agency administrators can create custom NCIC fields for NCIC persons, vehicles, and property (articles) queries. In both applications, there must be NCIC supported data available for the custom fields to return data. | |||
| 85.00 | The solution should have the ability to generate a call from a previous call | X | Users can copy calls from the right-click menu in the Call List, from a Custom CFS Entry window, or from a mapped command. | |||
| 86.00 | The solution should have the ability for call takers and dispatchers to work on the same call for service simultaneously | X | Multiple users can update on the same CFS record simultaneously. Users are notified of new information via the Change Indicator icon in the Call List. | |||
| 87.00 | The solution should have the ability for call takers to add comments to a call after it has been dispatched and automatically update the dispatcher's call screen | X | Comments can be added throughout the life cycle of a CFS, and updates are automatically available to other users as they are made. | |||
| 88.00 | The solution should include the ability for users to mark call comments and messages as urgent/high priority | X | A toggle control in the narrative text box allows users to denote critical narratives. | |||
| 89.00 | The solution should have the ability to receive Phase I and Phase II geographic X/Y coordinates from a cellular telephone carrier | X | Enterprise CAD supports this function via the E911 and Rapid SOS query functions. As a phone call is received, E911 data is received (if available) from the E911 and/or Rapid SOS subscription. This data includes location information. This data can be used by a CAD dispatcher to create a call for service and auto-populate the location and other caller data in the new call. | |||
| 90.00 | The solution should have the ability to relate X/Y coordinates to an actual address | X | E911 location data will populate the address field if a call for service is created from E 911. Any call for service location data in the address field can be geoverified or overridden by the CAD dispatcher. If the data is geoverified, this will translate to a verified address point or intersection. | |||
| 91.00 | The solution should have the ability to transform X/Y coordinates to the map for display | X | Right-click menu options allow the call for service to be quickly plotted on the map. | |||
| 92.00 | The solution should have the ability to capture the call location separately from caller location | X | Caller location and call location can be capture separately. The primary call location is captured within the call for service details and the caller location is plotted from E 911 data. | |||
| 93.00 | The solution should have the ability to capture multiple locations outside of caller location, including multiple secondary unit locations | X | Both CAD and Mobile users can add or indicate additional locations to the call for service via the assigned location field and secondary location. Secondary location can also have a location list that will auto populate jails, hospitals, care facilities, etc., based upon status changes and list contents. | |||
| 94.00 | The solution should have the ability to enter a location for an event by entering any of the following: | -- | -- | -- | -- | -- |
| 94.01 | Street address | X | Street Address is captured as part of location. | |||
| 94.02 | Block number or address range | X | Locations can be entered as block numbers/address ranges. | |||
| 94.03 | Intersections - including intersections by partial street names | X | Locations can be entered as intersections. | |||
| 94.04 | Latitude/Longitude | X | Locations can be entered as latitude/longitude coordinates. | |||
| 94.05 | Mile markers by 1/10th of a mile on interstates | X | Mile markers are supported as verified point locations. | |||
| 94.06 | Common place names | X | Common names are supported as verified locations. | |||
| 94.07 | Street and highway name aliases | X | Aliases are supported as verified locations. | |||
| 94.08 | Point and click on the map | X | Users can enter a call for service by right-clicking a location on the map. | |||
| 95.00 | The solution should have the ability to validate intersections, regardless of which street name is entered first (e.g., Main St / Broadway, or Broadway / Main St). | X | When identifying an intersection as the location, users only need to enter one of the street names and the software will display a list of intersecting streets. | |||
| 96.00 | The solution should have the ability to save identical intersection names with different address points | X | Addresses and intersections are unique; however, each is a verified point location. A search for an address can result in the nearest intersection, a search for an intersection can result in a proximity search for the nearest addresses to the intersection. This is dependent on properly maintained GIS data. | |||
| 97.00 | The solution should have the ability to parse address data into any of the following elements: | -- | -- | -- | -- | -- |
| 97.01 | Street number | X | Street number is a supported GIS data element. | |||
| 97.02 | Mile marker | X | Mile markers are supported GIS data elements. | |||
| 97.03 | Apartment, lot, or suite information | X | Apartment, lot, and/or suite number qualifiers are supported GIS data elements. | |||
| 97.04 | Street name | X | Street name is a supported GIS data element. | |||
| 97.05 | Street prefix | X | Street prefix is a supported GIS data element. | |||
| 97.06 | Street type (e.g., Ave., Ln., St, Rd, Way, etc.) | X | Street type is a supported GIS data element. | |||
| 97.07 | Unit type | X | Apartment, lot, suite, and/or unit numbers are captured in a separate address field. Unit type ("apartment," "suite," etc.) is not indicated. | |||
| 97.08 | Unit number | X | Unit number qualifiers are supported GIS data elements. | |||
| 97.09 | City | X | City is a supported GIS data element. | |||
| 98.00 | The solution should have the ability to capture the following information upon receipt of a wireless 9-1-1 call: | -- | -- | -- | -- | -- |
| 98.01 | Latitude/Longitude | X | Latitude and longitude is captured with incoming 911 calls. | |||
| 98.02 | Closest street address | X | Nearest address is captured for wireless callers with incoming 911 calls. | |||
| 98.03 | Nearest cross street | X | E911 location data will supply the caller location and the estimated nearest address. Geoverification from the agency's GIS mapping data will result in address translation or nearest intersection. | |||
| 99.00 | The solution should have the ability to geoverify the location of all entered addresses | X | E911 location data will supply the caller location and the estimated nearest address. Geoverification from the agency's GIS mapping data will result in address translation or nearest intersection. | |||
| 100.00 | The solution should have the ability to override the geoverified location | X | Users can select the "override" check box to override an entered address. | |||
| 101.00 | The solution should have the ability to validate a location entry upon: | -- | -- | -- | -- | -- |
| 101.01 | Operator request (e.g., press a button) | X | Once a location is entered, users can press the tab key to initiate the geoverification process. | |||
| 101.02 | Entry into a location field | X | Entering data into a location field initiates the geoverification process. | |||
| 102.00 | The solution should have the ability to create a report of all overridden geoverified locations | X | Overridden Address report is a standard report. | |||
| 103.00 | The solution should have the ability upon address verification, for the system to auto-populate associated fields (e.g., zip code, town, etc.) | X | Associated data (common names, town/venue, etc.) is populated upon geo-verification of location entries. | |||
| 104.00 | The solution should have the ability for addresses entered by field units (e.g., on a self-dispatch) to correctly populate all address fields in the CAD call | X | The system populates the appropriate address fields when users enter geo-verified locations. | |||
| 105.00 | The solution should have the ability to support RapidSOS integration | X | Enterprise CAD includes native RapidSOS integration. | |||
| 106.00 | The solution should have the ability to use the E9-1-1 ALI reported location address for address verification | X | Location information is captured with receipt of incoming 911 calls. | |||
| 107.00 | The solution should have the ability to use the coordinate-based GIS to determine if there are premise or hazard records within a defined radius of the call | X | The system returns alerts associated with the call, including proximity alerts. The proximity alert distance values are configured by administrators in Enterprise CAD Maintenance. | |||
| 108.00 | The solution should have the ability to enter a street name and be presented with: | -- | -- | -- | -- | -- |
| 108.01 | Aliases | X | Street aliases are supported and maintained by GIS administrators. | |||
| 108.02 | Associated address ranges | X | Address range information is included in the Street Sub-Locator data maintained by GIS administrators. | |||
| 108.03 | List of cross streets | X | Cross street/nearest intersection data can be configured to display by GIS administrators. | |||
| 109.00 | The solution should have the ability to automatically display the following data elements that are relevant, upon entry of a verified address: | -- | -- | -- | -- | -- |
| 109.01 | High/low cross streets | X | GIS administrators maintain nearest cross street/nearest intersection configurations to associate with geoverified addresses. | |||
| 109.02 | Common place names | X | Common names, business names, aliases, etc., are supported GIS data elements. | |||
| 109.03 | Business names | X | Common names, business names, aliases, etc., are supported GIS data elements. | |||
| 109.04 | Law Enforcement response area/Troop area | X | The Area Type Maintenance page allows GIS administrators to enter and maintain various types of geographical-based and non-geographical based areas (examples: EMS ORI, police ORI, beat, station, district, neighborhoods, etc.) | |||
| 109.05 | Apartment complex names | X | Common names, business names, aliases, etc., are supported GIS data elements. | |||
| 110.00 | The solution should have the ability to translate the call location to the appropriate public safety geographical boundary/Troop area | X | GIS administrators maintain areas/area types so that they may be associated with geoverified locations. | |||
| 111.00 | The solution should have the ability to translate street alias names to actual street names or addresses | X | GIS administrators maintain aliases so that they may be associated with geoverified locations. | |||
| 112.00 | The solution should have the ability to enter a common place name and be presented with a list of addresses with that common place name (e.g., McDonald's search) | X | If dispatchers enter a valid address that has multiple common names associated to it, an additional list appears below the Contact Location field. Once that list is clicked, a list of common names associated with the address displays. Selecting one of the common names from the list places that common name below the Contact Location field. This allows responders to know exactly where to contact the caller for locations with multiple occupancies. | |||
| 113.00 | The solution should have the ability to notify users through a visual and/or audible flag if multiple street addresses, street names, or intersections are found in GIS | X | The Interactive Location Prompt (ILP) feature allows users to see a list of candidates as they enter characters from a common name, address, intersection, etc. | |||
| 114.00 | The solution should have the ability to offer a list of address options if multiple similar addresses, intersections, or street names are found in GIS | X | The Interactive Location Prompt (ILP) feature allows users to see a list of candidates as they enter characters from a common name, address, intersection, etc. | |||
| 115.00 | The solution should have the ability to display, on a map, the call location in relation to other active calls on the map during the call entry process | X | Calls display on the map based on user settings. Additionally, users can use right-click functionality in the call list to zoom to the call on the map. | |||
| 116.00 | The solution should have the ability to manually verify an address without creating an event | X | The Verified Address Search window allows users to search for addresses that are verified and have them plot on the map. Once a verified address has been entered, a list of possible matches is displayed. | |||
| 117.00 | The solution should have the ability to display a drop-down list containing call types | X | Call types are agency-defined and maintained in a validation set, a dropdown table from which users can select the appropriate call type in the CFS Entry screen. | |||
| 118.00 | The solution should filter the list of possible call type candidates by code and description, allowing users to easily filter and select the appropriate call type via keyboard function | X | The proposed solution includes a type ahead function within drop-down menus that will narrow the list and allow quick selection of a list item using the mouse or keyboard. | |||
| 119.00 | The solution should allow authorized users to override the default call priority | X | The default priority associated with a call type as configured in Enterprise CAD Maintenance auto-populates the priority field in the CFS entry screen. Users can change the priority at any time. | |||
| Call Creation | ||||||
| 120.00 | The solution should have the ability to create a CAD call by entering a location and call type, at minimum | X | Location is the only required field to create a call for service. | |||
| 121.00 | The solution should have the ability to input all call and narrative information on one screen | X | The Default CFS Entry screen captures location, call type, narrative, caller, etc. information and includes individual tabs for the collection of further information (vehicles, people, alerts, dispositions, etc.). Additionally, administrators can configure custom CFS Entry or Quick Call Entry windows to re-order entry fields or add/remove fields altogether. | |||
| 122.00 | The solution should have the ability to display a blank form for entering new calls with a single keystroke, mouse click, or function key upon initiation of a CAD call | X | Users can create a call via several methods, including clicking the Create Call button, using the command line, copying calls from the Default Call List, and right-clicking on the map. | |||
| 123.00 | The solution should have the ability to enter calls using: | -- | -- | -- | ||
| 123.01 | Standard call entry form | X | Users can create a call by clicking the Create Call button to open a new CFS entry window. | |||
| 123.02 | Command line | X | Users can create a "new call" from the command line. | |||
| 124.00 | The solution should have the ability to suspend the entry of a call (hold) | X | Once a call is created, it becomes part of the pending call list and is available to access, edit, update, etc. at any time until it is cleared or canceled. | |||
| 125.00 | The solution should allow CAD users with appropriate permissions to access and complete calls that were suspended (held) by other users prior to completion | X | Once a call is created, it becomes part of the pending call list and is available to access, edit, update, etc. at any time until it is cleared or canceled. | |||
| 126.00 | The solution should have the ability to support multiple partially completed/suspended calls | X | Calls that have been created but not yet dispatched are part of the pending call list, which supports multiple partially completed calls. | |||
| 127.00 | The solution should have the ability to exclude partially completed/ suspended calls in CAD for viewing by Mobile users | X | Mobile users can use standard available filters or create their own filters to exclude pending calls. | |||
| 128.00 | The solution should have the ability for the call for service record to indicate if call data entry was suspended | X | Via Call and Unit Logs, which track and timestamp all activity on a CFS record. | |||
| 129.00 | The solution should have the ability to time stamp suspension and reactivation of call entry | X | Call and Unit Logs track and timestamp all activity on a CFS record. | |||
| 130.00 | The solution should have the ability to auto-spawn a call for another agency based on a specific on demand (e.g., Capitol Security is needed in addition to NSP) | X | Copying a CFS allows agencies to share calls with associated agencies that may also be responding to the call. When a CFS is copied, the dispatcher can copy existing narratives to the copied call, link the original and copied calls, change the call type for the copied call based on the agency to which the call is being copied, and add comments as to why the CFS was copied. | |||
| Duplicate Call Management | ||||||
| 131.00 | The solution should have the ability to identify and flag potential duplicate calls during the call taking process in a manner that allows users to quickly identify potential duplicate calls to determine if a current call should be supplemented or a new call created | X | The Default Call List includes a column that displays visual indicators regarding possible associated calls. Dispatchers can then open the “Associated Calls" tab of the CFS to see the details of the possible associated call and determine if they are associated or need to be disassociated. | |||
| 132.00 | The solution should have the ability to display proximity calls on a map (e.g., calls within a specified distance of each other to assist users in identifying possible duplicate calls) | X | In the Associated Calls tab, users can enter a search radius to return possible associated calls within a specified radius from the current CFS. All calls can be viewed on the map. | |||
| 133.00 | The solution should have the ability for the agency to define parameters of duplicate call identification (e.g., defined proximity, definition of "recently closed", etc.) | X | Administrators can configure the default search radius, in miles, for the application to search for possible associated calls. | |||
| 134.00 | The solution should have the ability to automatically provide users with call details about possible duplicate calls (including time of call, location, call type, and proximity) | X | Dispatchers can open the “Associated Calls" tab of the CFS to see the details of the possible associated call. | |||
| 135.00 | The solution should maintain all call information when a call is supplemented using the duplicate call/merging functions (e.g., caller names, phone number(s) and remarks, etc.), with appropriate date and time stamps | X | When calls are associated, all original information is retained. | |||
| Premise Information Retrieval | ||||||
| 136.00 | The solution should have the ability to search for premise information based on any of the following data elements: | -- | -- | -- | -- | -- |
| 136.01 | Address | X | Users can search for location information using address. | |||
| 136.02 | Sub-address (e.g., unit number, building floor, apartment number, etc.) | X | Qualifier information (unit/apartment number, etc.) can be used to search for location information. | |||
| 136.03 | Block ranges | X | Block ranges can be used to search for location information. | |||
| 136.04 | Business name | X | Common names, business names, aliases, etc., can be used to search for location information. | |||
| 136.05 | Historic business name (unlimited number) | X | ||||
| 136.06 | Common place names | X | Common names, business names, aliases, etc. can be used to search for location information. | |||
| 136.07 | Intersections (including intersections by partial street names) | X | Users can search for location information using intersections. | |||
| 136.08 | Name | X | CAD users can search for emergency contacts for businesses or premises if a person has been associated to the pre mise as a "contact." | |||
| 136.09 | Phone number | X | The system does not support searching for location information using phone number. | |||
| 137.00 | The solution should have the ability to query the Niche RMS system on demand or based on specific parameters (high risk, etc.) | X | The proposed solution does not support this functionality. | |||
| 138.00 | The solution should have the ability to automatically initiate a search for associated premise information in CAD upon address entry | X | Location and premise history information are displayed in the Alerts tab of the CFS. | |||
| 139.00 | The solution should automatically alert users to premise information on locations not associated with calls based on a specific address or user defined radius | X | Users are notified of associated alerts, and detail information is included in the Alerts tab of the CFS. Users can search for associated alerts and include proximity alerts based on the distance value designated in Enterprise CAD Maintenance. |
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 .