Spreadsheet: 189e7500-2c3c-451b-8252-51033e8fccb9
Sheet: CAD

Spokane County Request for Proposals #P8705
Public Safety Information Systems Replacement Project
Computer Aided Dispatch Functional Requirements
 | General_CAD_Requirements
 | Call Taking
 | CAD_Mapping_Requirements
 | Automatic_Vehicle_Location__AVL
 | CAD_Dispatching
 | CAD_Unit_Management
 | CAD_Call_Management
 | Towed Vehicles
 | CAD_Call_Disposition
 | BOLOs
 | CAD_Communications_Supervisor_Support
 | CAD Reporting and Query Features
 | CAD_and_Mobile_Messaging
 | CAD_System_Admin
Item # | CAD Functional Requirements | Comply ( C) | Not Comply (N) | Alternative\Conversion (A) | Modification (M) | Third Party Add-On (T) | Comments
1 | General [NAME]
2 | Ability to handle multiple types of public safety agencies within the same jurisdiction:
3 | Law Enforcement
4 | Fire
5 | EMS
6 | Ability for authorized user to configure any CAD workstation to manage:
7 | Either call taking or dispatching functions
8 | Both call taking and dispatching functions
9 | Ability to perform all criticial dispatch functions from command line or funcation keys in addition to mouse funcationality
10 | Ability to comply with relevant NFPA standards (e.g., 1221, 1061, 1710) regarding installation, maintenance and usage of emergency services communications systems.
11 | Ability to sync the CAD application to a universal time source (currently satellite).
12 | Ability to comply with published NENA NG9-1-1 standards.
13 | Ability to comply with NIEM standards.
14 | Ability to provide dedicated fields to capture all CAD transactions in an audit log, including but not limited to:
15 | Additional units added to call
16 | Any change in unit location
17 | Any status change
18 | Call assigned to unit's call queue
19 | Call dispatched
20 | Call for service created (call entered into system)
21 | Call priority change
22 | Call received
23 | Call re-routed
24 | Call reviewed
25 | Call transferred to another agency
26 | Call transferred from E9-1-1 to CAD system
27 | Cleared from call
28 | Data Entry
29 | Geo-verification
30 | Incident closed
31 | Incident reopened
32 | Incident supplemented
33 | Incident level upgrade
34 | Incident level downgrade
35 | Incident updated
36 | Last-known unit location
37 | Location change
38 | Narrative changes
39 | Pre-empt (swap unit between incidents)
40 | Subsequent dispatcher reviews call
41 | Transferred to dispatcher (call entered)
42 | Unit receives call
43 | Unit status updates
44 | Ability to enable alternate terminal routing |  |  |  |  |  | Ex. A main dispatch terminal goes down; How to route any future messages (both system generated and manual)to a secondary terminal or backup center
45 | [NAME] to include (but not limited to):
46 | Ability to print CAD Indicent in batches
47 | By Incident
48 | By Type Code
49 | By Priority
50 | By User
51 | Ability to print a selcted area of the CAD incident
52 | Ability to select which\how many pages to print
53 | Ability to print complete CAD messages/mail
54 | Ability to print with funcation keys and\or mouse
55 | Ability to print in color
56 | Multi-Jurisdiction Capability
57 | Ability to accommodate multiple jurisdictions.
58 | Ability for a call-taker/dispatcher to manage multiple jurisdictions simultaneously.
59 | Ability to view incidents across disciplines.
60 | Ability to create a duplicate incident with identical information transferred from the call-taker to all relevant dispatch disciplines (e.g., car accident sends the call information to both law enforcement and fire)
61 | Ability to automatically transfer call information between disciplines as new information is added (e.g., as the law enforcement dispatcher is updating call information, that information is made available to the fire dispatcher working on the identical call) as defined by each agency.
62 | Ability to manually transfer call information between disciplines as new information is added (e.g., as the law enforcement dispatcher is updating call information, that information is made available to the fire dispatcher working on the identical call) as defined by each agency.
63 | Ability for the County to define which data elements (e.g., unit status, units responding, etc.) are transferred between disciplines working on the same call.
64 | Application User Interface
65 | Ability for each Agency to determine which window configuration options are configurable at the user level.
66 | Ability for users to customize window views, including, but not limited to:
67 | Font size
68 | Font colors
69 | Font type
70 | Window background color
71 | Window sizes
72 | Window locations
73 | Fields displayed
74 | Order in which fields are displayed
75 | Ability to save  windows configurations based on user IDs (e.g., not workstation-specific).
76 | Ability to maintain multiple windows configurations for each user.
77 | Ability to maintain window configuration settings during upgrades.
78 | Ability to allow a return to system default settings.
79 | Ability to perform commands using any of the following methods:
80 | Agency-defined function keys
81 | Agency-defined shortcuts
82 | Command lines
83 | Toolbar
84 | Keyboard
85 | Mouse click
86 | Ability to execute any CAD function using the keyboard (list exceptions).
87 | Ability to execute any CAD function using the mouse (list exceptions).
88 | Ability to provide type ahead capability such that the user can continue entering data while the system is processing a previous transaction.
89 | Ability to display system messages without affecting work in progress.
90 | Ability to minimize or maximize any activity screen.
91 | Ability to have multiple windows open at the same time.
92 | Ability to tile or cascade multiple windows on screen.
93 | Ability to provide multiple command lines.
94 | Ability to create a new command line with a single keystroke.
95 | Ability to link a command line to a distinct incident.
96 | Ability to enter commands in any order on the command line.
97 | Ability to enter more than one command on a single command line.
98 | Ability for CAD system to support multiple command sets.
99 | Ability for narrative fields to have the following attributes:
100 | Unlimited number of characters (if limited, note the maximum characters permissible)
101 | Word wrap
102 | Ability to use arrow and tab keys to scroll within a window.
103 | Ability to display one or more status windows at the same time.
104 | Ability to provide a spell check utility.
105 | Ability to support copy and paste functionality.
106 | Call Taking
107 | [NAME]
108 | Ability to receive call data from:
109 | E9-1-1 phone system
110 | Non-emergency 10 digit phone numbers
111 | Private alarm companies
112 | Automated Secure Alarm Protocol
113 | IP-based sources
114 | NG E9-1-1 phone system
115 | Call Data Entry
116 | Ability for users to use either preformatted screens or command lines for incident entry.
117 | Ability to provide dedicated fields to capture all incoming call information from the E9-1-1 system, including, but not limited to:
118 | Caller name
119 | Caller telephone number
120 | Caller address/location calling from
121 | Incident location
122 | Alternate telephone number
123 | Cellular phone service provider
124 | Phase I or Phase II indication
125 | X/Y coordinates
126 | X/Y/Z coordinates
127 | Lat/Long coordinates
128 | Text messages (assuming phone system is NG9-1-1 capable)
129 | IP address (assuming phone system is NG9-1-1 capable) [note the IP version number the system is compliant with in the "comments" section]
130 | TTY conversation
131 | Any other information captured by the E9-1-1 system
132 | Ability to attach multimedia messages (MMS), including videos or pictures taken by citizens, to a call.
133 | Ability to extract files (e.g., videos, images, etc.) from the CAD system and make it available for email via attachment.
134 | Ability to transfer all call reporting party information (e.g., name, phone number, address) from E9-1-1 phone system into CAD application with a function key.
135 | Ability to transfer all call reporting party information (e.g., name, phone number, address) from E9-1-1 phone system into CAD application automatically.
136 | Ability for each agency to determine how E9-1-1 phone system information is transferred into the CAD (i.e., automatic or via function key).
137 | Ability to enter standard vehicle information in defined fields and record the entered information as part of the incident record.
138 | Ability to enter suspect information in defined fields and record the entered information as part of the incident record.
139 | Ability to generate an incident from a previous incident.
140 | Ability to generate an incident from a previous incident across agencies (e.g., Law Enforcement to Fire and vice versa).
141 | Location Capture
142 | Ability to receive geographic coordinates from a cellular telephone carrier.
143 | Ability to relate X/Y coordinates to an actual address.
144 | Ability to transform X/Y coordinates to a map for display.
145 | Ability to relate Lat/Long coordinates to an actual address.
146 | Ability to transform Lat/Long coordinates to a map for display.
147 | Ability to relate X/Y/Z coordinates to an actual address.
148 | Ability to transform X/Y/Z coordinates to a map for display.
149 | Ability to capture incident location separately from caller location.
150 | Ability to enter a location for an event by the following methods:
151 | Street address
152 | Block number or address range
153 | Commonplace name
154 | Landmark
155 | Intersecting street names
156 | X/Y coordinates
157 | Lat/Long coordinates
158 | X/Y/Z coordinates
159 | Point and click on a map
160 | Ability to suggest locations based on type-ahead capabilities for:
161 | Street addresses
162 | Intersections
163 | Ability to restrict type-ahead capabilities based upon:
164 | Agency
165 | User
166 | Ability to type in either street first when entering intersections.
167 | Ability to support the following when entering location information:
168 | Drop down menus
169 | Partial identifier search
170 | Aliases/Monikers
171 | Ability to save intersections as identical address points regardless of order of streets entered (e.g., 1st/Main same as Main/1st).
172 | Ability to enter addresses on one line.
173 | Ability for system to automatically parse address data into address data fields including:
174 | Street number
175 | Street name
176 | Street prefix
177 | Street suffix (NW, SW, NE, SE)
178 | Street type (Av, [NAME], Bd, "None")
179 | Unit type
180 | Unit number
181 | City
182 | County
183 | State
184 | Road classification
185 | Ability to accept spelled numbers (e.g., one, twenty, first).
186 | Ability to transfer caller location information into incident location fields.
187 | Ability to transfer incident location information into caller location fields.
188 | Location Verification
189 | Ability to verify any address entered into the system (e.g., updated field personnel locations, field personnel-initiated incidents, etc.).
190 | Ability to modify incident location at any time during the call.
191 | Ability to support Phase I wireless location validation from cellular callers.
192 | Ability to support Phase II wireless location validation from cellular callers.
193 | Ability to support NG9-1-1 location data.
194 | Ability to use the ALI reported location address for address verification.
195 | Ability to notify dispatcher if multiple street addresses/street names/intersections with the same names are found in geofile.
196 | Ability to offer a list of address options if multiple similar addresses/intersections/street names are found in geofile.
197 | Ability to display closest address matches based on:
198 | Block ranges
199 | Building name
200 | Business name
201 | Premise name
202 | Common place names
203 | Intersections
204 | Phonetic spelling
205 | Soundex
206 | Street name
207 | Ability to display an unlimited number of common place names during the address verification process.
208 | Ability to translate call location to appropriate public safety geographical boundary (e.g. district, beat, sector, etc.).
209 | Ability to translate alias names to actual street names or addresses.
210 | Ability to display, on a map the incident location in relation to other active incidents on the map during the incident entry process.
211 | Ability to display geofile data when location is validated.
212 | Ability to manually override address if not verified by geofile.
213 | Ability to log all locations that fail geofile validation.
214 | Ability to create a report of all overridden geoverified locations.
215 | Ability to manually override and correct address/location presented in CAD incident without correction affecting address/location stored in geofile.
216 | Ability for notification of correction to be automatically generated and sent to geofile administrator whenever a user manually overrides and corrects an address/location.
217 | Ability for the notification of correction to capture the following:
218 | Address/location information as presented (ANI/ALI information)
219 | Address/location data as corrected by the user
220 | Date/time of report
221 | User ID
222 | Ability to perform address verification manually without creating an event.
223 | Call Classification and Prioritization
224 | Ability to provide an option to generate automatic notifications to appropriate personnel upon entry of Agency-defined call types. [If this functionality can be provided, describe how the message can be sent to the appropriate personnel in the "comments" section.]
225 | Ability for system to automatically enter the appropriate Agency-defined priority for each new incident based on call type.
226 | Ability to override incident priority.
227 | Ability to allow the authorized user to manually upgrade or downgrade the system-assigned priority.
228 | Ability for dispatcher to change call type without impacting active call data.
229 | Incident Initiation
230 | Ability to initiate an incident from the input of location and type code.
231 | Ability to input all call and narrative information on one screen.
232 | Ability to display a blank form for entering new incidents with a single keystroke, [NAME] click or function key upon initiation of a CAD incident.
233 | Ability to copy an existing incident to create a new incident at the same location.
234 | Ability to open and view multiple incident entry windows.
235 | Ability to cascade/tile multiple incident entry windows.
236 | Ability to enter incidents using:
237 | Standard call entry screen form
238 | CAD command on a command line
239 | Map by clicking on a location
240 | Duplicate Call Management
241 | Ability to automatically identify potential duplicate calls based on:
242 | Incident/type code
243 | Agency-defined proximity
244 | Agency-defined time parameter
245 | Caller name
246 | Ability to display proximity calls on a map (e.g., to assist dispatchers in identifying possible duplicate calls).
247 | Ability to include recently closed incidents in the potential duplicate call identification process.
248 | Ability for system administrator to define "recently closed" through a configuration parameter (e.g., time period).
249 | Ability to manually identify a duplicate call and then combine with primary call.
250 | Ability to notify call taker when duplicate calls are combined.
251 | Ability, when calls are combined, for the previous call numbers to be automatically updated with the new primary call number.
252 | Ability to provide the dispatcher with the following information about possible duplicate incidents:
253 | Incident details
254 | Incident location
255 | Incident status
256 | Incident type
257 | User-defined proximity to current incident
258 | Caller phone number
259 | Ability for the dispatcher to do any of the following if a CAD incident is determined to be a duplicate call:
260 | Add to the original incident record a second complainant with complete complainant information and additional incident comments
261 | Cancel the call
262 | Close a duplicate incident and cross-reference it to the original CAD incident
263 | Create an entirely new incident using existing address data
264 | Ability to filter duplicate calls out of reports.
265 | Hazard and Premise Information Retrieval
266 | Ability to automatically initiate a search for hazards and premise information, upon address verification, based on:
267 | Address
268 | Block range
269 | Current business name
270 | Historic business name (unlimited)
271 | Common place names
272 | Intersections
273 | Ability for automatic search to include the following databases:
274 | Law Enforcement RMS
275 | Fire RMS
276 | Ability to attach any premise or hazard information to a CAD call.
277 | Ability to attach any premise or hazard information to an individual.
278 | Ability to automatically display previous calls for service at the verified location.
279 | Ability to provide an alert to the call-taker/dispatcher when an agency-defined incident type occurred at the verified location within its history (e.g., violent crime)
280 | Ability to display the number of previous calls at a location.
281 | Ability for map to display all known hazards within an agency-defined radius.
282 | Incident Scheduling
283 | Ability to enter incidents scheduled for dispatching at a later time, maintaining the original time of entry.
284 | Ability to modify incidents scheduled for dispatching at a later time, maintaining the original time of entry.
285 | Call Routing
286 | Ability to send call for service to appropriate controlling dispatcher based on:
287 | Location of incident
288 | Agency type (e.g., law enforcement or fire)
289 | Both location and agency type
290 | Dispatch Group
291 | Ability to manually designate (or override automatic routing recommendation) to which console a call will be sent.
292 | CAD Mapping Requirements
293 | Ability for mapping functionality to be integrated into CAD application.
294 | Ability to select multiple map layers for display, limited only by the number of available map layers.
295 | Ability to integrate streaming video from multiple sources with CAD maps in real-time or near real-time
296 | Ability to view on map the locations of:
297 | Incoming 9-1-1 caller
298 | Incident location during address verification.
299 | All pending and active 9-1-1 calls
300 | Units based on AVL or last known locations
301 | Ability to display an address on the map when it is entered into the command line.
302 | Ability to dynamically display location of NG9-1-1 caller in real-time.
303 | Ability to pull up a call for service and have it automatically display on the map.
304 | Ability to select a unit and have its last known location automatically display on the map.
305 | Ability to zoom in and center map display on:
306 | Incident location during address verification.
307 | Any unit
308 | CAD incident in active window
309 | Last known location of a selected unit (AVL or unit status)
310 | Vehicle in pursuit mode
311 | Vehicle activating emergency button
312 | Ability to support plume modeling and create model as a GIS layer.
313 | Ability to support fire modeling and create model as a GIS layer.
314 | Ability to support modeling software (e.g., CAMEO/ALOHA).  Specify which software supported in the "comments" section.
315 | Ability to utilize color, text, and/or symbols to distinguish status of unit.
316 | Ability to project anticipated response times between two points on a map.
317 | Ability for operational user to close streets by clicking on a specific area (e.g., street, hundred block area) from the CAD map.
318 | Ability to adjust routing recommendations based on closed streets.
319 | Ability for user to define an expected duration for street closures.
320 | Ability to alert user when the expected duration for a street closure has expired.
321 | Ability to push closed street information to mobile computers.
322 | Ability to select vehicles to display on map by user-defined criteria including, but not limited to:
323 | Incident number
324 | Incident type
325 | Response area (e.g., district, beat, etc.)
326 | Station
327 | Status
328 | Type
329 | Unit ID
330 | Geofile Administration
331 | Ability to accommodate an unlimited number of map layers.
332 | System is compatible with ESRI products.
333 | System supports all current ESRI products and version (if not, specify which products and versions are supported within the comments section).
334 | System supports all ESRI data formats (if not, specify which formats are supported within the comments section).
335 | Vendor is a certified ESRI-partner.
336 | Ability to support standard ESRI mapping functions.
337 | Ability to support a map layer for aerial spatial images.
338 | Ability to cross-reference map with internet mapping services (e.g., Google maps, County [NAME], etc.)
339 | Ability to support a map layer of oblique aerial imagery.
340 | Ability to add geofile layers as needed.
341 | Ability to support compressed imagery formats (e.g., MrSID)
342 | Ability to determine which map layers are available for each application  (e.g., CAD, Mobile, RMS).
343 | Ability to change reporting boundaries (e.g., areas, beats, districts, etc.).
344 | Ability to update the system with a new geofile without system downtime.
345 | Ability to update the system with a new geofile without system performance degradation.
346 | Ability to support high resolution imagery.
347 | Ability to test new geofile updates "offline" for accuracy and errors, prior to updating the "live" geofile.
348 | Ability for geofile updates to be recognized without requiring logging off and logging back on to the system.
349 | Map Data
350 | Ability to support the following location fields, including, but not limited to:
351 | Apartment building name
352 | Apartment number (e.g., [NAME], #5, 2D, D2)
353 | Block range
354 | Business name
355 | Address number
356 | City
357 | Civic associations (e.g., COPS areas, neighborhoods, community names)
358 | Common place name
359 | County
360 | Intersections
361 | On ramps, off ramps, exit numbers (including direction)
362 | Prefix
363 | Mile markers (including numbers and direction)
364 | Reporting area (e.g., district, beat)
365 | Street abbreviation
366 | Street name
367 | Street type
368 | Suffix
369 | Lat/Long
370 | X/Y coordinates
371 | X/Y/Z coordinates
372 | Ability to add a location field attribute without requiring vendor intervention.
373 | Ability to associate geofile data with the following:
374 | Address
375 | Reporting area (e.g., district, beat, jurisdiction, etc.)
376 | Census tract
377 | Entire common place or business name and aliases
378 | High and low cross streets
379 | Closest organizations (e.g., schools, churches, civic associates, etc.)
380 | County-defined
381 | Map Functionality
382 | Ability to turn map layers off and on.
383 | Ability to modify layer transparency.
384 | Ability to force adherence to user-defined addressing standards (e.g., abbreviations, directions, etc.).
385 | Ability to attach files to addresses (e.g., apartment maps, photos, aerial images).
386 | Ability to attach premise information (e.g., hazards) to addresses.
387 | Ability to print map at any time.
388 | Ability to click on a location on a map and pull up any supplemental information (e.g. fire pre-plan, hazards, incident history) associated with that location.
389 | Ability to click on a location on a map and pull up any supplemental information associated with an Agency-defined parameter around the location (e.g., polygon search).
390 | Ability to display flags on locations containing additional information (e.g. fire pre-plans, hazards, incident history).
391 | User Interface
392 | Ability to allow users to customize map views including, but not limited to:
393 | Font size
394 | Level of detail
395 | Screen size
396 | Ability for user to update/modify map displays (e.g., preset default zoom levels and views).
397 | Ability for users to define which map layers are displayed.
398 | [NAME]
399 | Ability to use a mouse to "click on" a point at any zoom level and have the following information displayed:
400 | Street name (including alias)
401 | Street type
402 | Block number or address range
403 | Address
404 | X/Y Coordinates
405 | Lat/Long
406 | X/Y/Z Coordinates
407 | Ability for the user to define which street information is displayed, when clicking on a map location.
408 | Ability to provide the following map navigation functionality:
409 | Pan from given area to adjacent area
410 | Return back to previous view
411 | Zoom in on area for enhanced detail
412 | Zoom out of an area
413 | Move up and down
414 | Move left and right
415 | Ability to zoom to relevant map location by searching on available map layer information including, but not limited to:
416 | Common place name
417 | Hydrants
418 | Address
419 | Address range
420 | Incident number
421 | Intersection
422 | Landmark
423 | X/Y coordinates
424 | X/Y/Z coordinates
425 | Lat/Long
426 | Parcel owner
427 | Street names
428 | Automatic Vehicle Location (AVL)
429 | Ability to support the use of a continuous, real-time AVL system via a CAD interface.
430 | Ability to turn AVL on/off by:
431 | Agency
432 | Unit
433 | Ability to default to Agency-defined defaults for dispatching when AVL is unavailable.
434 | Ability to automatically mark a unit on-scene when it comes within a certain number of feet of the incident location.
435 | Ability for each agency to define what constitutes on-scene.
436 | Ability to prevent unit from updating status to on-scene if unit is not actually on-scene according to AVL data.
437 | Ability to log the specific X/Y coordinate from where the unit was dispatched prior to responding to an incident.
438 | Ability for system to convert X/Y coordinates to nearest cross-streets.
439 | Ability to automatically log fire apparatus status as en route to a call upon exiting the station when responding to a call for service.
440 | Ability to configure which agency vehicles are displayed based upon responsibility (e.g., fire dispatcher sees only fire units)
441 | Ability to automatically refresh current vehicle location at Agency-defined intervals.
442 | Ability to color code units when connectivity is lost.
443 | Ability to recreate an incident within the CAD system identifying vehicle locations, including direction and speed.
444 | Dispatching
445 | General [NAME]
446 | Ability to dispatch both fire/EMS and law enforcement units from the same CAD application window.
447 | Ability to control both fire/EMS and law enforcement units from the same CAD application window.
448 | Ability to configure dispatching workstations based upon discipline.
449 | CAD Incident Retrieval
450 | Ability to alert a dispatcher to the arrival of a new incident.
451 | Ability to alert a dispatcher to the arrival of new incident information from the call taker.
452 | Ability to review each pending incident sequentially.
453 | Ability to keep incidents in pending queue indefinitely.
454 | Resource Recommendation
455 | Ability to automatically provide appropriate resource recommendations based on any combination of:
456 | AVL location
457 | Closest unit taking into account:
458 | Natural boundaries
459 | Obstacles
460 | Traffic
461 | Train crossings
462 | Speed limits
463 | Street network
464 | Street direction
465 | Equipment availability
466 | Jurisdiction responsibility
467 | Incident area (e.g., unique response for specific response area)
468 | Incident type
469 | Occupancy type (e.g. residential, office building, etc.)
470 | Pre-defined response plans (response area plan)
471 | Special conditions (e.g., heightened response)
472 | Type of units required
473 | Number of units required
474 | Number of personnel required
475 | Unit status
476 | Ability for each agency using the CAD system (i.e., [NAME] and Fire) to enable and disable agency-specific resource recommendations.
477 | Ability to support closest unit dispatching (AVL-based) that takes into account automatic aid based on pre-defined agreements.
478 | Ability to prioritize unit response based on incident type so that appropriate units are automatically recommended and/or dispatched in priority order.
479 | Ability to enable and disable agency-specific resource recommendations (e.g., specific response plan for Fire, specific response for Law Enforcement).
480 | Ability to re-recommend closest units (e.g., a new unit comes into service).
481 | Ability for system to update the unit recommendation if user makes relevant incident information changes (e.g., type, location, alarm level).
482 | Ability to record the unit recommendation as it was presented to the dispatcher, including when no units were available.
483 | Resource Determination
484 | Ability to bring up a list of special skills/equipment for:
485 | All personnel logged on
486 | A selected person
487 | Apparatus/vehicle
488 | Ability to display potentially available resources based on unit status:
489 | Assigned to a CAD call
490 | Assigned to a CAD call with a lower priority
491 | Unassigned
492 | Resource Dispatch
493 | Ability for dispatcher to select and assign/re-assign recommended units using any of the following methods:
494 | Command line entry
495 | Function key
496 | [NAME] (drag and drop onto map)
497 | Ability to preempt units on a call to respond to a different incident.
498 | Ability to designate a responding unit as primary unit.
499 | Ability to notify field unit when labeled as the primary unit.
500 | Ability to change the primary unit at any time.
501 | Ability to dispatch units by:
502 | Accepting the proposed application recommended units
503 | Selecting and dispatching units other than those recommended by the application
504 | Selecting some, but not all, of the recommended units
505 | Ability to log recommendation overrides in the audit trail (e.g., recommended units and dispatched units).
506 | Ability for CAD application to do the following upon dispatch:
507 | Assign the recommended or requested units
508 | Initiate alphanumeric paging
509 | Activate fire station alerting system
510 | Remove the incident from the pending queue
511 | Send the incident to the assigned unit's Mobile computer
512 | Send any applicable premise information
513 | Start the status timers
514 | Update the status display
515 | Ability to dispatch more than one unit at a time to the same call.
516 | Ability for dispatcher to assign a CAD incident to one or more units by "dragging and dropping" the units onto the CAD incident.
517 | Ability to assign a unit to an incident to which it was not originally recommended.
518 | Ability to dispatch to multiple types of telecommunications devices simultaneously including, but not limited to:
519 | Mobile computer
520 | Cell phone
521 | Pager
522 | Ability to configure the system to push out different information based on the receiving device (e.g., short message to alphanumeric paging device and full dispatch message to mobile computer).
523 | Ability to send dispatches to printers (e.g., "rip and run" printers in fire stations).
524 | Ability to send dispatches via email.
525 | Ability to provide sender notification that dispatches have been delivered to a specific device.
526 | Timers
527 | Ability to provide incident timers and alerts based upon Agency-defined parameters (e.g., type of incident, unit arrival time, priority status) and times.
528 | Ability to manually set incident timers and alerts.
529 | Ability for a user to create a custom timer specific to their workstation.
530 | Ability for a user to create a custom timer specific to the incident.
531 | Ability to display call timers on CAD screens.
532 | Ability for each agency to create its own automatic timers.
533 | Ability to alert operator to the expiration of the timer via:
534 | Audible alert
535 | Visual alert
536 | Ability for a user to enable/disable automatic timers.
537 | Ability to not require a user to acknowledge the expiration of a timer.
538 | Ability to record acknowledgement of timer alert.
539 | Ability to provide the operator of the following options when a status timer expires:
540 | Modify to new time value
541 | Reset to default value
542 | Delete the timer
543 | Field-Initiated Calls for Service
544 | Ability to enter field-initiated incidents (e.g., traffic stop).
545 | Ability to add additional units to a field-initiated incident.
546 | Ability to limit field-initiated calls to Agency-defined call types.
547 | Ability to verify addresses of field-initiated incidents.
548 | Ability for dispatcher to put a unit on a self-initiated activity and run the plate in one step.
549 | Ability to run multiple plates in a single step.
550 | Ability for field personnel to initiate an administrative incident (e.g., put units out on training or drills).
551 | Unit Assignment to CAD Incident
552 | Ability to update unit status to associate the dispatched unit or units with the CAD incident.
553 | Ability to take a unit off a call and reassign the unit to a new call via:
554 | Single command
555 | Drag and drop
556 | Ability to use one command to both dispatch and put "on scene" field personnel (e.g., if field personnel is "out with another unit").
557 | Call Stacking/Queuing
558 | Ability to hold an incident for a specific unit.
559 | Ability to prevent a held incident from any other unit assigning themselves to that call.
560 | Ability to notify field unit when a call is held for that unit.
561 | Ability to automatically notify the dispatcher of a held incident when the unit becomes available.
562 | Ability to hold more than one incident to a given unit or resource (call stacking).
563 | Ability for administrator to turn call stacking on and off.
564 | Ability to stack calls based on:
565 | Call Type
566 | Time of Call Received
567 | Priority
568 | User preference
569 | Ability to override any of the above to create a dispatchers queue.
570 | Call Preemption
571 | Ability to pull a unit off an incident and reassign the unit to a new incident.
572 | Ability to return CAD incident to the pending dispatch queue if all units are removed from an active incident.
573 | Ability to visually indicate a preempted call (e.g., color code).
574 | Ability to support a swap feature to allow two units to swap incidents with a single command.
575 | Ability to support a unit exchange command which allows the dispatcher to remove an assigned unit from an incident and assign a second unassigned unit to the first unit's incident.
576 | Unit Management
577 | Unit Placement in Service
578 | Ability for County to define an unlimited number of unit statuses.  If limited, indicate the maximum number in the comments section.
579 | Ability to support a change of quarters (minimum of three-way)
580 | Ability to log one or more units on-duty/off-duty with a single command.
581 | Ability to define a roster (e.g. squad, company, etc.).
582 | Ability to place all units in a previously defined roster on or off-duty with a single command.
583 | Ability to allow for single unit exceptions when placing a roster on or off duty.
584 | Ability to log a fire apparatus into service without tying individuals to the apparatus.
585 | Ability to identify fire units by special equipment (e.g., rescue tools, etc.).
586 | Ability to keep vehicles (e.g., fire apparatus) on duty (e.g., 24x7) and change personnel associated with the vehicles (e.g., on shift changes).
587 | Ability to designate a unit available for only certain types of calls.
588 | Ability for units to log themselves into or out of service.
589 | Ability to  prevent units from logging themselves into and out of service.
590 | Ability for units to log on to the system without being available for calls.
591 | Ability for units to indicate when they are available for calls.
592 | Ability for dispatchers to place multiple units (e.g., an entire squad or company) into "available for calls" status.
593 | Ability to add an individual to a unit at any time.
594 | Ability to add an individual to a unit and have the call history reflect that all those individuals were on the unit when arriving on scene (e.g., personnel did not log on until after arriving at scene)
595 | Ability to log locations of individuals from a unit responding to an incident (e.g., Officer A is located north of building, Officer B is located south of building - both Officers are part of the same single unit)
596 | Ability to remove an individual from a unit at any time.
597 | Ability to associate multiple individuals with a unit.
598 | Ability to associate skills with a unit.
599 | Ability to indicate a unit does not have a mobile computer.
600 | Ability to simultaneously clear field personnel from a call and log the personnel out of the system (e.g., for field personnel taking calls when off-duty).
601 | Ability to sign a unit on with temporary call sign (e.g., to indicate off-duty or on special assignment).
602 | Ability to track special assignments (e.g., working extra jobs):
603 | Assign officer to location
604 | Designate officer as not available to take calls
605 | Designate officer as on special duty
606 | Cross Staffing
607 | Ability to deploy an apparatus to an incident while simultaneously removing an apparatus from service based on cross-staffing.
608 | Ability to place both apparatuses back in service when personnel are available to staff the apparatus.
609 | Unit [NAME]
610 | Ability to modify unit availability regardless of status (e.g., on-scene, but available).
611 | Ability to display the following unit information:
612 | Battalion
613 | Beat
614 | Call type
615 | Cell phone
616 | Census tract
617 | Current incident number
618 | Current location
619 | Current status
620 | Elapsed time in status
621 | Last known location
622 | Logged onto Mobile (Y/N)
623 | Name
624 | Original location
625 | Radio ID
626 | Radio channel
627 | Special note or comments
628 | Station
629 | Unit ID/call sign
630 | Vehicle number
631 | Any information captured at logon
632 | Ability to dynamically (automatically update) display unit status data.
633 | Ability to sort displayed data by any unit information (e.g., station, shift, incident, unit, location, status, etc.).
634 | Ability to filter the units to be displayed in a single status monitor (e.g., by response area, discipline, type, status, out of service (mechanical), etc.).
635 | Unit Activity Tracking
636 | Ability to record all unit assignments.
637 | Ability to record all unit locations.
638 | Ability to record all unit status changes.
639 | Ability to record number of times a unit has been assigned as primary unit based upon a user-defined time frame.
640 | Ability to review unit status history within the CAD application.
641 | Ability to update location and note mileage for multiple stops.
642 | Ability to record multiple arrival times, including:
643 | [NAME] at a staging area
644 | Arrival at the incident location (e.g., room within a building)
645 | Arrival at the scene (e.g., general location)
646 | Arrival at patient
647 | Ability to record multiple units arriving:
648 | At one time (all at once)
649 | At different times
650 | Ability to place "at the scene" units that were not originally dispatched to the call.
651 | Ability for a dispatcher to change the location of a unit at any time while the unit is still assigned to an incident.
652 | Unit Clearance
653 | Ability to clear one unit from a CAD incident while allowing the other assigned units to remain on the call.
654 | Ability to clear all units simultaneously from a CAD incident.
655 | Ability to request user confirmation prior to clearing the last unit from a CAD incident.
656 | Ability to alert responding units when additional units are cleared from or added to a call.
657 | Ability to require a disposition to be entered prior to clearing the primary unit from a CAD incident.
658 | Call Management
659 | CAD Call Display
660 | Ability to monitor an unlimited number of incidents.
661 | Ability for a user to select an incident for continuous monitoring such that:
662 | Incident appears in a separate window
663 | All incident or unit activity, regardless of point of entry, is displayed in this window as it is recorded to the CAD database
664 | Ability to review incident information in reverse chronological order.
665 | Ability to display a window listing pending and holding incidents entered from any CAD workstation.  The following should be displayed:
666 | Response area
667 | Incident number
668 | Incident type
669 | Location
670 | Priority
671 | Status
672 | Time in status
673 | Time received
674 | Total elapsed time
675 | Ability for each agency to configure what information described above is displayed.
676 | Ability to sort active calls by:
677 | Response area
678 | Priority
679 | Time in status
680 | Time received
681 | Total elapsed time
682 | Ability for dispatcher to transfer management of all calls except one (e.g., a hot call) to another dispatcher.
683 | Ability to designate a single call (e.g., a hot call) to a single dispatch group, regardless of the number of units assigned to the call.
684 | Ability to initiate a perimeter command to generate a perimeter upon entry of a location and perimeter distance (e.g., set a 3 block perimeter around 300 Main St.).
685 | Ability for perimeter to automatically adjust based upon updated location information.
686 | Ability to generate perimeters via a drawing tool on the map.
687 | Ability to send suggested perimeter positions to a unit.
688 | CAD Incident Updates
689 | Ability to update the incident as new information is received.
690 | Ability for call takers to add information to a CAD incident after the incident has been routed to a dispatcher.
691 | Ability for agency-defined supplemental information entered by the call-taker to not automatically be transferred to the dispatcher.
692 | Ability for multiple call takers to provide input to a single call.
693 | Ability to visually distinguish information entered by each call taker (e.g., Call Taker A's font is in blue, Call Taker B's font is in red) into a single call.
694 | Ability to simultaneously notify dispatcher and dispatched units of updated information as configured by each agency.
695 | Ability for dispatcher screen to update automatically as new information is added to a call.
696 | Ability for the screen of anyone monitoring a call to update automatically as new information is added to a call.
697 | Ability to automatically record all CAD incident information changes in chronological order.
698 | Ability for system to automatically highlight changes made since last entry.
699 | Ability to attach NCIC returns to incident records.
700 | Ability to copy and paste NCIC returns into incident records.
701 | Ability for users to add supplemental information to closed incidents.
702 | Ability to notify call taker when they've added a supplement to a closed call.
703 | Reopening CAD Incidents
704 | Ability to reopen closed incidents.
705 | Ability to assign units to reopened calls.
706 | Ability for dispatchers to add comments to a CAD call record after the call is closed without reopening the incident.
707 | Ability for dispatchers to modify the final disposition of the CAD call record after the call is closed without reopening the incident.
708 | Ability for dispatchers to modify the call type of the CAD call record after the call is closed without reopening the incident.
709 | Ability for dispatchers to modify the dispatch group of the CAD call record after the call is closed without reopening the incident.
710 | Ability for each agency to determine what users may re-open calls.
711 | Ability for each agency to determine which data elements may be modified in a closed call.
712 | Hyperlinking and Cross-Referencing Calls
713 | Ability for dispatcher to hyperlink a field-initiated call to another incident.
714 | Ability to hyperlink active incidents.
715 | Ability to hyperlink closed incidents.
716 | Ability to hyperlink an unlimited number of related incidents (if limited, indicate the maximum number of hyperlinks)
717 | Ability to cancel a cross-reference or hyperlink.
718 | Ability to provide a field to cross-reference active incidents.
719 | Ability to provide a field to cross-reference closed incidents.
720 | Towed Vehicles
721 | Towing Vehicle Rotation List
722 | Ability to maintain a single list of multiple tow company contractors with different kinds of capabilities (e.g., asset seizure, evidence impound, etc.).
723 | Ability to provide tow module within a Mobile environment (based upon user permissions).
724 | Ability to support specific tow company lists for each agency.
725 | Ability for system to recommend a contractor based on the following:
726 | Contractor capabilities
727 | Vehicle location
728 | Position in contractor rotation list
729 | Ability to capture reason for exception when a contractor other than the one recommended is selected.
730 | Ability to record that a contractor was selected from the service rotation list.
731 | Ability to record contractor response.
732 | Ability to provide an archive of contractor responses.
733 | Ability to replace a contractor at the top of the rotation list when the dispatchers cancels the tow call out (e.g., through no fault of the contractor).
734 | Ability to attach tow request and response record to incident record.
735 | Ability to send tow company information to deputy in field (e.g., to prefill field reporting form).
736 | Ability to generate an automatic timer when a tow is requested (based on agency-defined timers).
737 | Ability to capture the response time of the towing vehicle.
738 | Ability to capture non-compliance of tow contract agreements (e.g., not responding within the contracted response time).
739 | Ability to generate a report identifying:
740 | Tow company
741 | Average Response Time
742 | Number of times of non-compliance response time
743 | Contractor responses
744 | Ability to de-activate/re-activate a towing company from the rotation list.
745 | Ability to temporarily remove a towing company from the rotation list and have that towing company automatically available at the conclusion of its temporary expiration.
746 | Ability to add/remove a towing company from the rotation list.
747 | Ability to store contact information for all tow companies within the rotation list.
748 | Ability for user to update the tow company's contact information.
749 | Ability to record "by request" tows (i.e., for tows requested by the individual that are not contracted by the County)
750 | Call Disposition
751 | CAD Incident Cancellation
752 | Ability to cancel an incident with a single command.
753 | Ability to generate a test call without generating a case number.
754 | Ability to automatically remove the incident from the pending or active incidents queue and add the disposition (e.g., cancelled) upon execution of a command canceling an incident.
755 | Ability to automatically clear all dispatched units from the incident upon incident cancellation (e.g. upon invoking the cancel command).
756 | Disposition Recording
757 | Ability for each Agency to define disposition codes.
758 | Ability for each agency to modify their disposition codes without requiring vendor intervention.
759 | Ability to filter disposition codes by agency (e.g., fire and law enforcement each have their own disposition codes).
760 | Ability to support an unlimited number of disposition types.
761 | Ability for each agency to define multiple disposition types for one incident.
762 | Ability to require a disposition code before an incident can be cleared.
763 | Ability for either dispatchers or field personnel to enter the disposition code.
764 | Ability to enter comments along with a disposition code (note the number of characters permissible in the "comments" section).
765 | Ability to reject a disposition if unsuitable for the incident type based on Agency-defined criteria.
766 | Ability to support multiple dispositions per incident per officer.
767 | Ability to prevent the disposition of a secondary unit from overriding the disposition of the primary unit.
768 | Ability when the primary unit is identified or changed after a disposition is entered, for the associated dispositions to update accordingly (e.g., change the secondary unit to the primary unit, the second unit's disposition now becomes the primary disposition).
769 | Report Initiation
770 | Ability to identify whether a report is required based on disposition code.
771 | Ability to transfer agency-defined call for service data to:
772 | Law Enforcement RMS
773 | Law Enforcement Field Reporting (e.g. to initiate a report)
774 | Electronic Patient Care Report
775 | Fire RMS
776 | Ability to initiate a report before an incident is closed (e.g., download data to Fire RMS).
777 | Ability to notify field personnel of all incidents requiring reports (e.g., reports necessary queue).
778 | CAD Incident Closure
779 | Ability to clear more than one selected unit from an incident while leaving one or more selected units on the incident.
780 | Ability to clear a single unit from an incident without clearing other assigned units from the incident.
781 | Ability to clear multiple units without closing the incident.
782 | Ability to require confirmation before closing a CAD incident (e.g., a message saying "Are you sure you want to close this incident?).
783 | Ability for each agency to configure whether or not a closed confirmation is required.
784 | Ability to change any call data before closing an incident.
785 | Ability to change an incident disposition after a call is closed.
786 | [NAME] Management
787 | Ability to identify station coverage deficiencies based on minimum staffing levels by apparatus type.
788 | Ability to identify station coverage deficiencies based on minimum staffing levels by apparatus capability.
789 | Ability to identify coverage deficiencies by agency defined parameters.
790 | Ability to recommend move-ups based on:
791 | Fixed station order
792 | Current vehicle location (e.g., AVL)
793 | Alarm levels
794 | Ability for dispatchers to:
795 | Accept move-up recommendations
796 | Override move-up recommendations
797 | Ability to reverse move-ups as apparatus clear calls.
798 | Ability to distinguish between assigned units and units in move-up or cover status.
799 | Ability to provide an alert when locations are nearing station coverage deficiencies.
800 | Ability for move-up recommendations to take into account units from neighboring jurisdictions.
801 | Ability for move-up recommendations to take into account the number of nearby units that are attending the incident and recommend units from farther away (e.g., Pull units from 5 miles away as opposed to 2 miles away to prevent a coverage "black hole").
802 | BOLOs
803 | Ability to create BOLOs (based upon level of security clearance).
804 | Ability to provide an audit trail for BOLOs.
805 | Ability for field personnel to create BOLOs.
806 | Ability to create defined BOLO receiving groups (e.g., law enforcement only, law and fire, etc.)
807 | Ability to associate a BOLO with a case number.
808 | Ability to provide the following fields for a BOLO record:
809 | Date issued
810 | BOLO expiration date
811 | Nature of the BOLO
812 | BOLO priority
813 | Subject name
814 | Case number
815 | Incident number
816 | Subject description
817 | Date of birth
818 | Known address or location
819 | Vehicle description
820 | Vehicle license plate
821 | Weapon (multiple)
822 | Known associates
823 | Last known location
824 | Contact Information
825 | Person issuing the BOLO
826 | Agency issuing the BOLO
827 | Additional information in free-form text field
828 | Ability to search for BOLO based upon any of the above-mentioned items.
829 | Ability to attach a file to a BOLO.
830 | Ability to embed a photo in a BOLO.
831 | Ability to embed a video in a BOLO.
832 | Ability to update a BOLO.
833 | Ability to associate a timer with a BOLO that notifies dispatch based on user-defined time frame.
834 | Ability to set time limits for BOLO retention.
835 | Ability to close a BOLO.
836 | Ability to modify a BOLO.
837 | Ability for user other than the BOLO author to modify the BOLO, based upon security level.
838 | Ability to designate groups or individuals to whom BOLOs should be sent.
839 | Ability to view history of recently created BOLOs.
840 | Ability to archive expired BOLO records.
841 | Ability to search expired BOLO records.
842 | Communications Supervisor Support
843 | Ability for a communications supervisor to monitor system configuration and current staffing (e.g., who is signed-on, at what position, and with what responsibilities).
844 | Ability for a CAD workstation to be configured as a supervisor workstation upon logon of a user with a CAD supervisor profile.
845 | Ability for a communications supervisor to monitor activity on any user workstation.
846 | Ability to generate statistical information from within the CAD application on all dispatcher activity including all incident management time parameters (time on hold, response time, etc.).
847 | Ability for an individual with defined security access to remotely take control of a workstation.
848 | Ability for all messages sent to and from a trainee to be available to the trainee's supervisor.
849 | Ability to allow two users to work on the same call simultaneously (e.g., to allow a trainer and trainee to work on the same call).
850 | CAD Testing/Training Environment
851 | Ability to support a CAD testing/training environment that mirrors the functionality of the CAD production environment.
852 | Ability for testing/training environment to support an unlimited number of incidents (if limited, indicate the maximum in the comments section).
853 | Ability to support a CAD testing/training environment that mirrors the configuration of the CAD production environment.
854 | Ability to visually distinguish testing/training environments from production environments.
855 | Ability to designate any production workstation as a training workstation based on user log on.
856 | Ability to designate any training workstation as a production workstation based on user log on.
857 | Ability for testing and training to occur without impacting the production environment.
858 | Ability to support a separate test E9-1-1 connection (or a canned script of E9-1-1 information).
859 | Ability to support a separate test mobile connection (or a canned script of mobile information).
860 | CAD Reporting and Query Features
861 | CAD Reporting and Analysis
862 | Ability to provide a native reporting tool that can:
863 | Create CAD reports based on any data field in the CAD database
864 | Create CAD reports based on multiple operational data fields in the CAD database
865 | Ability to create, within the CAD application, standard reports consistent with NFPA benchmarks (e.g., 1221, 1710).
866 | Ability to generate the following standard reports from within the CAD application:
867 | Incident analysis by day of week
868 | Incident analysis by geographic area
869 | Incident analysis by hour of day
870 | Incident analysis by shift
871 | Incident analysis by call type
872 | Incident analysis by disposition
873 | Incident analysis by geographic area by hour of day
874 | Incident analysis by responding agency
875 | Incident analysis by dispatching agency
876 | Incident analysis by dispatcher
877 | Incident analysis by workstation
878 | Incident analysis by unit
879 | Call Source (e.g., officer-initiated, 9-1-1, 10-digit, [NAME], etc.)
880 | False alarm reports
881 | Response times by geographic area
882 | Response times by type of call/priority
883 | Response times by original call destination
884 | Response times by assigned unit
885 | Response times by agency
886 | Calls on hold during specific time range
887 | Total and average time on call – by day of week
888 | Total and average time on call – by geographic area
889 | Total and average time on call – by hour of day
890 | Total calls for service by:
891 | Date or date range
892 | Disposition
893 | Time of day
894 | Total incidents by date by nature or disposition
895 | Ability to provide an analytical tool that reviews workload by call-taker/dispatcher.
896 | Ability to analyze incidents based upon multiple parameters (e.g., date, time, location, call type, dispatcher, etc.)
897 | Ability to provide a dashboard reporting feature. - expand on this.
898 | Ability to create ad hoc reports.
899 | Ability to generate a list of incidents to be shared with the public based on agency-specific business rules.
900 | Ability to generate a report containing a summary of incidents for an agency-defined period of time (e.g., for distribution to the public).
901 | CAD Queries
902 | Ability to query law RMS from within the CAD application.
903 | Ability to query FRMS from within the CAD application.
904 | Ability to query WACIC/NCIC from within the CAD application.
905 | Ability to query all databases internal to the CAD application as well as any databases interfaced to the CAD application with a single query.
906 | Ability to query call for service records based on data elements captured, including but not limited to:
907 | Date range
908 | Time range
909 | Call type
910 | Incident number
911 | Unit ID
912 | Officer name/ID
913 | Location
914 | Any location in an incident
915 | Block Range
916 | Response Area
917 | Name
918 | License plate
919 | Phone number
920 | Intersection
921 | Any information within the narrative
922 | Any combination of these parameters
923 | Ability to query call  for service records geographically.
924 | Ability to automatically notify user when query information has been queried within an agency-defined time frame "delayed inquiry hit" (e.g., querying a license that has been queried in the past hour by another user).
925 | Ability to automatically run a registered vehicle owner upon return of a license plate query.
926 | Ability to query and view the following by any public safety boundary layer (e.g., beat, sector etc.):
927 | Active calls
928 | Pending calls
929 | Ability to query unit history by any combination of the following:
930 | Date and time range (e.g., start and end date and time parameters)
931 | Unit ID, field personnel ID, or employee number
932 | Ability to query resource availability by:
933 | Dispatch group
934 | Geographic area (e.g., fire zone box, beat, sector)
935 | Officer name/ID
936 | Agency
937 | Special skills
938 | Unit types (e.g., apparatus, patrol units, Hazmat, etc.)
939 | Ability to query unit status by:
940 | Date and time range
941 | Dispatch group
942 | Personnel ID
943 | Geographic area (e.g., fire zone box, beat, sector)
944 | Incident type
945 | Terminal ID
946 | Unit ID
947 | Field Personnel name
948 | Unit types (e.g., apparatus, patrol units)
949 | Ability to sort query results by any criteria (e.g., most recent to oldest, by priority, etc.).
950 | Ability for operator to associate RMS, WACIC/NCIC/NLETS, and other database queries with a requesting Unit ID or Officer name/ID |  |  |  |  |  | Regardless of the requestor’s log-in status
951 | CAD and Mobile Messaging
952 | General Messaging Features
953 | Ability to send messages to a user who is not logged into CAD and cache that message for retrieval when the user logs onto CAD.
954 | Ability upon log-on to be automatically assigned to the corresponding message group.
955 | Ability for certain individuals to be part of multiple messaging groups.
956 | Ability for message server to continuously attempt to deliver a message until received and confirmed.
957 | Ability to support a minimum of the following messaging functions to and from any CAD address:
958 | Desktop-to-desktop messaging
959 | Desktop-to-dispatch messaging
960 | Desktop-to-pager messaging
961 | Desktop-to-cell phone messaging
962 | Desktop-to-unit messaging
963 | Unit-to-desktop messaging
964 | Unit-to-dispatch messaging, without units having to know the dispatcher port number
965 | Unit-to-pager messaging
966 | Unit-to-unit messaging
967 | Unit-to-cell phone messaging
968 | Ability to send a message to a specific individual on a shared apparatus/unit.
969 | Ability to send broadcast messages (e.g. to all users).
970 | Ability to support real-time instant messaging.
971 | Ability to display the following identifiers within a message:
972 | [NAME] name/unit ID
973 | Sender date
974 | Sender time
975 | Sender workstation ID
976 | Receiver name/unit ID
977 | Receiver date
978 | Receiver time
979 | Receiver workstation ID
980 | Ability to assign and change the priority level of a message (e.g., routine, urgent, emergency).
981 | Ability for each terminal to have a unique identifier included in each transmission to the host.
982 | Ability to provide a web-based version of messaging capabilities.
983 | Ability to attach a dispatch-related messages to an incident.
984 | Ability to store messages for later viewing.
985 | Ability for host computer to store unread messages when user logs off.
986 | Ability for messages to be sorted by most recent or first received.
987 | Sending Messages
988 | Ability to create, edit and save message groups.
989 | Ability to send messages across agencies (e.g., law enforcement to fire and vice versa).
990 | Ability to create an automatic message type based on call type or unit assigned to the call (e.g., in the case of K-9 call, all responding units are sent a message to make a public announcement).
991 | Ability to select a recipient from the unit status window within CAD.
992 | Ability for users to select an unlimited number of people as part of a message group.
993 | Ability to enter unlimited narrative with wrap-around feature (if limited, note the characters permissible in the "comments" section).
994 | Ability to add to a message before forwarding to another user.
995 | Ability to attach files to messages.
996 | Ability to embed photos in messages.
997 | Ability to set County-defined file size limit.
998 | Ability to automatically compress and resize images to comply with County-defined file size limits.
999 | Ability to send a message to all units handling a specific incident.
1000 | Ability to transmit a reply message to the originator of a currently displayed message without having to reenter the originator's address.
1001 | Ability to transmit a "reply all" message to multiple recipients that were part of the originator's message group.
1002 | Ability to create messages that are retained in the system and sent at pre-specified times.
1003 | Ability to provide a notification for delivery of messages to the device.
1004 | Ability to provide a notification for non-delivery of messages.
1005 | Receiving Messages
1006 | Ability to notify receiver via an audible and/or visual flag that a new message has arrived in mailbox.
1007 | Ability to sort messages in chronological order.
1008 | Ability to notify receiver of an unread message after an Agency-defined time period.
1009 | Ability to prevent incoming messages from interfering with current work.
1010 | Ability to notify receiver of total number of unread messages.
1011 | Ability to prevent incoming messages from overlaying the screen.
1012 | Ability for messages to be queued in an "inbox" for later viewing at the convenience of users.
1013 | Ability to assign a priority to a message (e.g., an emergency message would override other message).
1014 | Ability to query message logs by Agency-defined criteria (e.g., date/time range, sender, recipient, device).
1015 | Ability to note time opened/read by receiver.
1016 | Ability to queue and display message waiting by priority.
1017 | Ability to clear a message from the inbox.
1018 | Ability to retain a message in the inbox.
1019 | Ability for supervisors to monitor messages.
1020 | Ability to generate report or notification of Agency-defined inappropriate language.
1021 | Ability to store messages in a County-defined buffer size.
1022 | Ability to delete oldest messages as buffer fills.
1023 | Ability to maintain an archive of all messages.
1024 | CAD System Administration
1025 | CAD Table Maintenance
1026 | Ability for CAD fields to default to County-defined values.
1027 | Ability for CAD fields to default to Agency-defined values.
1028 | Ability to include, at a minimum, the following data tables:
1029 | Call source (e.g., officer-initiated, 9-1-1, 10-digit, etc.)
1030 | Call types and priorities
1031 | Commands
1032 | Devices
1033 | Dispositions
1034 | Equipment
1035 | Event error logs (so vendor can identify and troubleshoot errors)
1036 | Patrol and command area definitions
1037 | Personnel, including emergency contact information and current assignment
1038 | Timers
1039 | Unit status types (i.e., assigned, unassigned, assigned but available)
1040 | Units
1041 | Ability for each agency to define the above-listed data tables.
1042 | Ability to limit the types of calls to which certain units can respond.
1043 | Ability to override the above-described functionality.
1044 | Ability to create and maintain a call type classification that is based upon the time of day.
1045 | CAD Configuration
1046 | Ability to create agency-defined data entry screens.
1047 | Ability to configure the field entry sequence.
1048 | Ability to create conditional fields and mandatory data elements based on agency-defined criteria.
1049 | Ability for agency to add or change data elements on any screen based on defined system permissions.
1050 | Ability to configure commands (e.g., V = vehicle stop) at the administrator level.
1051 | Ability to configure status code colors.
1052 | Response Plans
1053 | Ability for each agency to develop response plans based on:
1054 | Geographic area (e.g., beat, sector, fire zone box etc.)
1055 | Address
1056 | Time of day
1057 | Fire alarm level
1058 | Call type
1059 | Fire pre-plan
1060 | Responding Agency
1061 | Resource availability
1062 | Station coverage requirements
1063 | Ability to assign a single response plan with multiple call types.
1064 | Ability to support differing response plans by agency (Agencies may respond differently to the same call type).
1065 | Ability to include multiple agencies in response plans.
1066 | Ability to disable/enable response plans (e.g., fairs, parades, etc.)
1067 | Ability to generate temporary response plans.
1068 | Ability for user to override response plan recommendation.
1069 | Ability to load a new response plan without stopping or pausing application operations.
1070 | Ability for a communications supervisor to update the response plans (e.g., without assistance from technical support or vendor).
1071 | [NAME] and Premise History File Maintenance
1072 | Ability to capture  hazard and premise information including, but not limited to:
1073 | Building information
1074 | Emergency contact information
1075 | Firearms
1076 | Hazardous materials
1077 | Medical concerns
1078 | Occupancy information
1079 | Pre-plan information
1080 | Ability to enter hazards and premise information associated with:
1081 | Persons
1082 | Specific locations
1083 | Address ranges
1084 | Vehicles
1085 | Ability to associate a temporary hazard with a location.
1086 | Ability for pre-plan information to be transferrable across disciplines.
1087 | Ability for each agency to limit what pre-plan and hazard information is made available across disciplines.
1088 | Ability to store pre-plans.
1089 | Ability for pre-plans to be uploaded from a Fire RMS.
1090 | Ability to attach files to hazard and premise records (e.g., building layouts).
1091 | Ability to automatically update premise history when an incident occurs.
1092 | Ability to capture the following information when creating premise history:
1093 | Date and time stamp
1094 | Date of incident
1095 | Disposition
1096 | Type of incident
1097 | Incident number
1098 | Narrative text of unlimited length (if limited, indicate maximum in the "comments" field)
1099 | Ability to store premise information for an agency-defined length of time.
1100 | Ability to define valid date ranges for time limited premise information at a given location (e.g., information valid between <start date> and <end date>.
1101 | Ability to provide a notification to the System Administrator of upcoming notification expirations.
1102 | Administrative Contact Database
1103 | Ability to maintain a searchable list of contact information and telephone numbers related to other city and state departments, utility companies, hospitals, ambulance companies, and other law, fire, and EMS agencies.
1104 | Ability to access administrative contact database directly from CAD window.
1105 | Ability to access RMS/FRMS Personnel module directly from CAD.
1106 | Ability to restrict access to certain data fields within the RMS/FRMS personnel modules.
1107 | Ability to restrict access to the database based upon security level.
1108 | Ability to support an upload of contact data via standard file formats (e.g., CSV).
1109 | CAD Recovery
1110 | Ability to retain and display last-known unit and incident status in the event of a catastrophic system failure (e.g., at the workstation, remote external logging device or similar solution).
1111 | Ability to load incidents from the backup environment into the production environment upon restarting system after a system failure.
1112 | Ability for CAD workstation to maintain operation in the event the CAD server fails.
1113 | Ability to reset numbering after CAD system has been restarted.
1114 | Ability to retain CAD numbering sequence after system has been restarted.
1115 | Ability to add incidents retroactively independent of incident number order or sequential time sequence (i.e., incident 15 may have occurred after incident 20) in the event that the CAD system is unavailable for a time.
1116 | Ability to process retroactive incidents and assign incident numbers in the same manner as new incidents; the supervisor can override the times associated with the incident.
1117 | Ability to set aside a block of call for service numbers in the event of a catastrophic CAD failure to enable a manual workflow and tracking.
1118 | Ability to indicate in the audit trail that an incident was entered retroactively.
1119 | Ability to perform CAD catch-ups after system downtime, without requiring users to log back in.