The file's text, extracted by GovTribe without its formatting.
FUNCTIONAL LIST
ATTACHMENT A
| COMPUTER-AIDED DISPATCH (CAD) SPECIFICATION |
| MANDATORY = M |
DESIRED = D
OPTIONAL = O
VENDOR COMPLIANCE
(USE
CODE KEY)
VENDOR COMMENT
LAW ENFORCEMENT
GENERAL SYSTEM REQUIREMENTS
| 1. |
| Include the following functions: |
| d. |
| Location verification |
| M |
| · |
| Information retrieval |
| M |
| · |
| Dispatch resource decision |
| M |
| · |
| Caution notes and Be on the lookout (BOLO) |
| M |
| i. |
| Paging and messaging |
| M |
| j. |
| Mapping functionality |
| M |
| 2. |
| Include the following interfaces: |
| a. |
| With Mobile Data Computers (MDCs) |
| M |
| b. |
| With external, local, state, and federal information systems |
| M |
| c. |
| With RMS (wait until future fiscal year) |
| O |
9-1-1 INTEGRATION
| 3. |
| Support 9-1-1 telephony function integration without additional workstation hardware, keyboard, or mouse |
| M |
| 4. |
| Support 9-1-1 telephony system integration without additional software installation required at the workstation |
| M |
| 5. |
| Support 9-1-1 telephony integration into the same application as the CAD |
| M |
| 6. |
| Expandable to support an SMS messaging function |
| O |
BUSINESS CONTINUITY/DISASTER RECOVERY
| 7. |
| In an emergency that requires that the dispatch center be moved to an offsite, secure location, support the creation of an offsite, real-time backup server at the relocated communication center with hardware and network connectivity |
O
| 8. |
| Agency can enter activity data performed during the interruption of service upon recovery from a CAD service interruption |
| M |
RESOURCE MANAGEMENT
| 9. |
| Facilitate multiple resource types on a single resource (engine, quint, patrol, beat unit) |
| M |
| 10. |
| Incident recommendations must recognize when a unit meets the requirement for more than one resource type |
| M |
ROTATION FOR SERVICES
| 11. |
| Provide a rotation provider module for services such as wrecker towing, locksmith, or private ambulance services |
| M |
| 12. |
| The rotation provider module must provide multiple service provider categories. Example: wrecker rotations support categories for heavy equipment wreckers and passenger vehicle wreckers |
| M |
| 13. |
| Support creation of custom rotations for services such as tow companies, private ambulance services |
| M |
| 14. |
| User can bypass a service provider without penalty and the service provider will remain on the top of the list |
| M |
| 15. |
| System administrator can configure multiple rotation provider lists for various services |
| M |
| 16. |
| Wrecker tow rotation can support multiple rotations |
| M |
| 17. |
| Automatically recommend the next available rotation provider in the correct rotation based on geography |
| M |
| 18. |
| If a service provider cannot respond, the user can note on record and recommend the next rotation provider |
| M |
| 19. |
| If a rotation request is cancelled, the user can place the service provider into the next spot in the rotation |
| M |
| 20. |
| The rotation provider module supports owner requests |
| M |
| 21. |
| The rotation provider module captures, the following data elements related to a tow request: |
| 22. |
| If resources other than those recommended by the rotation are selected, allow the telecommunicator to capture the reason for the exception |
| M |
CALL TAKING
| 23. |
| Call taking includes receiving the call, entering sufficient and accurate information from the caller, determining whether this is a duplicate of a call in progress, and recording or updating a call for service in the system |
| M |
| 24. |
| New calls for service are created using compiled information – both automatically by the system and manually by the user – during the call taking process |
| M |
| 25. |
| Assign a unique call number to each new call for service |
| M |
| 26. |
| Service both emergency and non-emergency priority calls |
| M |
| 27. |
| Provide a command line that allows users to easily create officer-initiated incidents |
| M |
| 28. |
| Support an environment where the call taker is different from the user |
| M |
| 29. |
| Provide a command line for quick and easy entry of traffic stops |
| M |
| 30. |
| Users can enter/create calls from within browser. The newly created calls for service are automatically displayed in the CAD and available for dispatching. |
| M |
| 31. |
| Minimum call information needed to open/initiate a call for service: type of call and location of the call for service |
| M |
| 32. |
| The user answers calls from the public from a 9-1-1 line, a 7- or 10-digit phone number |
| M |
| 33. |
| If the call is generated from the 9-1-1 system, the location is available from ANI/ALI, if interface exists |
| M |
| 34. |
| When ANI/ALI information is provided by the 9-1-1 controller, it is automatically populated in the CAD system into the correct fields |
| M |
| 35. |
| User can apply procedures and guidelines such as ProQA, PowerPhone™, or APCO Meds to verify, analyze, classify, and prioritize the call prior to routing the call for service to dispatch |
O
| 36. |
| A field-initiated incident can be generated from a CAD workstation or the mobile client device |
| M |
| 37. |
| User can create a call for service for future scheduled events |
| M |
| 38. |
| User can perform call taking, geo-validation, unit recommendation, and dispatch of units from a single screen |
| M |
| 39. |
| Display units assigned to an active call within the call taking screen |
| M |
| 40. |
| Display desired calls and units in specific areas |
| M |
| 41. |
| Display summary premise information, with the option to drill down to full details |
| M |
| 42. |
| Filter positions to view calls and/or units related to specific geographic areas, patrol zones, cities, and/or call discipline (police, fire, EMS) |
| M |
| 43. |
| Support multiple call taking screens within the same window |
| M |
| 44. |
| Provide a notification module to alert users of any applicable events occurring in the system |
| M |
| 45. |
| System administrator can configure the notifications within the system |
| M |
| 46. |
| System administrator can alias intersections for use in geo-verification entry |
| M |
| 47. |
| System administrator can alias streets for use in geo-verification entry |
| M |
| 48. |
| Can ‘exact match’ on the address point. If no matching address point is found, revert to the normal street/block range validation, and match on the block address, if appropriate |
| M |
| 49. |
| Provide the following call for service data update capabilities: |
| a. |
| Automatic update as new information related to an open call becomes available |
| M |
| b. |
| Multiple users can view and update the same call simultaneously |
| M |
| c. |
| User entry of narrative data on any pending or active call for service |
| M |
| d. |
| User entry of narrative data to a closed call for service without having to re-open the incident |
| M |
| · |
| All narrative data entered is time and date stamped and the user adding the narrative is recorded with each comment |
| M |
| · |
| Unauthorized users cannot modify narrative data |
| M |
| · |
| Narrative data can be configured and sorted in ascending or descending order |
| M |
| · |
| The user with rights can edit call information – excepting fixed times – after it has been closed and log the changes that were made |
| M |
| 50. |
| System administrator determines when to start the "response" clock (when the user has a valid address and nature/ problem) |
| M |
CALL DISPOSITION
| 51. |
| User can open a call for service |
| M |
| 52. |
| User can close a call for service that does not require the dispatch of resources |
| M |
| 53. |
| Mobile data computers transactions can update CAD to record unit status and close the call for service |
| M |
| 54. |
| Prevent mobile data computer users from closing calls for service |
| M |
| 55. |
| If all mobile units are removed from the call via mobile data computers, then the call for service is placed in the pending dispatch queue for closure by the user |
| N/A |
| 56. |
| Call information collected during the call for service is available for use by the field reporting tool and RMS |
| M |
| 57. |
| Configurable to require a disposition by incident, by unit, or not at all |
| M |
| 58. |
| Configurable to enforce that a call disposition is required when the unit clears from the incident |
| M |
| 59. |
| Multiple dispositions can be added to individual units |
| M |
| 60. |
| Each call for service can have multiple dispositions assigned |
| M |
| 61. |
| Assign a disposition to the call for service different than the unit disposition |
| M |
| 62. |
| Automatically evaluate the call for service location to determine whether a call is a duplicate. The user compares the system information to the caller information to determine whether the call is a duplicate. |
| M |
| 63. |
| User can append an identified duplicate call to the original call for service or link it to an existing call |
| M |
| 64. |
| An officer can enter call for service disposition via optional MDT interface |
| M |
| 65. |
| Enable or disable multi-assign and call stacking |
| M |
| 66. |
| Custom time stamps can be built for use on the incident screen, such as Fire Under Control, Secondary Search Complete |
| M |
LOCATION VERIFICATION
| 67. |
| Caller location is checked against current address listings in the system. The location format can be any of the following: |
| c. |
| Common place name. Location information for a common place, such as the City Hall, has a street address listing cross-reference that will provide the legal street address. |
| M |
| 68. |
| Geofile performs the following functions: |
| a. |
| Validate the street name as an existing street in the geofile for the service area |
| M |
| b. |
| Resolve ambiguities while accounting for spelling variations and duplications |
| M |
| c. |
| Validate intersections |
| M |
| d. |
| Validate address range |
| M |
| e. |
| Relate common place names to actual addresses |
| M |
| f. |
| Relate X, Y coordinates to an actual address |
| M |
| g. |
| Transform latitude and longitude to map coordinates for display for Phase II calls |
| M |
| h. |
| Determine call location to agency reporting area |
| M |
| i. |
| Translate alias names to actual street names |
| M |
| 69. |
| Suggest matches as the user types prior to geo-validation for: |
| 70. |
| Suggest geo-validation options as the user enters information into the call taking record |
| M |
| 71. |
| User can select an address via hotkey without taking focus from the current field within the call taking screen |
| M |
| 72. |
| Perform a duplicate check of any other active incidents within a specified radius of the new call upon geo-validation of an address |
| M |
| a. |
| The radius of the duplicate check is configurable by the system administrator |
| M |
| b. |
| The duplicate check also searches recently closed incidents |
| M |
CALL PRIORITIZATION
| 73. |
| Prioritize calls based on call type, applying established guidelines and procedures to determine the appropriate dispatch and response needs |
| M |
| 74. |
| Support multiple different call priorities |
| M |
| 75. |
| Automatically update call for service priority upon call type modification |
| M |
| 76. |
| User can manually update call for service priority without call type modification |
| M |
| 77. |
| Display high priority caution note information to the user without taking focus from the current active field |
| M |
CALL MANAGEMENT
| 78. |
| Manage the call by continuously updating the call for service data with any additional information reported by callers or officers on scene |
| M |
| 79. |
| Call for service data are displayed and monitored through CAD, including activities such as additional call information and activities reported by the officers |
| M |
| a. |
| Call for service queue provides immediate access to all open calls, including unassigned |
| M |
| b. |
| Automatic removal of a closed call from the call display |
| M |
| 80. |
| User can manually manage the call by continuously updating the DVS data with any additional information reported by callers or officers on scene |
| M |
| 81. |
| User can revise resource recommendations based on additional information |
| M |
| 82. |
| User can add or reassign resources based on additional information |
| M |
| 83. |
| Display additional call for service data and alert user once information is available |
| M |
| 84. |
| Make the following information available to view: |
| a. |
| Recently closed calls (within no more than two actions) |
| M |
| b. |
| An existing VFS that has been cleared |
| M |
| c. |
| Changes to cleared calls for service are traced for audit purposes |
| M |
REOPENING A CALL
| 85. |
| User can reopen a call |
| M |
| 86. |
| When reopening a call, the incident is placed in the pending incident queue allowing the user to assign appropriate units |
| M |
INFORMATION RETRIEVAL – IS THE INFORMATION LIMITED TO THE AGENCY’S PARTICULAR RMS SYSTEM? OR COUNTY SHARED INFORMATION?
| 87. |
| Ability to query RMS for the following Person information: |
| c. |
| Mental or health issues |
| M |
| 88. |
| User can query master vehicle information. Any previous instance of the vehicle associated with a call for service will be displayed. |
| M |
| 89. |
| Automatically search internal files for information on premise locations and history of previous calls for that location |
| M |
| a. |
| Automatically search for medical alerts entered as caution notes or premise comments at the call for service location |
| M |
| b. |
| Automatically search for hazard information entered as caution notes or premise comments at the call for service location |
| M |
| c. |
| Automatically search for contact information entered as caution notes, premise information or alarm information at the call for service location |
| M |
| d. |
| Automatically search for fire plan information at the call for service location. Fire plan information can include, at a minimum, lock box location, contact information, sprinkler information, and provide free-text area for agency-defined information. |
| M |
QUERY
| 90. |
| Run of records checks (Person, Vehicle, Article and Firearm) by entering the criteria in a mask or via a command line |
| M |
| 91. |
| Provide notification of ‘hot’ records check returns by visual and/or audio indicator |
| M |
| 92. |
| Query mask indicates which fields are required based on the query |
| M |
| 93. |
| Query mask indicates which fields will be submitted based on the query |
| M |
| 94. |
| Justice message switch allows connection to multiple databases (JUSTICE PARTNERS; LEGAL SOURCE?) |
| M |
| 95. |
| Incident screen provides visual notification of the following information without a query: |
| a. |
| Hazardous material (hazmat) information on file |
| M |
| b. |
| Premise information on file |
| M |
| c. |
| Prior incidents to the address |
| M |
| d. |
| Permit information on file |
| M |
| e. |
| Supplemental information entered for the incident |
| M |
| 96. |
| Can add supplemental information (Person, Vehicle, Firearm and Property) and optionally submit a query |
| M |
REPORTABILITY
| 97. |
| Can add a case number to indicate if the call for service requires a report |
| M |
| 98. |
| When the report number is assigned, it can be viewed by dispatch workstations and MDTs |
| M |
| 99. |
| Can assign case numbers by pulling them directly from the RMS |
| O |
QUEUE MANAGEMENT
| 100. |
| User can create ad hoc queues |
| O |
| 101. |
| User can filter on any logical field in the incident and unit queue |
| O |
| 102. |
| User can sort on any logical field in the incident and unit queue |
| M |
| 103. |
| User can add any available columns to the queue display and save it to the user profile |
| M |
| 104. |
| User can re-order the displayed columns in the queue display and save it to the user profile |
| M |
| 105. |
| User can group by any column in the queue display and save it to the user profile |
| M |
| 106. |
| User can display any created ad hoc columns in a tab within the window |
| M |
| 107. |
| User can display any created ad hoc columns as a tiled window within the queue display window |
| M |
| 108. |
| User can display any created ad hoc columns as their own window |
| M |
| 109. |
| User can drill into unit or incident details from the queue management display without opening a separate window to display the information |
| M |
| 110. |
| User can execute any logical command line action against the incident or unit that has been selected, within the drill down display |
| M |
| 111. |
| User can display all assigned units on the incident on the incident drill down display |
| M |
| 112. |
| User can execute any appropriate status action from within the unit drill down display |
| M |
| 113. |
| User can rename any newly created queue tabs and save the name to the user profile |
| M |
| 114. |
| When a user takes control of a command sector, the incident and unit queue management display automatically add the appropriate incidents and units to the display |
| M |
| 115. |
| Drag-and-drop assignment within the queue management display of incidents to units |
| M |
| 116. |
| Default sort of events in the call queues by agency-defined priority |
| M |
UNIT RECOMMENDATION
| 117. |
| Check location information obtained from the caller or ANI/ALI data spill and verify using the geofile to identify the patrol area assignment in which the call is located |
| M |
| 118. |
| Determine unit proximity based on the unit’s assigned area of responsibility and/or a GPS device attached to the unit |
| M |
| 119. |
| Dynamically recommend the closest appropriate resource for a call for service based on unit drive time, taking into account road speeds |
| M |
| 120. |
| Automatically recommend resources for the selected call for service based upon preset criteria for the response area, call for service type and priority. Preset criteria includes but is not limited to unit and personnel capabilities as well as unit resource designations. |
| M |
| 121. |
| Automatically recommended resources based on response plans that factor in unit capability with regard to skills and equipment required for the call for service, unit availability, and proximity of resources |
| M |
| 122. |
| Recommend resources based on the closest most appropriate units, based on response plan |
| M |
| a. |
| Unit recommendation based on a station order, based on the response plan |
| M |
| b. |
| Display the closest unit(s) based upon information received from GPS devices attached to the units |
| M |
| 123. |
| The system administrator can configure the system to automatically assign an incident number based on the jurisdiction |
| M |
| 124. |
| User can accept, override, or modify the recommended resources based on additional information provided by (or by request of) units on the scene |
| M |
| 125. |
| Apply multiple capabilities to a single resource (extrication tools, spike strip, Spanish speaker). Incident recommendations recognize when a unit meets the requirement for more than one capability. |
| M |
| 126. |
| Process way streets, elevations for bridges and tunnels, speed limits, road types, and road impedances for unit recommendations as well as driving directions for mobile users |
| M |
| 127. |
| Users can adjust road speeds, closures and detours in real time for specific road segments to dynamically alter unit recommendations and driving directions in responders’ mobile computers. Additionally, dispatch maps visually indicate these road impedances. |
| M |
| 128. |
| Uses Intellisense to recommend location information |
| M |
| 129. |
| Recommend units that are currently assigned to a lower priority incident (but not yet on scene) for a higher priority incident |
| M |
| 130. |
| The system administrator can configure eligibility of unit status for recommendation |
| M |
DISPATCH RESOURCE DECISION
| 131. |
| Automatically route the call to the correct user based on the call type and location |
| M |
| 132. |
| Display available resources based upon unit status, including “unassigned” and “assigned but available” |
| M |
| 133. |
| Show separate pending and assigned queues |
| M |
| 134. |
| User can re-sort the pending call queue and the assigned call queue based on any data column displayed in the queue |
| M |
| a. |
| User can re-sort the data with a single action |
| M |
| b. |
| User can re-sort the call queues as often as desired |
| M |
| c. |
| User can re-sort based on the system default call order with a single action |
| M |
| 135. |
| User can assign the recommended resources or modify the recommendation and assign |
| M |
DISPATCH UNITS
| 136. |
| Automatically assign and notify units of incidents based on the response area, nature/problem |
| M |
| 137. |
| Agency can perform dispatch and notify units manually (select and assign per incident type) |
| M |
| 138. |
| Units specifically recommended or selected for a call for service can be dispatched by one action |
| M |
| 139. |
| User can dispatch units without system recommendation by command line or drag-and-drop action |
| M |
| 140. |
| User can change the primary unit designation from the CAD workstation or from the mobile at any point during the call for service |
| M |
| 141. |
| Compare the travel time of the farthest assigned unit to the newly available unit to recommend to the user a “swap” of units |
| M |
| 142. |
| Swap calls with either drag-and-drop or via a command line. Information about the swap is recorded in the incident comments. |
| M |
| 143. |
| Can restrict incident cancellation to the user controlling the area. Non-controlling users can submit a “request to cancel” to alert the controlling user. |
| O |
| 144. |
| Non-controlling user can assign units not under their control. This option is set at the Agency level. |
| M |
| 145. |
| User can view unsent resources/vehicles for the incident if not all resources are available at the time of dispatch |
| D |
| 146. |
| Can designate a response area as primary if a specific location falls into more than one response area |
| D |
| 147. |
| Can edit the response areas by adding, moving, or deleting a node |
| M |
| 148. |
| Support radio channel assignment based on radio groups within a geographic area |
| M |
| 149. |
| Multiple incidents can be assigned to the radio channel |
| M |
| 150. |
| Support the creation of strike teams |
| a. |
| The creator has the ability to name the strike team |
| M |
| b. |
| Strike team status changes are applied to all units assigned to the strike team |
| M |
ASSIGN UNITS
| 151. |
| User can remove Assigned by Available units from their assigned status based on priority levels and the resource needs of the call for service |
| M |
| 152. |
| A unit or units can be reassigned. The units are placed in on available status and the call for service returned to the Pending Incident queue. |
| M |
| 153. |
| Can divert a unit en route while encountering an incident |
| M |
| 154. |
| Can stack a pending incident to a unit |
| M |
| 155. |
| Provide a visual status indicator that the unit is assigned to one call and stacked on another |
| M |
| 156. |
| Multiple calls for service can be stacked to a specific unit. Time stamps for multi-assigned calls are recorded at unit assignment. |
| M |
| 157. |
| When the unit takes an action related a multi-assigned call for service, the timestamp is recorded immediately |
| M |
| 158. |
| Prompt the user to cancel, multi-assign, or stack an incident if the incident is placed on a unit that is currently assigned |
| M |
| 159. |
| Continually monitor, update, and record unit status entered by the user and/or mobile units |
| M |
| 160. |
| Unit status change information is available for inclusion in predefined and agency-defined reports |
| M |
| 161. |
| Automatically update the call for service record to designate the dispatched unit(s) as responding units to the call |
| M |
UNIT STATUS
| 162. |
| Continuously display information to reflect the current status of the units the user is monitoring |
| M |
| 163. |
| Continuously update information to reflect the current status of the units the user is monitoring |
| M |
| 164. |
| Unit activity report include, at minimum: |
| c. |
| User updating status |
| M |
| 165. |
| The unit status options include: |
| d. |
| Arrived at destination |
| M |
| · |
| Prompt user to enter a destination and odometer reading |
| M |
| f. |
| Left scene for secondary location |
| M |
| g. |
| Arrived at secondary location |
| M |
| i. |
| · |
| Prompt user to enter a destination and odometer reading |
| M |
| j. |
| Conditional availability |
| M |
| · |
| Support the use of configurable conditional availability reasons |
| M |
| 166. |
| Reasons for conditional availability support unit delay settings. The system administrator sets a standard time delay for conditional availability reason and factors the unit delay into the unit estimated time of arrival when unit evaluation for recommendation takes place. |
| M |
| 167. |
| Reasons for conditional availability support valid incident priorities for recommendation. The system administrator can make only selected incident priorities available for recommendation and dispatch when a unit has conditional availability reason with this option configured. (A unit is available for recommendation to priority 1 and 2 calls but not lower priority calls.) |
| M |
| 168. |
| Each agency-defined status assigned updates the unit log and records a time and date stamp |
| M |
| 169. |
| Capture and time-stamp any change in unit location |
| M |
| 170. |
| Maintain the elapsed time between status changes/checks and alert the user when agency-defined thresholds are met |
| M |
| 171. |
| Provide an elapsed timer that displays the total duration of the call |
| M |
| 172. |
| Display indicates unit status and assigned call for services, if any |
| M |
| 173. |
| Display indicates the last location entered for the unit |
| M |
| 174. |
| Location updates can performed manually or by use of an AVL feed |
| M |
| 175. |
| When the unit timer expires, display call for service type and priority for assigned units |
| M |
| 176. |
| Alert the user to the expiration of unit timers |
| M |
| 177. |
| System administrator can configure the amount of time before expiration of the timer, based on call for service priority |
| M |
| 178. |
| System administrator can configure an alert to the assigned units that the time required has expired |
| M |
| 179. |
| User can reset after the timer has expired |
| M |
| 180. |
| User can cancel the timer for the current call for service |
| M |
| 181. |
| Recorded unit status activity is updated to associate the dispatched unit(s) with the call for service, including location and time |
| M |
| 182. |
| When a unit has cleared from a scene and is no longer assigned to the call for service, the unit is assigned ‘available’ status |
| M |
| a. |
| Data received from mobile data computer transmissions updates CAD and reflects the new status of the unit |
| M |
| b. |
| Clearing the call clears all units assigned to the call for service and all units are reassigned to ‘available’ status |
| M |
| 183. |
| Can "reply" a units travel history or incident record for specific time period or incident |
| M |
CAUTION NOTES
| 184. |
| Support a user with the correct permissions to enter a caution note to: |
| a. |
| Address/intersection or premise |
| M |
| 185. |
| User can enter a caution note containing a start date/time and an end date/time. The caution note displays only during the time it is valid. |
| M |
| 186. |
| Caution notes can be entered to the building and/or apartment level |
| M |
INCIDENT REVIEW
| 187. |
| User can recreate a picture of the system at the time of unit assignment to an incident |
| M |
| 188. |
| The report displays: |
| b. |
| Summary of other units and incidents |
| M |
| c. |
| Status count summary |
| M |
| d. |
| Incident count by priority |
| M |
| e. |
| Active System Status Management (SSM) plan |
| M |
| f. |
| Map of displayed units |
| M |
BE ON THE LOOKOUT (BOLO)
| 189. |
| Authorized user can enter BOLOs and maintain the BOLO files |
| M |
| 190. |
| BOLO creator can assign an associated expiration date |
| M |
| 191. |
| BOLO file includes the following information: |
| e. |
| Subject vehicle information |
| M |
| 192. |
| Search BOLOs and print a report of the search results |
| M |
| 193. |
| Support BOLO creation and transmission |
| M |
PAGING AND MESSAGING
| 194. |
| Paging system has a backup service provider |
| M |
| 195. |
| Paging system allows custom text messages using database fields to provide information to the field unit assigned the pager |
| M |
| 196. |
| Supports alpha-numeric paging using the following protocols: |
| d. |
| Motorola’s Carbon Copy® |
| O |
| 197. |
| Messaging system supports all attachments |
| M |
| 198. |
| Support communication between communication center, web, and mobile client CAD applications |
| M |
| 199. |
| Can audit all messages based on: |
| 200. |
| Support portable radio assignment so that the name of the person assigned can be displayed to the user in the event of an emergency activation |
| M |
SYSTEM ADMINISTRATION MODULE
CONFIGURATION
| 201. |
| Multiple custom text fields can be built that can be used on the incident screen to collect agency-defined information |
| M |
| 202. |
| Configurable to include enforcement of agency SOPs (dispatch policies) |
| M |
| 203. |
| Configurable to determine, screen parameters, color choices, screen layout and user preferences |
| M |
| 204. |
| System administrator can prevent users from modifying status color schemes |
| M |
| 205. |
| System administrator can allow or prevent users from modifying the call entry form and/or the active call viewing form |
| M |
| 206. |
| System administrator can allow users to assign a primary and multiple secondary roles or resource types and multiple capabilities for the same units |
| M |
| 207. |
| Users can change dispatch levels manually, or via preset date and time to send pre-configured responses for heightened levels of activity |
| M |
SECURITY
| 208. |
| Allow access to information based on passwords |
| M |
| 209. |
| Support role-based authentication and authorization |
| M |
| 210. |
| Apply appropriate edits to all entered data to ensure data integrity and maintain activity logs and audit trails |
| M |
| 211. |
| Support Lightweight Directory Access Protocol (LDAP) to obtain directory information based upon the X.500 standard |
| County Protocol |
GENERAL
| 212. |
| An unlimited number of telephone numbers can associated with personnel |
| M |
| 213. |
| A "person" can be added to the unit when the person is on duty on the unit |
| M |
| 214. |
| The system administrator can specify the format for: |
| b. |
| Confirmation numbers (prescheduled calls) |
| M |
| f. |
| Rotation response numbers |
| M |
| 215. |
| The system administrator can specify the agency-defined number display to be: |
| a. |
| Base response number |
| O |
| b. |
| Master incident number |
| O |
| 216. |
| Can "cross-staff" units |
| M |
| 217. |
| When cross-staffing, the system administrator can determine if it is a single-direction or multiple-direction |
| O |
| 218. |
| When cross-staffing, the unit that is left in quarters is automatically placed in a status that indicates that the unit is not available |
| O |
GEOFILE MAINTENANCE
| 219. |
| The geofile contains the following information: |
| 220. |
| Contain a commonplace name file that the user can use for call entry rather than entering a street address |
| M |
| 221. |
| Contain a conversion table to convert street abbreviations into correct formats that match the feed from the 9-1-1 controller |
| M |
| 222. |
| Agency can enter and update all geofile data, including the physical address and X, Y coordinates |
| M |
| 223. |
| Support geofile creation and maintenance using an available mapping/GIS database based on the ESRI platform |
| M |
TABLE MAINTENANCE
| 224. |
| The data used to support system recommendations or decisions is maintained in agency-modifiable tables |
| M |
| 225. |
| The system administrator can define table access for each individual user |
| M |
| 226. |
| The system administrator grants a user access to all tables |
| M |
| 227. |
| Examples of common tables include but are not limited to: |
| b. |
| Call types and priorities |
| M |
| c. |
| Standard unit status plus the ability to input reasons for conditional availability |
| M |
| d. |
| Personnel (including emergency contact information and current assignment) |
| M |
| f. |
| Patrol and command area definitions |
| M |
TRAINING
| 228. |
| Provide a training environment that allows users to work normally within the system without affecting the production system |
| M |
| 229. |
| The training environment mirrors the production system so that the table values are the same. The following items are included the training environment: |
| a. |
| Agency type definitions (Law, Fire, EMS) |
| M |
| b. |
| Table definitions including unit names, recommendation patterns, premise information, personnel information, security permissions |
| M |
MAPPING
| 230. |
| Calls addresses entered into CAD (as opposed to those populated from the ANI/ALI controller) automatically plot on the map display |
| M |
| 231. |
| Calls are automatically removed from the map display when cleared from the CAD system |
| M |
| 232. |
| Users can create a call from the map |
| M |
| 233. |
| When creating a call from the map, the X, Y coordinates are pulled from the map and converted into an address. Both the X and Y coordinates and the address are populated into the CAD system. |
| M |
| 234. |
| The user can center the map on specific calls for service via the CAD user interface, without having to select any buttons on the map display |
| M |
| 235. |
| Integrated directly with the 9-1-1 CPE and be capable of capturing and extracting the pertinent information from the E9-1-1 data stream provided by the telephone company |
| M |
| 236. |
| Provide instantaneous call-plotting of wireline and wireless Phase I and Phase II calls on a digital map |
| M |
| 237. |
| Use ESRI Symbology® and support multiple locators so that user can display a street centerline layer, a GPS point layer, lakes layer, and other layers simultaneously |
| M |
| 238. |
| Display map data in geo-database format without conversion (unless required based on projection data) |
| M |
| 239. |
| Display different map data sets with different map projections without conversion as long as projections are the same (such as aerials and centerlines) |
| M |
| 240. |
| Use a polygon layer to display Emergency Service Number (ESN) |
| M |
| 241. |
| Built on ESRI’s ArcGIS Engine |
| M |
| 242. |
| Built on a Microsoft .NET framework |
| O |
| 243. |
| Support MXD project files |
| O |
| 244. |
| Support display of all active 9-1-1 calls at all answering positions in a multiple workstation environment |
| M |
| 245. |
| Support connection to a network for simultaneous display of 9-1-1 ANI/ALI data in a multiple workstation environment |
| M |
| 246. |
| Display all incoming 9-1-1 calls prior to answer as well as calls answered by other users at different workstations within the Public Safety Answering Point (PSAP) |
| M |
| 247. |
| Plot addresses (ALI) with both standard and non-standard street designators to a map that contains standard street designators. Example: “AVE” and “AV” map “AVE”. |
| M |
| 248. |
| Display the rebid functionality with ALI |
| M |
| 249. |
| Update call location after a repeat ALI |
| M |
| 250. |
| Support the addition of other software modules (AVL, map maintenance, and ENS) |
| M |
| 251. |
| Support integration with Pictometry technology to utilize the Pictometry application within the CAD system |
| M |
| 252. |
| Read many supporting GIS layers, formats, projections, and coordinate systems |
| M |
| 253. |
| Support the addition of dynamic map services such as weather maps, fire locations, and satellite imagery |
| M |
| 254. |
| Create multiple ad hoc virtual boundaries or geographic areas on the map to set up geofencing alerts |
| M |
| 255. |
| Record when incidents or units have left/entered a user-created geofence and alert users |
| M |
| 256. |
| Able to specify geofence boundaries for the following statuses: |
| b. |
| At scene second location |
| M |
| 257. |
| Able to notify the user when a unit has: |
| a. |
| Moved 'x' miles/km away from an incident |
| M |
| b. |
| Moved 'x' miles/km from the transport destination |
| M |
PHASE I and PHASE II WIRELESS COMPLIANCY
| 258. |
| Wireless Phase I and Phase II mapping compliant |
| M |
| 259. |
| Display Phase I and Phase II wireless callers on the map to show their location |
| M |
| 260. |
| Zoom to and highlight the tower and cellular sector of an incoming wireless Phase I 9-1-1 call when it is answered by geocoding to the tower address and capturing the cell sector information from the ALI |
| M |
| 261. |
| Display location and list X, Y coordinates used to determine the callers’ position for Phase II wireless calls |
| M |
| 262. |
| Geo-validate the x/y coordinate for Phase II wireless calls |
| M |
| 263. |
| Provide emergency responders a standard locatable address derived from the centerline in addition to the X, Y coordinates during a Phase II call |
| M |
| 264. |
| Provide emergency responders a standard locatable address derived from the x/y coordinates for a Phase II wireless call |
| M |
SYSTEM CONFIGURATION
| 265. |
| The system administrator can add any set of features to the display and setup with desired symbols, text, selection method, and coordinate system |
| M |
| 266. |
| Provide the system administrator a customizable list of preset map view layers that can be accessed by the user |
| M |
| 267. |
| System administrator can configure the main map view to display multiple map views for either common or different map layers |
| M |
| 268. |
| System administrator can set different preset zoom levels for each map displayed when an E9-1-1 call is received or an address is manually located |
| M |
| 269. |
| System administrator can configure a different map view for each agency type |
| M |
| 270. |
| System administrators can specify jurisdictional, address information as well as response plan assignments to either the right or left side of the street for ultimate control in areas that border neighboring jurisdictions |
| M |
PREMISE INFORMATION, IMAGE LIBRARY
| 271. |
| Support map features linked to one or more external documents such as Microsoft Word documents, PDF files, and TIFF images to quickly retrieve burn permits, event information, building plans, site photos, etc., based on attributes in a map feature and the file name |
| M |
| 272. |
| Store and retrieve premise information (JPEG, TIFF, PDF, MR SID) linked to a geographical location or address |
| M |
| 273. |
| Premise database is built and maintained by the system administrator and viewable by the users |
| M |
| 274. |
| Store digital images |
| M |
MAP WINDOW FEATURES
| 275. |
| User can resize the maps by clicking and dragging the map to the desired size |
| M |
| 276. |
| User can expand the map to the full screen size with the click of a mouse |
| M |
| 277. |
| Include a standard set of user tools accessible on the main user interface |
| M |
TOOLS/FUNCTIONS
| 278. |
| Provide zoom-in, zoom-out, and pan capabilities in the map browser |
| M |
| 279. |
| Zoom-in to the extent of a “click-and-drag” defined box |
| M |
| 280. |
| Measure the distance from point A to point B |
| M |
| 281. |
| Calculate the cumulative distance from point-to-point-to-point, and beyond |
| M |
| 282. |
| Display distances in multiple formats (e.g., feet, miles, and meters) |
| M |
| 283. |
| Display coordinates in decimal degrees; degrees/minutes/seconds; degrees/decimal/minutes |
| M |
| 284. |
| Provide a status bar that displays information about the current mouse pointer location |
| M |
| 285. |
| The system administrator configures the status bar to show X, Y; UTM or MGRS notations |
| M |
| 286. |
| The information displayed on the status bar includes the zoom level and coordinates in decimal degrees, coordinates in degrees/ minutes/ seconds, coordinates in degrees/decimal/minutes |
| M |
| 287. |
| Print the active screen to a connected printer or plotter |
| M |
| 288. |
| Drill down through map layers and display the information contained in the multiple layers |
| M |
| 289. |
| Perform a query of map layers |
| M |
| 290. |
| Automatically allow for differing levels of map data detail based on the zoom level. For example, neighborhood streets, fire hydrants, and other detailed information are displayed when zoomed into a local area. Only freeways and major roads are displayed when viewing a large area. |
| M |
| 291. |
| Able to turn map layers off and on. The system administrator configures the list of user-controlled layers, assignable by individual or group. |
| M |
| 292. |
| Provide an information tool to retrieve and display all attributes for a user-selected feature |
| M |
| 293. |
| Depict “entity” boundaries, such as school campuses |
| M |
| 294. |
| Search map layers to find closest features to a location (fire hydrants, fire departments, driveways, EMS departments) |
| M |
| 295. |
| Enter two street names and have the map display the intersection of the streets |
| M |
CALL DISPLAY FEATURES
| 296. |
| Geographic coordinates of the current mouse position in latitude/longitude (degrees, minutes, and seconds and decimal degrees) as well as UTM and US State Plane, depending on user needs |
| M |
| 297. |
| Labels for attributes of a layer |
| M |
| 298. |
| Labels for multiple attributes in the same layer |
| M |
| 299. |
| Manually entered latitude/longitude coordinates |
| M |
| 300. |
| Change unit icons by status and incident icons by priority |
| M |
| 301. |
| Automatically clear call icons from the map after the incident has closed |
| M |
QUERY/SEARCH FUNCTIONS
| 302. |
| Generate the closest possible address or intersection to the latitude/longitude coordinates (X, Y) on a Phase II call (reverse geocoding) |
| M |
| 303. |
| Accommodate potential street aliases for all street names and address searches |
| M |
| 304. |
| User can search by layer |
| M |
| 305. |
| User can search by multiple layers |
| M |
| 306. |
| User can search by physical address to pinpoint caller’s exact location on the map |
| M |
ROUTING
| 307. |
| Generate routes and driving directions between two locations either via mouse click selection or by entering a “to” and “from” address |
| M |
| 308. |
| Provide advanced routing capabilities, including: |
| a. |
| Use of routing data to determine the most appropriate unit for dispatch |
| M |
| b. |
| Route around restricted barriers, maintain road impedances when performing the route calculation |
| M |
GEO-VALIDATION
| 309. |
| Suggest address matches based on the information supplied by the user |
| M |
| 310. |
| Query internet based search engines for address information such as Google or Bing |
| M |
| 311. |
| Upon execution of an internet address search, use a hotkey or mouse click to select an option from the internet address search results |
| M |
| 312. |
| Support address points |
| M |
| 313. |
| In the geo-validation algorithm, display address options with block range, street name, city, building, and apartment in the search results |
| M |
| 314. |
| User can search more results than initially returned |
| M |
| 315. |
| Upon selection of an address, display a thumbnail map on the call taking screen indicating the location of the address selected |
| M |
RMS INTERFACE
| 316. |
| Can assigning RMS incident numbers |
| O |
| a. |
| Can assign case numbers at any point during the call for service |
| M |
| b. |
| Maintain a unique number mask for each department |
| M |
| 317. |
| Incident data can be transferred to the agency records section for its use. The following data is available for transfer: |
| e. |
| Location of incident |
| M |
| 318. |
| Automatically transfer incident data as an incident report number is assigned and at the time of final disposition of the call for service |
| M |
III. MOBILE DATA SYSTEM
| MOBILE DATA SYSTEM (MDS) SPECIFICATIONS |
| MANDATORY = M |
DESIRED = D
OPTIONAL = O
VENDOR COMPLIANCE
(USE
CODE KEY)
VENDOR COMMENT
MOBILE CLIENT MODULE
GENERAL FUNCTIONALITY
| 1. |
| User can write comments in the unit log |
| M |
| 2. |
| All comments recorded in the unit log are available for viewing from the CAD system |
| M |
| 3. |
| Date- and time-stamp all comments recorded in the unit log |
| M |
| 4. |
| User can search historical CAD calls |
| M |
| 5. |
| User can view call times for all calls they have been assigned to |
| M |
| 6. |
| User can view a list of all calls they are assigned to |
| M |
| 7. |
| User can view narratives for calls they are not assigned to |
| M |
| 8. |
| Units can be assigned to multiple calls at the same time |
| M |
| 9. |
| User can assign themselves to the stacked calls in any order |
| M |
| 10. |
| User can add dispositions to calls |
| M |
| 11. |
| CAD and Mobile users can access the BOLO file |
| M |
| 12. |
| User can search the BOLO file |
| M |
| 13. |
| Automatically search the BOLO file when the user enters a license plate into the system |
| M |
| 14. |
| Provide function keys for frequently used actions |
| M |
| 15. |
| Provide hotkeys to access additional actions |
| M |
| 16. |
| Designed for a touchscreen computer |
| M |
| 17. |
| Send a photograph to all users |
| M |
| 18. |
| Send messages all users |
| M |
| 19. |
| Mobile users can view, edit and add supplemental information to any call for service |
| M |
| 20. |
| Any supplemental information entered in the mobile client is synchronized with CAD in near real time |
| M |
| 21. |
| Any supplemental information entered in CAD is synchronized with mobile client in near real time |
| M |
| 22. |
| Mobile users can perform the following searches from supplemental information in the existing mobile search query: |
| 23. |
| System administrator configures triggers for banner-type event notification |
| M |
| 24. |
| Notify users of an event |
| M |
| 25. |
| Mobile users can take action from the notification |
| M |
| 26. |
| Automatically status units based on their geographic location |
| O |
| 27. |
| Mobile user can activate mobile functions verbally (voice recognition) and receive results back audibly from the computer |
| O |
| 28. |
| Provide the mobile user audible results pertaining to the incident information screen |
| O |
| 29. |
| Provide the mobile user audible results pertaining to the records check results screen |
| O |
SECURITY
| 30. |
| In accordance with CJIS policy 5.1 |
| M |
| 31. |
| Pass mobile users credentials to the FBR application, eliminating the need to re-enter user credentials into FBR |
| M |
DISPATCH
| 32. |
| Audible alert when a new call is assigned |
| M |
| 33. |
| Visual alert when a new call is assigned |
| M |
| 34. |
| Present the following information on a single screen when a new call is dispatched: |
| c. |
| Caller location (can be different from incident location) |
| M |
| f. |
| Additional units assigned |
| M |
| g. |
| Notification of previous call information |
| M |
| h. |
| Display of driving directions |
| M |
| i. |
| Notification of subjects on the call |
| M |
| j. |
| Notification of vehicles on the call |
| M |
| k. |
| Notification of fire pre-plan |
| M |
| 35. |
| Updated as information is updated in the CAD system |
| M |
| 36. |
| Audible alert as information is updated in the CAD system |
| M |
| 37. |
| Automatically display the call location on a map upon dispatch |
| M |
| 38. |
| User can update the following statuses with a single action: |
| d. |
| Left scene for secondary location |
| M |
| e. |
| Arrived at secondary location |
| M |
| g. |
| Conditional availability (including reason and location) |
| M |
| 39. |
| User can update their status |
| M |
| 40. |
| User can add narrative to a call |
| M |
| 41. |
| User can add one or more dispositions to a call |
| M |
| 42. |
| User can supplement a dispatched call with additional comments, unit notes, or any miscellaneous data by use of the command line or the call screen |
| M |
OFFICER-INITIATED CALLS
| 43. |
| Provide a button for creating a traffic stop |
| M |
| 44. |
| Provide a button for creating an officer-initiated call |
| M |
| 45. |
| Upon entry of a traffic stop or officer-initiated call, set the unit status to On Scene |
| M |
| 46. |
| When the user initiates a call, the data from the last query executed is available for use in the new call |
| M |
| 47. |
| User can add information on vehicles and subjects during entry of an officer-initiated call |
| M |
| 48. |
| Automatically send vehicle queries upon entry of an officer-initiated call |
| M |
| 49. |
| Automatically send person queries upon entry of an officer-initiated call |
| M |
| 50. |
| Can add a button to the main toolbar for officer-initiated calls |
| M |
| 51. |
| Can add a button to the main toolbar for traffic stops |
| M |
| 52. |
| User can dispatch themselves to a call already entered |
| M |
MESSAGING
| 53. |
| Can send messages to any user who is logged on to the system |
| M |
| 54. |
| Can send messages to multiple users simultaneously |
| M |
| 55. |
| Can send messages to users who are not logged on |
| M |
| 56. |
| Audible and visual alert when a message is received |
| M |
| 57. |
| Audible and visual message alert upon log-on |
| M |
| 58. |
| System administrator can set up groups to receive messages |
| M |
| 59. |
| User can message with any mobile system user or CAD system user |
| M |
| 60. |
| Log all chat messages |
| M |
| 61. |
| The email component can send, receive, and include attachments |
| M |
CALL QUEUE
| 62. |
| User can view all current calls from CAD |
| M |
| 63. |
| User can map the location of any call in the queue |
| M |
| 64. |
| User can view the narrative for any call in the queue |
| M |
| 65. |
| Divide calls into pending and assigned queues |
| M |
| 66. |
| Update the call queues automatically |
| M |
| 67. |
| Update the call queues upon changes rather than at predetermined intervals |
| M |
| 68. |
| User can filter call queues based on patrol area |
| M |
| 69. |
| System administrator defines and locks call queue filters |
| M |
| 70. |
| User can sort call queues by any value displayed in the queue |
| M |
| 71. |
| User can modify the column width of the displayed data |
| M |
| 72. |
| User can set column width and automatically save to local MDT |
| M |
| 73. |
| User can access the call log from the unit queue |
| M |
| 74. |
| User can view incident detail from any incident queue with one click |
| M |
| 75. |
| User can view an incident location on the map with one click from any queue |
| M |
| 76. |
| Update the call logs in real time |
| M |
UNIT QUEUE
| 77. |
| Sort units by status |
| M |
| 78. |
| Automatically update unit queues |
| M |
| 79. |
| Update unit logs in real time |
| M |
| 80. |
| Define and lock unit queue filters |
| M |
| 81. |
| User can view the narrative for any call in the queue |
| M |
| 82. |
| User can view the unit on the map with one click from the unit queue |
| M |
| 83. |
| User can sort unit queues by any value displayed in the queue |
| M |
| 84. |
| User can sort the order of the data displayed in the queue |
| M |
| 85. |
| User can modify the column width of the displayed data |
| M |
| 86. |
| User can access the unit log from the unit queue |
| M |
| 87. |
| User can map the location of any call assigned to a unit in the queue |
| M |
| 88. |
| System administrator can configure the update interval for the unit queues |
| M |
QUERY CAPABILITIES
| 89. |
| Automatic query to the following agency’s upon scanning a driver’s license: |
| 90. |
| Provide the following queries: |
| 91. |
| Automatically populate CAD with the following data entered from the mobile client: |
| 92. |
| User can view query results in their native format |
| M |
| 93. |
| Return Images (where applicable) in response to a Name query of: |
| c. |
| Jail Management System (JMS |
| O |
| 94. |
| Query the following RMS activities: |
| 95. |
| System administrators can set keywords that trigger a notification to other mobile and CAD users when a unit receives a hit |
| M |
| a. |
| This notification alerts the user of a hot return |
| M |
| 96. |
| Users can run the following checks to standard law enforcement databases (NLETS and NCIC), local RMS databases, and supplemental information |
| 97. |
| Users can automatically search NLETS, NCIC, local RMS databases and supplemental information with a single query |
| M |
| 98. |
| Mobile users can query on one or more of the three available law enforcement databases (NCIC, RMS, supplemental information) |
| M |
MESSAGE SWITCH MODULE
SUPPORTED PROTOCOLS
| 99. |
| Support the following protocols: |
| c. |
| G2/3/4 must be compatible with NetMotion® and Radio IP |
| M |
SECURITY
| 100. |
| Support CJIS security requirements |
| M |
| 101. |
| The system administrator can: |
| a. |
| Set a minimum password length |
| M |
| b. |
| Require the use of uppercase letters in passwords |
| M |
| c. |
| Require the use of special characters in passwords |
| M |
| d. |
| Require the use of numbers in passwords |
| M |
| e. |
| Require that users change their passwords after a defined interval |
| M |
| f. |
| Set the frequency for password re-use |
| M |
| g. |
| Set the number of unsuccessful logon attempts allowed before the user is locked out |
| M |
| h. |
| Lock a user’s account |
| M |
| i. |
| Log off a mobile client |
| M |
| 102. |
| Record unsuccessful logon attempts |
| M |
| 103. |
| Each mobile client device is provisioned with access to the system. The system will display an authorization error in the event of unauthorized access attempt. |
| M |
TECHNOLOGY
| 104. |
| Uses Microsoft SQL database |
| M |
| 105. |
| Uses Microsoft SQL reports |
| M |
| 106. |
| Integrate with Crystal Reports |
| M |
SYSTEM ADMISTRATOR FUNCTIONS
| 107. |
| The system administrator can send mobile client software updates to the mobile client devices |
| M |
| 108. |
| Mobile client software upgrades are automatically downloaded to the mobile client devices |
| M |
| 109. |
| Accommodate receipt of software updates through WiFi hotspots |
| M |
| 110. |
| Automatically switch from an 802.11 hotspot to a commercial wireless network without impacting the mobile client operations |
| M |
| 111. |
| The mobile client software automatically downloads and installs updates when available |
| M |
| 112. |
| Support manual mobile client requests for mobile client software updates |
| M |
| 113. |
| Software updates prompt the user to accept updates |
| M |
| 114. |
| Software updates download in the background of the application without interrupting use of the application |
| M |
| 115. |
| The system administrator can view all users logged into the mobile server in a printable output that includes the following: |
| a. |
| Device Registration ID |
| M |
| q. |
| Out of Vehicle Status |
| M |
| t. |
| Timestamp of CAD Status |
| M |
| u. |
| Incident ID (if incident assigned) |
| M |
| v. |
| Incident Number (if incident assigned) |
| M |
| w. |
| Destination Latitude/Longitude (if incident assigned) |
| M |
MAPPING MODULE
Geographic Information System (GIS)
| a. |
| A single-button traffic stop |
| M |
| b. |
| Easy-to-view display |
| M |
| c. |
| Large buttons for touchscreen |
| M |
| d. |
| Screen tinting options for different lighting environments |
| M |
| e. |
| Able to invert every color on the map to accommodate lighting condition variations in the vehicle |
| M |
| f. |
| Day mode to night mode to enable easy viewing of the mobile client |
| M |
| g. |
| Built on the Esri Map Objects® or Esri ArcGIS® map engine |
| M |
| h. |
| Support MrSID mapping types |
This is the start of the file's text. The full file is on GovTribe.
