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

Spokane County Request for Proposals #P8705
Public Safety Information Systems Replacement Project
RMS Requirements
 | RMS!B30
 | RMS!B114
 | RMS!B404
 | RMS!B437
 | [NAME]
 | RMS!B574
 | [NAME]
 | RMS!B717
 | RMS!B839
 | RMS!B854
 | RMS!B865
 | RMS!B1031
 | RMS!B1119
 | RMS!B1241
 | RMS!B1436
 | RMS!B1573
 | RMS!B1621
 | RMS!B1738
Item # | General RMS Requirements | Comply ( C) | Not Comply (N) | Alternative\Conversion (A) | Modification (M) | Third Party Add-On (T) | Comments
1 | Ability to generate inquiries to internal and external sources from within application.
2 | Ability to support a multi-jurisdictional environment.
3 | Ability to access a browser-based RMS.
4 | Ability for information captured in one module to be made transferrable to all other modules within the RMS.
5 | Ability to support NIBRS reporting.
6 | Ability to incorporate NIBRS business logic.
7 | Ability for agency to modify business logic.
8 | Ability to support CLERY reporting.
9 | Ability to support UCR reporting.
10 | Ability for system to automatically convert NIBRS codes to UCR codes.
11 | Ability to create a CAD generated incident number within the RMS without requiring the dispatch of resources.
12 | Ability for the County to add data elements.
13 | System operates on MS Windows.
14 | Ability to support a messaging system to allow users to communicate via:
15 | RMS user-to-RMS user (and vice versa)
16 | RMS user-to-CAD user (and vice versa)
17 | RMS user-to-Mobile user (and vice versa)
18 | RMS user-to-AFR user (and vice versa)
19 | General Data Entry Requirements
20 | Ability to eliminate redundant data entry by allowing reuse of previously stored information when entering new records or reports.
21 | Ability to use or reuse the data returned from external sources to eliminate redundant data entry.
22 | Ability to support an unlimited number of characters for data fields (if limited, enter the characters permissible in the "comments" section).
23 | Ability to provide narrative/comment fields of unlimited length (if limited, enter the characters permissible in the "comments" section).
24 | Ability to provide basic word processing capabilities on narrative and comment fields, including, but not limited to:
25 | Text wrap
26 | Paragraph formatting
27 | Use of bullets and numbering
28 | Spell check
29 | [NAME] check
30 | Ability to copy and paste data between fields.
31 | Ability to automatically calculate the day of week for any entered date.
32 | Ability to enter data in a non-case sensitive format.
33 | Ability to require agency specific fields to require data entry in a case sensitive format (e.g., all capitals).
34 | Ability for all data extracts and inputs to comply with GJXDM standards.
35 | Ability to automatically translate standard text entries into NIBRS codes.
36 | Ability to attach files to records.
37 | General Data Quality Controls
38 | Ability for drop down lists to incorporate NCIC codes where applicable.
39 | Ability for County to define drop down lists.
40 | Ability for County to modify drop down lists without vendor intervention.
41 | Ability for the County to define mandatory fields in data entry screens.
42 | Ability to prevent appearance on a data entry screen of a field for which a value should not be entered.
43 | Ability for County to modify tab order.
44 | Ability to identify mandatory fields based on previously entered data (e.g. crime type).
45 | Ability to limit available values in subsequent code tables based on previously entered data (e.g. crime type).
46 | Ability to visually distinguish between mandatory and optional fields.
47 | Ability to prompt user to complete any mandatory fields not completed.
48 | Ability to validate data entry to ensure all required fields have been completed when records entry is fully complete.
49 | Ability to validate data entry to ensure all required fields have been completed at time of data entry (e.g., by field)
50 | Ability to validate data to ensure that only valid codes have been used.
51 | Ability to validate any data field that requires master index data against master indices.
52 | Ability to advise user of data entry errors.
53 | Ability to suggest a remedy for errors.
54 | Ability for corrected data in a field (e.g. address) to auto populate across related reports.
55 | Ability to add supplemental data fields.
56 | Ability to remove any data fields.
57 | NIBRS Reporting
58 | Ability to submit reports for automatic NIBRS review from the RMS following supervisor approval (should be a review of elements only and not a submission).
59 | Ability for RMS to be automatically updated with NIBRS requirements as requirements change.
60 | Ability to flag any data fields that do not meet NIBRS requirements, or contain errors.
61 | Ability to prevent reports from being submitted to NIBRS until all errors have been corrected.
62 | Ability for system to identify trends that continually fail to meet NIBRS requirements (to identify training needs).
63 | Ability to perform monthly NIBRS audits.
64 | Ability to flag any data elements that are edited by an authorized user other than the original author (e.g., NIBRS review personnel change a data element from the original report).
65 | Ability to electronically submit NIBRS data to WASPC.
66 | Ability to maintain electronic submission compliance as determined by WASPC.
67 | Ability to run all reports as required by NIBRS.
68 | Ability to run all reports as required by CLERY.
69 | Ability to maintain a version history of each case that identifies any edits to a case report over time.
70 | Alerts and [NAME]
71 | Ability to create an alert based on records matching specified criteria:
72 | Audible alert
73 | Visual Alert
74 | Ability to create a flag on a person of interest (e.g. for an investigation).
75 | Ability to generate alerts to individuals via:
76 | RMS Log-on
77 | E-mail
78 | Ability to create a flag based on a crime type.
79 | Ability to create and define an unlimited number of alert categories.
80 | Ability to limit ability to see alerts by security profile.
81 | Ability to create business rules for flag categories (e.g. length of time before expiration by type of flag).
82 | Ability to enter comments regarding the alert associated with a record.
83 | Ability to create an alert so that a user is notified when a name is queried, entered, or updated in any other context in the RMS (note the type of alerting available in the comments section, e.g., e-mail, text, etc.)
84 | Master Indices
85 | General Master Index Requirements
86 | Ability to maintain the following master indices:
87 | People
88 | Locations
89 | Property
90 | Vehicles
91 | Licensing
92 | Organizations (e.g., businesses and gangs)
93 | Ability to maintain historical information upon entry of updated information into a master record.
94 | Ability to automatically update master indices upon entry of report information.
95 | Ability to give a user entering a new master record  the option of determining if there is potentially an existing master record match.
96 | Ability to automatically perform a matching function using a rules-based process defined by the County when a record or report is added to the RMS.
97 | Ability to support linkages across master indices.
98 | Ability to link phone numbers to:
99 | People
100 | Locations
101 | Organizations
102 | Property
103 | Vehicles
104 | Ability to perform the following functions for all records related to a query return:
105 | Retrieve
106 | Display
107 | Export
108 | Print
109 | Master Name Index
110 | Ability to link an individual master name record to every event in which the individual is involved or associated.
111 | Ability to give a master name record to every person associated with an event.
112 | Ability to link a new event to an existing master name record if the person is involved in the new event.
113 | Ability to assign and manage unique CCID numbers to some names
114 | Ability to accommodate:
115 | Hyphenated names
116 | Names with apostrophes (e.g., O'Malley)
117 | Multiple word names (e.g. Sanchez de Cordova or [NAME])
118 | Ability to link alias names to an individual master name record.
119 | Ability to produce a synopsis of all RMS records associated with a person by querying that person's name.
120 | Ability to view all related records (e.g., order for protection, domestic abuse no contact order, eviction order, etc.) when querying an individual MNI record.
121 | Ability to provide dedicated fields to capture, at a minimum, the following information in the master name index:
122 | Physical characteristics, including, but not limited to:
123 | Build
124 | Citizenship
125 | Date of birth
126 | Place of birth
127 | Ethnicity
128 | Eye color
129 | Hair color
130 | Hair style
131 | Hair length
132 | Hand use
133 | Height
134 | Height Range
135 | Race
136 | Sex
137 | Sex at birth
138 | Weight
139 | Weight Range
140 | Scars, marks and tattoos, including:
141 | Type (scar mark or tattoo)
142 | Location
143 | Description
144 | Age at time of incident
145 | Age range
146 | INS number
147 | Address
148 | Address history
149 | Residency
150 | Relationship to incident (e.g., suspect, victim, etc.)
151 | School information
152 | Employer information
153 | Occupation
154 | Telephone numbers (multiple)
155 | [NAME] addresses
156 | Involvements:
157 | Known involvements (people with whom involved in previous incidents)
158 | Nature of involvement (e.g. how determined involved or associated with another person)
159 | Associates (e.g. via a link to an organization)
160 | Name of associate
161 | Nature of association (e.g. associated via which organization)
162 | Modus operandi
163 | Identification information, including, but not limited to:
164 | Social security number
165 | Driver's license number and state
166 | Alien registration number
167 | Immigration status
168 | FBI number
169 | Sex offender number
170 | Ability to update MNI information while maintaining historical information.
171 | Ability to track changes for an individual over time for pieces of information that are subject to change including, but not limited to:
172 | Weight
173 | Hair color
174 | Address
175 | Identification numbers (e.g., DOL number, SSN)
176 | Employer information
177 | Phone number
178 | Name changes
179 | Ability to associate alias identifiers with a master name record, including, but not limited to:
180 | Alias names
181 | False names
182 | Monikers
183 | Dates of birth
184 | Social security number
185 | CID (also known as CCID)
186 | Driver's license number
187 | Ability to provide user entering a name with a list of potential existing master name records based on a variety of criteria, including:
188 | Exact spelling
189 | Partial name
190 | Sound-alike searching
191 | Phonetic replacement
192 | Diminutive first names
193 | Social security number
194 | Name order (e.g., first, middle, last)
195 | Date of birth
196 | Age range
197 | Driver's license number
198 | Ability for user to decide whether to link information to an existing master name record or add a new master name record.
199 | Ability for user to add a new master name record.
200 | Ability to generate a canned report displaying all added and linked MNI records for a user-defined period of time.
201 | Ability to unlink a record or report from one MNI record and re-link it to another MNI record.
202 | Ability to merge multiple MNI records into one MNI record.
203 | Ability to unlink distinct MNI records.
204 | Ability to run a canned report identifying potential duplicate MNI records.
205 | Master [NAME] Index
206 | Ability to link a vehicle record to every event in which a vehicle is involved or associated.
207 | Ability to give a master vehicle record to every vehicle associated with an event.
208 | Ability to link a new event to an existing master vehicle record if the vehicle is involved in the new event.
209 | Ability to provide dedicated fields to capture, at a minimum, the following information in the master vehicle index:
210 | Vehicle identification number
211 | License plate number
212 | License plate state
213 | License plate year
214 | Registered owner
215 | Legal Owner
216 | Vehicle description, including:
217 | Type
218 | Make
219 | Model
220 | Year
221 | Style
222 | Other identifiers (e.g., bumper stickers, broken windows, etc.)
223 | Color
224 | Vehicle Status (e.g., damaged, investigative, recovered, stolen, suspect)
225 | Ability to associate multiple owners with one vehicle.
226 | Ability to associate multiple drivers with a vehicle.
227 | Ability to associate multiple license plates with a vehicle.
228 | Ability to track previous vehicle owners.
229 | Ability to produce a synopsis of all RMS records associated with a vehicle by querying the vehicle.
230 | Ability to view all related records when querying an individual MVI record.
231 | Ability to automatically perform a matching function using a rules-based process defined by the agency when a record or report is added to the RMS.
232 | Ability to provide user entering a vehicle with a list of potential existing master vehicle records based on a variety of search criteria, including:
233 | Vehicle description
234 | Vehicle license plate number
235 | Partial license plate number
236 | Vehicle identification number or owner applied number
237 | Ability for user to decide whether to link information to an existing master vehicle record or add a new master vehicle record.
238 | Ability for user to link information to an existing master vehicle record.
239 | Ability for user to add a new master vehicle record.
240 | Ability to notify appropriate personnel when an MVI record is linked or added to the database.
241 | Ability to generate a canned report displaying all added and linked MVI records for a user-defined period of time.
242 | Ability to unlink a report or record from one MVI record and re-link it to another MVI record.
243 | Ability to merge two or more MVI records into one MVI record.
244 | Ability to unlink distinct MVI records.
245 | Ability to run a canned report identifying potential duplicate MVI records.
246 | Master Property Index
247 | Ability to link a property record to every incident/report in which the property is involved or associated.
248 | Ability to give a master property record to every piece of property associated with an event.
249 | Ability to link a new event to an existing master property record if the property is involved in the new event.
250 | Ability to link property entered as evidence with its evidence record.
251 | Ability to provide dedicated fields to document the following information in the master property index, including but not limited to:
252 | Agency
253 | Case Number
254 | Incident information:
255 | Incident number |  |  |  |  |  | Incident number should have standard format.  Year – seq where sequence number is zero filled from left or not, but be consistent.
256 | Date and time
257 | Location
258 | Property type (evidence, impounded, found, forfeitures, stolen, missing, etc.)
259 | Article information, including but not limited to:
260 | Brand name
261 | Category
262 | Color
263 | Comments
264 | Property condition
265 | Description
266 | Make
267 | Model name
268 | Model number
269 | NCIC code
270 | Owner-applied number
271 | License Plate Number
272 | Quantity (unit of measure)
273 | Serial number
274 | Size
275 | Special markings
276 | Subcategory (dangerous, illegal, oversized, valuable, and other user-defined categories)
277 | Involved in a crime (Y/N)
278 | Initial value
279 | Recovery information:
280 | Date
281 | Location
282 | Recovery Value
283 | Recovery condition
284 | Property Owner/Claimant information:
285 | Person name
286 | Arrested (Y/N)
287 | Address (multiple - home and business)
288 | Telephone number (multiple - home, business, cell)
289 | Social Security Number
290 | Age
291 | Date of Birth
292 | Weapons-specific information:
293 | Make
294 | Type
295 | Caliber/Gauge
296 | Finish
297 | Model
298 | Owner-applied number
299 | Serial number
300 | Suppressor
301 | Barrel length
302 | Agency-defined
303 | [NAME] weapon? (Y/N)
304 | Large capacity magazine (Y/N)
305 | Defaced serial number (Y/N)
306 | Currency-specific information:
307 | Currency denominations (type and quantity)
308 | Currency serial number(s)
309 | Currency type (i.e., cash, money order)
310 | Currency total amount
311 | Currency comments
312 | Drug seizure currency (Y/N)
313 | Counterfeit (Y/N)
314 | Non-U.S. Currency (Y/N)
315 | Foreign currency type (text field)
316 | Drug information:
317 | Quantity (unit of measure)
318 | Type
319 | Description
320 | Ability to automatically cross-reference the MPI when property is entered into an event in order to find potential matches.
321 | Master Location Index
322 | Ability to aggregate information throughout the RMS based on any of the following:
323 | Specific address
324 | Address range
325 | Geographic area (as defined in the geofile)
326 | Locations based on latitude and longitude coordinates
327 | Landmarks
328 | Ability to link a location record to every event in which the location is involved or associated.
329 | Ability to give a master location record to every location associated with an event.
330 | Ability to link a new event to an existing master location record if the location is involved in the new event.
331 | Ability to provide dedicated fields to capture premise information, including, but not limited to:
332 | Premise type
333 | Elevation (e.g. floor)
334 | Occupancy
335 | Hazards
336 | Common place name
337 | Last date entered or updated
338 | Ability to enforce formatting rules when entering location information.
339 | Ability to parse address fields into the following:
340 | Street number (including fractions, alphas, etc.)
341 | Street
342 | Street type
343 | Prefix directional
344 | Suffix directional
345 | Suite or apartment number
346 | City
347 | State
348 | Zip
349 | County
350 | Ability to accommodate non-street address location identifiers (e.g. mile markers, [NAME] post locations, subway stations).
351 | Ability to accommodate intersections.
352 | Ability to validate addresses at the  time of data entry (if address is within the boundaries of the agency geofile).
353 | Ability to update master location index with geofile data (e.g. latitude and longitude, agency-defined geographical boundaries, etc.), during the address validation process.
354 | Ability to accept an unverified address.
355 | Ability to flag an unverified address.
356 | Ability to notify appropriate personnel of unverified address entries.
357 | Ability to link addresses and commonplace street names.
358 | Ability to compute geoverification locations real time, at time of entry.
359 | Ability to compute jurisdiction of location real time, at time of entry.
360 | Master Organization Index
361 | Ability for agency to define organization categories (e.g. gangs, businesses, schools, shopping centers, etc.).
362 | Ability to link an organization record to every event in which the organization is involved or associated.
363 | Ability to give a master organization record to every organization associated with an event.
364 | Ability to link a new event to an existing master organization record if the organization is involved in the new event.
365 | Ability to capture organization information, including, but not limited to:
366 | Subgroups (e.g., specific faction within a specific gang)
367 | Type
368 | Name
369 | Associated individuals
370 | Association type (owner, gang member, etc.)
371 | Phone number(s)
372 | Location
373 | Aliases
374 | Ability to keep historical records of changes to organization names and locations.
375 | Ability to associate multiple organizations to a location.
376 | Ability to maintain historical records of organizational changes to a location (e.g., new business).
377 | Standard Master Indices Outputs
378 | Ability to query master indices by any operational data element.
379 | Ability to produce a comprehensive response to a query.
380 | Ability to display all related records when producing a comprehensive response to a query.
381 | Calls for Service
382 | General Calls for Service Requirements
383 | Ability to receive all call for service data transferrable from the CAD application as determined by the County.
384 | Ability to link call for service data to:
385 | Involved persons in the MNI
386 | Involved vehicles in the MNI
387 | Involved locations in the MNI
388 | Phone numbers
389 | Address
390 | Defined geographic area (e.g., district)
391 | Case reports
392 | Field contacts
393 | Ability to transfer call for service data when a report number is assigned.
394 | Ability to continually update call for service data until call is closed.
395 | Standard Calls for Service Outputs
396 | Ability to produce the following standard reports:
397 | Daily log showing calls for service for prior 24 hours
398 | Daily log showing calls received for a specified date and time period
399 | Report Tyupe (A-Approval, AA- Additional Approval, AS-Settle Approval or equivelants)
400 | Activity analysis by:
401 | Specified geographical area
402 | Specified time range
403 | Day of week
404 | Hour of day
405 | Hour of day and day of week
406 | Resource (e.g., officer)
407 | Response time analysis by:
408 | Specified geographical area
409 | Specified time range
410 | Call type
411 | Workload activity by:
412 | Resource assigned
413 | Specified time range
414 | Geographic area
415 | User
416 | Data Analysis
417 | General [NAME]
418 | Ability to analyze activity using the following analysis options, including, but not limited to:
419 | Frequency analyses (e.g., analyses with only one variable)
420 | Spatial analysis (e.g., analyses by user-defined geographical area).
421 | Time analysis (e.g., by time, date, date range, etc.)
422 | Link analysis (e.g., relationship between non-key related fields)
423 | Change over time analysis (e.g., comparative analysis)
424 | Simple relational analyses (e.g., seeking relationships between two data fields)
425 | Complex relational analysis (e.g., seeking relationships among three or more data fields).
426 | Ability to present statistics in graphical formats, including, but not limited to the following:
427 | Pin maps
428 | Bar graphs
429 | Pie charts
430 | Line graphs
431 | ESRI based, State Plane coordinate mapping displays
432 | Ability for all analysis to be run on a live database (i.e., in real-time).
433 | Ability to provide [NAME]-type functionality that displays summations of ongoing activities in real-time.
434 | Printing & Attachment Capabilites
435 | Abilit to select print areas based on:
436 | Offense Code
437 | Person(s)
438 | Property
439 | Vehicle(s)
440 | Narrative
441 | Ability to Print reports in batches by:
442 | Incident number
443 | User
444 | NIBRS Offense Code
445 | Ability to append attachmens to RMS Reports as (but not limited to):
446 | CPS/APS Reports
447 | Web Report and\or URL
448 | Fax
449 | Photo or Scanned Image (as JPEG, TIFF, GIF)
450 | Witness Statements
451 | Victim property lists
452 | General [NAME], Word, Excel documents
453 | Activity Analysis
454 | Ability to track and analyze crime activity by:
455 | Location
456 | Geographical area
457 | Time period
458 | Crime Type
459 | Modus operandi
460 | Agency
461 | Victim characteristics
462 | Any combination of above elements
463 | Ability to alert specific individuals (agency-defined) when crime activity exceeds an agency-defined level for a given:
464 | Incident type
465 | Location by user-defined geographic boundaries
466 | User-defined period
467 | Ability for each agency to label persons and create an optional alert associated with that individual.
468 | Ability for the above mentioned "frequent flier", for a user to be notified when a report is written regarding that individual (note the type of alerting available in the comments section, e.g., email, RMS log-on, etc.)
469 | Data Aggregation
470 | Ability to aggregate data by:
471 | Date range
472 | Time of day
473 | Day of week
474 | Geographical area
475 | Officer ID
476 | Shift
477 | Agency
478 | Ability to aggregate data contained in records to create:
479 | Summary reports showing data element totals (e.g. number of burglaries, number of calls for service)
480 | Summary reports showing data element averages (e.g., average number of stolen cars on Friday versus Wednesday)
481 | Summary reports showing frequency of occurrence (e.g., number of robberies at a gas station)
482 | Summary reports showing percentages (e.g., percentage of total crimes by beat, percentage of robberies involving a weapon, etc.)
483 | Ability to generate reports comparing information between multiple years.
484 | Map Analysis
485 | Ability to plot incident data on a map of the service area.
486 | Ability for mapping analysis to be ESRI-compatible
487 | Vendor is an ESRI certified partner.
488 | Ability to drill down for incident details from any incident plotted on the map.
489 | Ability to identify "hot spots" on a map.
490 | Ability to drill down on a map location for access to detailed incident history, premise history, etc.
491 | Ability to conduct a radius search on a map.
492 | Ability to conduct a polygon search on a map.
493 | Ability to easily print maps at any point during the drill down.
494 | Ability to use different icons to display different data types.
495 | Ability to select a defined geographical area on a map and display any event/incident type.
496 | Ability to select a defined geographical area on a map and display multiple event/incident types.
497 | Ability to display standard map elements (e.g., scale bar, north arrow, legend, title, date, time, creator, disclaimers, etc.)
498 | Ability for the County to define its own pin map icons (size, color, symbols, etc.).
499 | Link Analysis
500 | Ability to analyze linkages among data elements based on any combination of:
501 | Persons
502 | Organizations (e.g. gang affiliations)
503 | Vehicles
504 | Property
505 | Telephone numbers
506 | Locations
507 | Ability to drill down into specific records in relationship diagrams.
508 | Ability to click on a linked element to show links based on that element (e.g., if a person of interest is linked to a business, click on the business to show its linkages).
509 | Ability to display the nature of the link (e.g., telephone number, vehicle, incident, etc.).
510 | Ability to display relationships between stolen and recovered locations for vehicles.
511 | Ability to graphically display on a map the location of persons within a geographically defined area for a given time range (e.g.,, all people living in an area with a history of auto theft over the past two years) by:
512 | Incident Type
513 | Modus operandi
514 | Physical Characteristics
515 | Searches
516 | Ability to conduct searches on any operational data field.
517 | Ability to search narrative text.
518 | Ability to perform database queries using:
519 | "String search"
520 | "Wild cards"
521 | Date ranges
522 | Partial information in an operational data field
523 | Soundex or sound-alike algorithm
524 | Boolean operators (e.g., and, or, etc.)
525 | Any combination of  operational data fields
526 | Warrants
527 | General Warrant Requirements
528 | Ability for system to automatically verify the name imported from the County Warrant System against the Master Name Index.
529 | Ability to track the following status information in regard to the service of warrants:
530 | Serving officer
531 | Service date and time
532 | Serving agency
533 | Cleared (i.e., served)
534 | Cancelled
535 | Modified
536 | Officer assigned
537 | Date of assignment
538 | Method of service
539 | Date of service
540 | Location of service (agency-defined geographic areas)
541 | Mileage
542 | Service Fees
543 | Reason for nonservice
544 | Ability to view Warrant information from a Mobile environment.
545 | Ability for outside agencies such as the Courts to submit warrants using an automated interface between computer systems
546 | Ability to notify agency-defined personnel when certain warrants are served based upon person (e.g., warrant served for [NAME]).
547 | Ability for outside agencies such as the Courts to quash, cancel or recall a warrant through an automated interface between computer systems
548 | Warrant Management
549 | Ability to query the warrant module against any combination of the above-specified criteria that the system captures.
550 | Ability to cancel a warrant.
551 | Ability to record the following upon cancellation of a warrant:
552 | Date of cancellation
553 | Reason for cancellation
554 | Ability to modify a warrant.
555 | Ability to link a warrant to a master name record.
556 | Ability to link a file to a warrant.
557 | Standard Warrant Outputs
558 | Ability to print a warrant record.
559 | Ability to produce a report of warrants based on user-defined search criteria, including but not limited to:
560 | Geographic Area
561 | Expiration
562 | Crime Type
563 | Date of Warrant entry
564 | Warrant Type
565 | Data Range
566 | Any data field captured as part of the warrant
567 | Any combination of the above data
568 | Ability to produce summary reports of warrants.
569 | Ability to produce a report showing cancelled and modified warrants.
570 | Ability to produce a report showing attempts to serve by date or date range.
571 | Ability to produce a warrant aging report.
572 | Ability to produce a report showing warrant history for a subject.
573 | Ability to generate a scheduled report (e.g., monthly, quarterly, etc.) showing warrants that need to be reviewed.
574 | Personnel Activity
575 | Personnel Activity Requirements
576 | Ability to provide dedicated fields to capture personnel activity information, including, but not limited to:
577 | Arrests:
578 | Felony
579 | Misdemeanor
580 | Citations:
581 | Traffic
582 | Warnings
583 | Parking
584 | Misdemeanor
585 | Field interviews
586 | Self-initiated activity
587 | Dispatched activity
588 | Use of force
589 | Officer Assaults
590 | Injuries
591 | Officer involved shootings
592 | K-9 Activity
593 | Damage to property (including vehicles)
594 | Case assignments
595 | Reports filed (including type of report)
596 | Role in response efforts (primary or backup)
597 | Administrative time
598 | Time on duty
599 | Overtime
600 | Court time
601 | Training time
602 | Assistance outside of jurisdiction
603 | Unlimited special activities, listed in a County-defined drop down menu
604 | Reports entered
605 | Reports reviewed
606 | Reports approved
607 | Ability to track the following call information by officer:
608 | Call type
609 | Call received time
610 | Dispatch time
611 | Arrival time
612 | Call clearance time
613 | Disposition
614 | Ability for CAD Call for Service information to automatically populate and update Personnel Activity information.
615 | Ability for officers to add to their logs information that does not come from CAD.
616 | Ability to track "hold-over" time (time officer held on-duty past end of shift).
617 | Standard Personnel Activity Module Outputs
618 | Ability to generate reports summarizing patrol activity by:
619 | Individual
620 | Division
621 | Agency
622 | Timeframe
623 | Crime type
624 | Unit/Squad
625 | Shift
626 | Personnel Activity
627 | Self-initiated versus dispatched activity
628 | Date range
629 | Activity type
630 | Ability to generate reports summarizing records activity by:
631 | Reports entered
632 | Reports approved
633 | Ability to account for number of days working in summary statistics (e.g., arrests/day; tickets/day; etc.).
634 | Ability to generate reports itemizing patrol activity by:
635 | Type of crime
636 | Date range
637 | Response times (based on dispatch, received, and arrival times)
638 | Ability to query personnel workload activity by:
639 | Personnel name
640 | Personnel assignment
641 | Personnel ID
642 | Geographic area (e.g., beat, reporting district, etc.)
643 | Date/Time range
644 | Incident type
645 | Shift
646 | Unit/Squad
647 | Ability to for personnel workload activity to report summations of any data fields captured as part of personnel activity, including but not limited to:
648 | Arrests
649 | Citations
650 | Field interviews
651 | Self-initiated activity
652 | Dispatched activity
653 | Case assignments
654 | Reports filed (including type of report)
655 | Role in response efforts (primary or backup)
656 | Administrative time
657 | Time on duty
658 | Overtime
659 | Court time
660 | Training time
661 | Assistance outside of jurisdiction
662 | Personnel
663 | General Personnel Requirements
664 | Ability to provide dedicated fields to capture personnel information including, but not limited to:
665 | Name
666 | Address
667 | Telephone numbers (multiple)
668 | Race
669 | Ethnicity
670 | Sex
671 | Date of birth
672 | Driver license number
673 | Social security number
674 | Emergency contact information:
675 | Name
676 | Address
677 | [NAME]
678 | Phone number(s)
679 | Relationship
680 | Next of kin
681 | Employee photo
682 | Blood type
683 | Date of hire
684 | Date in class of hire
685 | Adjusted date of hire
686 | Evaluation dates
687 | Exit interview date
688 | Date of exit
689 | Employee ID number
690 | Department ID number
691 | Badge/serial number
692 | Current assignment
693 | Past assignment histories
694 | Rank(s)
695 | Promotion history
696 | Certifications
697 | Training history
698 | Education level
699 | Special skills
700 | Languages spoken
701 | Assigned equipment
702 | Vaccinations
703 | Exposures
704 | Work-related injuries
705 | Health-related duty restrictions
706 | Ability to alert supervisors of any personnel characteristics that are expiring (e.g., vaccinations, certifications, etc.)
707 | Ability to track all changes to personnel information, including but not limited to:
708 | Date of change
709 | Person making change
710 | Before/after values
711 | Ability to electronically attach files to personnel records.
712 | Standard Personnel Outputs
713 | Ability to generate personnel summary reports based on any operational data field in the personnel module.
714 | Ability to generate a report of individual personnel details.
715 | Ability to generate a duty roster.
716 | Ability to generate a report of issued equipment.
717 | Training
718 | Training Programs
719 | Ability to establish training programs.
720 | Ability to add ad hoc training.
721 | Ability to establish courses to include in the training programs, including:
722 | Course schedules
723 | Course content
724 | Prerequisites
725 | Maximum number of participants
726 | Minimum number of participants
727 | Ability to assign (schedule) participants to a class.
728 | Ability to document the viewing of online training (e.g., video).
729 | Ability to update individual training records when participants complete a class.
730 | Ability to define job categories (or classifications) with associated training requirements.
731 | Ability to assign personnel to one or more job categories for purposes of identifying required training programs.
732 | Individual and Job Category Training Records
733 | Ability to provide dedicated fields to capture individual training information, including, but not limited to:
734 | Name
735 | Employee ID
736 | Department ID
737 | Agency
738 | Job category
739 | Education history detail:
740 | School
741 | Number of units
742 | Years attended
743 | Degree(s) attained
744 | Special skills/qualifications
745 | Training certifications (multiple):
746 | Certification/license type
747 | Date obtained
748 | Date of expiration
749 | Endorsements
750 | Remarks
751 | Courses and seminars attended (multiple):
752 | Dates
753 | Course name/title
754 | Course number
755 | Course fees/training costs
756 | Date training started (if applicable)
757 | Date training ended
758 | Hours completed
759 | Location
760 | Instructor
761 | Vendor/training provider
762 | Instructor/school
763 | Certification number
764 | Completion status
765 | Grade received
766 | Reason for not attending (free form)
767 | Course Description
768 | Range qualifications:
769 | Weapons trained to operate
770 | Shooting score ranges
771 | Qualified to instruct:
772 | Courses
773 | Qualification expiration date
774 | Ability to link training records to personnel records.
775 | Ability to define training courses that contain one topic or multiple training topics.
776 | Ability to enter characteristics of topics, includintg dates, names, times, hours, and description.
777 | Ability to link special skills to CAD.
778 | Ability to link certifications to CAD.
779 | Ability to send annual reminders to check validity of special skills, update training record.
780 | Ability for notifications to be distributed to multiple individuals (e.g., individual and supervisor)
781 | Training Management
782 | Ability to track mandatory training requirements for each position/rank or team affiliation.
783 | Ability to track mandatory training for each job category.
784 | Ability to generate and print reports indicating upcoming training needs (i.e., who needs what training by what date).
785 | Ability to track ongoing mandatory training and notify supervisors of officers who have not completed mandatory training.
786 | Ability to alert users and supervisors of upcoming certification expirations.
787 | Ability to track follow-up training for personnel who do not pass certification tests.
788 | Ability to track firearms qualifications (e.g., trigger notification to employees and supervisors of upcoming qualifications).
789 | Ability to generate and print reports showing personnel who failed firearms qualifications.
790 | Ability for individuals to request and register for training online.
791 | Ability to capture and track training evaluations by course.
792 | Ability to capture and track training evaluations by instructor.
793 | Standard Training Module Outputs
794 | Ability to view individual training records at remote work stations.
795 | Ability to retrieve training records by:
796 | Name
797 | Employee ID
798 | Department ID
799 | Training type
800 | Instructor
801 | Course location
802 | Course
803 | Course Topic(s)
804 | Course date
805 | Certifications
806 | Ability to query training schedules based on a user-defined date range for a group or individual.
807 | Ability to track costs of training, including but not limited to:
808 | Individual course
809 | Individual personnel
810 | By division
811 | By type of training (e.g., peer training)
812 | As percentage of training budget
813 | Ability to display or print class roster information, including:
814 | Date for each class/program
815 | List of all participants, station/shift
816 | Grade information
817 | Instructor name
818 | Ability to produce training records for:
819 | Certified classes
820 | State or national academy classes
821 | Ability to print a summary of training activity by:
822 | Individual
823 | Training type
824 | Ability to create certificates.
825 | Ability to print certificates.
826 | Ability to display or print the following:
827 | Employees by certification
828 | Certification renewals by date
829 | Instructor certifications
830 | List of individuals that have not completed specific training
831 | Ability to generate summary reports for individuals that are certified, uncertified, due for certification, and overdue for certification.
832 | Field Training Program - OJT
833 | Ability to document field training for officers during on the job field training.
834 | Ability to create daily individualized training plans covering numerous ares of training.
835 | Require supervisors to sign-off on daily progress reports containing field training scores and elavuations.
836 | Provide detailed 'grading' analysis of officers progress.
837 | Create reports to comare and contrast training results, in order to evaluate officers being trained.
838 | Ability to import call for service information from CAD (or the CFS module in the RMS) to track:
839 | Field training hours worked
840 | Calls for service
841 | field contacts
842 | Court appearances
843 | Ability to link reports prepared by officers in on the job training to the field training record.
844 | Ability to consolidate information contained in the field training record to prepare a summary report.
845 | Ability for a field training officer to enter observation reports into field training record.
846 | Ability to track field training release date.
847 | Citations and Crash Reporting
848 | General [NAME]
849 | Ability to provide dedicated fields (as opposed to narrative/comments fields) to capture all citation information captured in Sector.
850 | Ability to link a citation to a related incident report(s).
851 | Standard Citations Module Outputs
852 | Ability to produce a summary of citations by:
853 | Offense code
854 | Offense type (criminal or civil)
855 | Date
856 | Officer
857 | Shift
858 | Demographic data
859 | Geographic area
860 | Violator
861 | Date range
862 | Towed Vehicles
863 | Towed Vehicle Requirements
864 | Ability to provide dedicated fields to document towed and impounded vehicles as required by the State of Washington.  A copy of the "Uniform Washington State Tow/Impound and Inventory Record" is available upon request.
865 | Ability to link tow record to case report.
866 | Ability to automatically query WACIC/NCIC upon entry into the RMS to search for potential matches of missing/stolen vehicles.
867 | Ability to link a towed vehicle to release time parameters for DUI holds.
868 | Standard Towed Vehicle Module Outputs
869 | Ability to generate a list of towed vehicles by any combination of towed vehicle descriptors.
870 | Ability to display towed vehicles on a map for a user-defined time period.
871 | Ability to generate a report displaying all seized vehicles within a user-defined time period.
872 | Ability to generate a report displaying all impounded vehicles within a user-defined time period.
873 | Case Management
874 | General Case Management Requirements
875 | Ability to accommodate a multi-jurisdictional configuration:
876 | Provide for case management at the individual agency level
877 | Provide for case management at the division level (e.g., to segregate gang-related investigations).
878 | Provide for case management at the investigative unit level
879 | Accommodate different business rules for different agencies
880 | Accommodate different business rules for different divisions
881 | Accommodate different business rules for different units
882 | Provide security controls to limit access to individual agency  records
883 | Provide dedicated fields to track ORI of multiple agencies (e.g., reporting agency, investigating agency, recovery agency, etc.)
884 | Ability for users to electronically send reports to an investigator supervisor.
885 | Ability to support multiple case numbers.
886 | Ability for a case to be associated with multiple agencies.
887 | Ability to define security for documents in the following ways:
888 | Author and creator can edit document while others have read-only access
889 | Primary officer assigned to the case can edit the document
890 | Ability to create case reminders.
891 | Ability to associate charges to a name in a case.
892 | Ability to mark a case as a "cold case"
893 | Ability to identify the following in a case:
894 | Protocol
895 | Child Death Review
896 | Domestic Violence
897 | Juvenile
898 | In Custody
899 | Firearms Seized
900 | [NAME]
901 | [NAME]
902 | Dumpsite
903 | Precursor
904 | [NAME]
905 | NonLab Callout
906 | Marshals TF
907 | Ability to identify that a grant is being used for a case.
908 | Ability to assign multiple crime codes to a case.
909 | Ability to assign multiple case types to a case.
910 | Ability to identify gagns associated with a case.
911 | Ability to generate a cover report listing all basic information about a case.
912 | Ability to link to forensics photos in a viewer that does not allow the photos to be printed or downloaded.
913 | Ability to add names to a case and identify that person's involvement in the case.
914 | Ability to identify primary case number in event multiple case numbers are used.
915 | Ability for reports to be automatically sent to an investigator supervisor based on built-in business logic (e.g., crime type).
916 | Ability to generate and print case labels using County-defined data elements.
917 | Ability to send reports to position profile as opposed to a specific person.
918 | Ability to establish case management work flow based on built-in business logic (e.g., incident type or case type).
919 | Ability for users to receive case referrals electronically.
920 | Ability to track case management activities including, but not limited to:
921 | Capturing and storing investigation data
922 | Interviews
923 | Producing supplemental reports
924 | Obtaining and executing search warrants
925 | Obtaining and executing arrest warrants
926 | Initiating criminal charges
927 | Case disposition
928 | Prosecution requests for investigative follow-up
929 | Ability for each agency to define the specific case management activities it wants to track.
930 | Ability for each agency to define the time allocation for each activity it wants to track.
931 | Ability to calculate case solvability based on agency-defined criteria.
932 | Ability to limit access to case information by security profile at the following levels:
933 | Case level
934 | Case document level
935 | Field level
936 | Ability to perform  case management activities from a Mobile environment.
937 | Investigation Assignment
938 | Ability for investigator supervisors to view unassigned cases online.
939 | Ability for investigator supervisors to review unassigned cases (e.g. read the reports) online.
940 | Ability for an investigator supervisor to electronically assign case responsibility to an officer.
941 | Ability to assign investigative officers to roles, including but not limited to:
942 | Primary
943 | Secondary
944 | Former
945 | Ability for investigators, officers or agency-specified groups to receive electronic notification that they have been assigned a new case via:
946 | [NAME]
947 | Log -on to RMS
948 | Ability for an investigator supervisor to identify cases not assigned for investigation or follow-up.
949 | Ability to document case activity due dates:
950 | Interim activity due date
951 | Final case due date
952 | Ability to extend due dates.
953 | Ability to document due date extensions without losing the original due date.
954 | Ability to label a case as "Early Case Resolution" (ECR).
955 | Ability for any case labeled as ECR to automatically calculate case due date as within 72 hours of labeling.
956 | Ability for any case labeled as ECR to automatically create an alert that notifies the assigned investigator within 72 hours of labeling.
957 | Case Monitoring
958 | Ability for investigator supervisors to monitor case activity including, but not limited to:
959 | Case status
960 | Responsible investigator
961 | Pending activities
962 | Overdue activities
963 | Ability for investigator supervisors to monitor investigators' workloads.
964 | Ability for agency to define types of investigations activities it wants to track (e.g., drop down menu of activities).
965 | Ability to provide dashboard-type functionality that provides a snapshot of current case monitoring information (e.g., number of cases, case statuses, etc.).
966 | Ability to provide a notes field associated with each case.
967 | Ability to provide multiple notes fields associated with each case.
968 | Ability for notes to capture date, time, note type and user ID of individual entering note.
969 | Ability for system to capture a log of communications that occur within the case management system.
970 | Ability for investigator supervisors to reassign cases to different investigators.
971 | Ability for investigator supervisors to electronically notify investigators of case reassignments via:
972 | [NAME]
973 | Log -on to RMS
974 | Ability to visually distinguish case status (e.g., by color, font, underline, italics, etc.).
975 | Ability to generate reports, including but not limited to the following reports:
976 | Cases by due date
977 | Assigned cases
978 | Assigned cases by supervisor
979 | Assigned cases by unit/section
980 | Cases pending assignment
981 | Statistical reports of solvability
982 | Case status (e.g., open, closed, etc.)
983 | Pending activity by investigator
984 | Pending activity by case
985 | Agency case disposition
986 | Court case disposition
987 | Agency-defined
988 | Investigation Management
989 | Ability for investigators to document case activity including, but not limited to, the following:
990 | Assigned follow up activity
991 | Completion of follow up activity
992 | Developing and tracking leads
993 | Interviews and interrogations
994 | Warrant requests
995 | Warrant statuses
996 | Writing supplemental reports
997 | Case notes
998 | Initiating criminal charges
999 | Prosecution requests for investigative follow-up
1000 | Agency case disposition
1001 | Court case disposition
1002 | Evidence collection
1003 | Seizures
1004 | Agency-defined activities
1005 | Ability for the supervisor to assign tasks to other investigators or officers.
1006 | Ability for supervisor to track tasks assigned to other investigators or officers by case.
1007 | Ability for an investigator to place an alert on an individual:
1008 | To send a notification to the investigator through the system of any query involving the individual
1009 | To send a notification via text message to the investigator's cell phone of any query involving the individual
1010 | To send a notification of any query on that individual without alerting the person making the query
1011 | To tell the person making a query on that individual to call the investigator
1012 | Ability to flag a property item such that the assigned investigator is notified when person makes inquiries on their property.
1013 | Ability to create an alert to determine when additional action is due (e.g., supplement report is due within 30 days of assignment).
1014 | Filing Charges
1015 | Ability to generate an application for criminal complaint.
1016 | Ability to generate a comprehensive document containing:
1017 | Charging recommendations
1018 | Case summary (e.g. of status and documentation)
1019 | All required case documents managed within the system
1020 | Ability to support electronic approval (e.g. by supervisor) prior to submitting case to the prosecuting attorney.
1021 | Allow officer to group 'reports' and imaged documents and submit them to the prosecutor as a referral packet, for charging consideration.
1022 | Ability to notify personnel upon completion of case.
1023 | Ability to document prosecutor or court requests for further investigation.
1024 | Ability to document prosecutor charging decisions.
1025 | Ability, for drug charges, to notate the number of drugs involved.
1026 | Additional Documentation
1027 | Ability to generate templates for additional case investigation documentation, including but not limited to:
1028 | Affidavits
1029 | Search warrants
1030 | Agency-defined
1031 | Ability to track the following related to each of the above listed documents:
1032 | Author/Officer Name
1033 | Status (e.g., issued)
1034 | Date of issuance
1035 | Ability for each agency to develop templates.
1036 | Ability to generate search warrant requests from the field.
1037 | Ability for above listed templates to pre-populate with data fields determined by the County, dependent upon document type (in case required fields are different between document types).
1038 | Case Disposition
1039 | Ability to provide dedicated fields to track agency case disposition.
1040 | Ability to provide dedicated fields to track court case disposition.
1041 | Ability to provide dedicated fields to track NIBRS case disposition.
1042 | Ability to request property release upon case closure.
1043 | Standard Case Management Module Outputs
1044 | Ability to produce the following standard reports:
1045 | Case aging report
1046 | Assigned cases and status
1047 | Cases pending assignment
1048 | Activity follow-up
1049 | Overdue activity (e.g. case assignment, follow-up)
1050 | Pending activity by:
1051 | Investigator
1052 | Case
1053 | Investigative Unit
1054 | Law enforcement case disposition
1055 | Court case disposition
1056 | Ability to provide statistical analysis of case status, including:
1057 | Percentage of Cases Solved:
1058 | by investigative unit
1059 | by individual
1060 | by division
1061 | by agency
1062 | Percentage of Cases Unsolved:
1063 | by investigative unit
1064 | by individual
1065 | by division
1066 | by agency
1067 | Ability to conduct comparative analysis against:
1068 | All crimes
1069 | Assigned cases
1070 | Crime type
1071 | Agency-defined parameter
1072 | Ability to run the following reports either by date and jurisdiction or by date and responsible unit:
1073 | Semi-Annual statistics by cases:
1074 | Cases assigned
1075 | Case Investigations Completed
1076 | Case Investigations Solved
1077 | Case Investigations Inactivated
1078 | Case Investigations Resulting in Arrests
1079 | Semi-Annual statistics by number of police reports
1080 | [NAME]
1081 | [NAME]
1082 | Reports Investigations Solved
1083 | Reports Investigations Inactivated
1084 | Reports Investigations Resulting in Arrests
1085 | Ability to run reports for a specific unit (e.g., [NAME]) that captures the following information:
1086 | Number of cases
1087 | Number of arrests
1088 | Number of felony charges
1089 | Number of misdemeanor charges
1090 | Number of gang felony drug related charges
1091 | Number of gang misdemeanor drug related charges
1092 | Number of gang related cases
1093 | Number of search warrants
1094 | Ability to run reports for a specific unit (e.g., Drug unit) that captures the following information:
1095 | Number of arrests by type of drug by jurisdiction
1096 | Number of felony drug charges by jurisdiction
1097 | Number of misdemeanor charges by jurisdiction
1098 | Number of marijuana grows by jurisdiction
1099 | Number of meth labs, dumpsites, precursor by jurisdiction
1100 | Number of cases that are part of a grant by jurisdiction
1101 | Juvenile
1102 | General [NAME]
1103 | Ability to expunge juvenile data based on current age.
1104 | Ability to generate a report/list that identifies expunged juvenile data.
1105 | Ability to visually distinguish any juvenile arrest reports from non-juvenile arrest reports.
1106 | Ability to restrict access to juvenile records by security group.
1107 | Ability to automatically archive juvenile information when requisite time has passed or subject reaches age of emancipation (whichever occurs first).
1108 | Ability to prevent juvenile information from being available in standard queries.
1109 | [NAME]
1110 | Ability to provide dedicated fields to document juvenile runaway/missing person settlement report including but not limited to:
1111 | Runaway/Missing person information:
1112 | Name
1113 | Alias
1114 | Race
1115 | Ethnicity
1116 | Date of Birth
1117 | Age
1118 | Height
1119 | Weight
1120 | Hair
1121 | Eyes
1122 | Descriptors
1123 | Address
1124 | Residential Status
1125 | Place of Employment
1126 | Place of School
1127 | Phone Number
1128 | [NAME] (e.g., Social Security Number)
1129 | [NAME]
1130 | Social Network Information
1131 | Parent/Guardian Information
1132 | Disposition (e.g., retained, released, etc.)
1133 | Ability to capture the following location information:
1134 | Location of Incident
1135 | Location of Settle Incident
1136 | Location of Detention/Release
1137 | Ability to capture the following officer involved information:
1138 | Name
1139 | Officer ID
1140 | Unit ID
1141 | Date
1142 | Ability to cross-reference a runaway/missing person report with another incident.
1143 | [NAME]
1144 | Ability to provide dedicated fields to document juvenile contact, including but not limited to:
1145 | Subject information
1146 | Parent or guardian information
1147 | Type of contact (field contact, arrest, etc.)
1148 | Offenses
1149 | Ability to associate a juvenile with adult status (e.g., [NAME] is a declined juvenile).
1150 | Ability to associate the date of declination.
1151 | Ability to alert user when querying or entering juvenile information that the juvenile has been declined (e.g., declination alert).
1152 | Ability for declination alert to expire based upon an agency-defined time frame (e.g., when subject turns 23)
1153 | Ability to provide dedicated fields to document information regarding juveniles arrested, including, but not limited to:
1154 | Case Number
1155 | Offense/Incident
1156 | Complainant's Name
1157 | Date/Time Reported
1158 | Address
1159 | Home phone
1160 | Work phone
1161 | Cell phone
1162 | Location of Offense
1163 | Date/Time of Offense
1164 | Charge Code
1165 | School/Grade
1166 | Employer
1167 | Place of Birth
1168 | Probation Officer
1169 | Arrested/detained information:
1170 | Where
1171 | Authorized by (e.g., judge, probation officer, intake officer, etc.)
1172 | Date/Time
1173 | Guardian information (multiple):
1174 | Parent type (mother, father, stepmother, stepfather, guardian, relative, etc.)
1175 | Name
1176 | Address
1177 | Length of time in custody (start and finish time as well as date and time)
1178 | Released to
1179 | Type arrest activity
1180 | Standard [NAME]
1181 | Ability to generate a report showing juveniles in custody for a specified time period.
1182 | Ability to generate a report identifying individuals that turn a certain age between a user-defined time period (e.g., individuals turning 23 between January 1 and March 1) identifying:
1183 | Case Number
1184 | Name
1185 | Arrest Date
1186 | Current Age
1187 | DOB
1188 | Age At Arrest
1189 | Ability to generate a juvenile contact report for a specified individual.
1190 | Allow for electronic disemmination of reports involving a juvenile to the juvenile Social Files Unit. |  |  |  |  |  | Added by ISD
1191 | Intelligence
1192 | General [NAME]
1193 | Ability to provide a separate database to store intelligence records.
1194 | Ability to comply with the Criminal Intelligence Systems Operating Policies (28 CFR Part 23 requirements).
1195 | Ability to limit access to intelligence and informant database.
1196 | Ability to track intelligence records in the RMS.
1197 | Ability to track informant records in the RMS.
1198 | Ability to provide dedicated fields to capture the following intelligence data:
1199 | Activity:
1200 | Date
1201 | Type of Activity (County-defined)
1202 | Offense
1203 | Case Number
1204 | Reporting Officer
1205 | Employee Number
1206 | Source of information
1207 | Narrative
1208 | Ability to provide fields to capture information on Criminal Informant Activity, including but not limited to:
1209 | Criminal Informant number
1210 | Location
1211 | Date
1212 | Case Number
1213 | Information Money
1214 | Purchase Money
1215 | Narrative
1216 | Entered by
1217 | Entered on
1218 | Ability to attach files to all above types of data.
1219 | Ability to associate multiple informant numbers to a single informant.
1220 | Ability to manually create criminal informant numbers.
1221 | Ability to maintain historical records of informant numbers.
1222 | Ability to link informants to a case.
1223 | Ability to notify users when new intelligence information is added.
1224 | Ability to track tips (e.g. drug, gang, vice, underage sales of tobacco and alcohol to minor, etc.), including:
1225 | Date
1226 | Time
1227 | Location
1228 | Type
1229 | Tip (narrative of unlimited length)
1230 | Follow-up activity
1231 | Source
1232 | Complainant
1233 | Disposition
1234 | Ability to query any data element stored under Tips.
1235 | Ability to provide an ability to electronically route Tips to appropriate personnel via:
1236 | Specific personnel
1237 | Unit
1238 | Division
1239 | Ability for personnel to "subscribe" to receiving tips.
1240 | Narcotics Investigations
1241 | Ability to track narcotics investigations in the system.
1242 | Ability to keep narcotics investigations separate in the system per intelligence rules.
1243 | Ability to provide dedicated fields to capture the following narcotics investigations data, including but not limited to:
1244 | Date Received
1245 | Complaint
1246 | Reported by
1247 | Address
1248 | Target Area
1249 | Narrative
1250 | Assigned to
1251 | Date Closed
1252 | Disposition
1253 | Case Number
1254 | Entered by
1255 | Entered on
1256 | Ability to provide dedicated fields to track investigations activity related to vice narcotics, including but not limited to:
1257 | Investigative hours:
1258 | Report
1259 | [NAME]
1260 | Search Warrant
1261 | Other
1262 | Total
1263 | Drugs Seized (multiple):
1264 | Type
1265 | Quantity
1266 | Value
1267 | Total
1268 | Other Seized:
1269 | Type
1270 | Quantity
1271 | Value
1272 | Funds Expended:
1273 | Informant
1274 | Expenses
1275 | Drug Buys
1276 | Total
1277 | General [NAME]
1278 | Ability to flag individuals with gang records in the Master Name Index.
1279 | Ability to retrieve gang information when query returns a name flagged with a gang record.
1280 | Ability to provide security provisions at the user level to:
1281 | Create gang records
1282 | Modify gang records
1283 | Ability to provide dedicated fields to capture the following gang-related data:
1284 | Alliance/origin
1285 | Race
1286 | Ethnicity
1287 | Colors
1288 | Locations
1289 | Subsets/cliques
1290 | MOs
1291 | Weapons
1292 | Vehicles and roles
1293 | Associated gangs
1294 | Activities
1295 | Members
1296 | Associates
1297 | [NAME] and vehicle relationships
1298 | Officer safety threat (flag)
1299 | Moniker
1300 | Member status (active or inactive)
1301 | Gang rank
1302 | Gang status (active, inactive, DOC, ICE, etc.)
1303 | Gang classification (member, associate, hang-around, etc.)
1304 | Ability to attach files (e.g., photos) to a gang record.
1305 | Ability to limit access to County-specified fields, including photos, within the gang database by:
1306 | Individual
1307 | Rank
1308 | Unit
1309 | Ability to identify juvenile gang members.
1310 | Ability to document criteria used to identify individual as a gang member.
1311 | Ability to flag open cases as "gang-related" (permission based).
1312 | Ability to auto-populate the gang database with information from the MNI once an individual is identified as a gang member.
1313 | Property and Evidence
1314 | General Property and Evidence Management Requirements
1315 | Ability to track:
1316 | Property collected as evidence
1317 | Impounded property
1318 | Found property
1319 | Property reported as stolen
1320 | Missing property
1321 | Remotely stored property
1322 | Safekeeping
1323 | Ability to assign a property number to a piece of property.
1324 | Ability for associated property (e.g., found at same location) to be logically associated (e.g., Property #1, Items A - Z).
1325 | Ability to collect and track property and evidence information, including but not limited to:
1326 | Property number
1327 | Case number
1328 | Incident information
1329 | Recovering Officer name and badge/serial number
1330 | Investigating officer name and badge/serial number
1331 | Property clerk name and serial number
1332 | Property supervisor name and serial number
1333 | Property/evidence type (evidence, found, safekeeping, impound, special, etc.)
1334 | Article information
1335 | Disposition
1336 | Article location
1337 | Lab exam requirements
1338 | Seized from
1339 | Finder's information
1340 | Property owner/claimant information
1341 | Ability to capture all required NCIC fields for article-specific information (e.g., weapons, currency, drugs, etc.)
1342 | Ability to automatically run all items with serial numbers through NCIC upon entry of the item.
1343 | Ability, upon entry of item into the RMS, to automatically scan the system for potential duplicates.
1344 | Bar Coding
1345 | Ability to use bar codes for:
1346 | Evidence entry
1347 | Transactions
1348 | Chain of custody change
1349 | Inventories
1350 | Audits
1351 | Mass data updates
1352 | Ability to capture a date and time stamp with any bar code activity.
1353 | Ability to print bar code labels in the field.
1354 | Ability for bar codes to be automatically generated from the RMS.
1355 | Ability to generate a single bar code label for all items under a property number.
1356 | Property and Evidence Collection
1357 | Ability to import property information from the incident report into the property record.
1358 | Ability to generate a receipt for items taken into property and evidence.
1359 | Ability to generate a bar code label with property information:
1360 | Item number
1361 | Property number
1362 | Case number
1363 | Ability to assign a unique sequential control number to each property item.
1364 | Ability to add investigator responsible for a case to the property record upon case assignment to the investigator.
1365 | Ability to run checks for property matches upon checking property into evidence:
1366 | Internal RMS databases (e.g., master indices)
1367 | External databases (e.g.,  NCIC, the Beast)
1368 | Chain of Custody
1369 | Ability to track chain of custody data for any piece of property entered into the system as evidence, including but not limited to:
1370 | Initial property collection information:
1371 | Seizing officer name and badge number/serial number
1372 | Location collected
1373 | Date/time item was submitted
1374 | Temporary storage location
1375 | Officer picking up item name and badge number/serial number
1376 | Date and time picked up
1377 | Date and time checked into evidence warehouse
1378 | Location in evidence warehouse
1379 | Check-out/check-in information:
1380 | Transferred by evidence personnel (name and badge number/serial number)
1381 | Transferred to (name, badge number/serial number, agency)
1382 | Time and date of check-out
1383 | Reason for check-out
1384 | Destination
1385 | Received by evidence personnel (name and badge/serial number)
1386 | Received from (name and badge/serial number, agency)
1387 | Time and date of check-in
1388 | Location returned to
1389 | Ability to capture electronic signatures.
1390 | Ability to track viewing of a property item, including but not limited to:
1391 | Start and end time of viewing
1392 | Evidence viewed by:
1393 | Property number
1394 | Item number
1395 | Location of viewing
1396 | Persons present during viewing (multiple)
1397 | Reason for viewing
1398 | Ability to provide automatic reminders that checked-out items are overdue.
1399 | Ability to include due dates for items to be returned.
1400 | Ability to scan bar code during check-out and check-in to update chain of custody (e.g., time and date information are populated and the user only adds information not in the system).
1401 | Ability to generate a chain of custody report for a property item entered into the system as evidence.
1402 | Ability to query a property item and identify its location from the chain of custody information.
1403 | Ability to mass check out evidence.
1404 | Ability to read a single bar code label for all items under a property number.
1405 | Inventory and Audits
1406 | Ability to generate a list of all property located in a given:
1407 | Property room area
1408 | Shelf
1409 | Bin
1410 | Ability to scan all items in a given location to check that items on a list of property are in the proper location.
1411 | Ability to generate a report of missing property items.
1412 | Ability to generate a list of items in a given location that are not on the generated list of property items that are supposed to be in that location.
1413 | Ability to document whether items on a random inventory list are in the proper location.
1414 | Ability to conduct a full inventory of property by:
1415 | Location
1416 | Case number
1417 | Involved parties (owner, seized from, etc.)
1418 | Personnel badge/serial number
1419 | Type of property
1420 | Ability to enter in a case number display:
1421 | A list of associated evidence
1422 | The location of associated evidence
1423 | Property and Evidence Disposition
1424 | Ability to classify property for disposal through:
1425 | Return to owner
1426 | Destruction
1427 | Conversion to police usage
1428 | Auction
1429 | Ability for agency to identify review dates for different types of property (e.g., 60 days for found/safekeeping, 30 years for homicide).
1430 | Ability to set property and evidence retention time frames based on:
1431 | Evidence/property type
1432 | Disposal status
1433 | Offense type
1434 | Ability to maintain property records after property disposal.
1435 | Ability to alert investigators of items that require review.
1436 | Ability to alert property and evidence personnel of items that require review.
1437 | Ability to alert property and evidence personnel of property items eligible for disposition.
1438 | Ability to add disposal information to a property record, including but not limited to:
1439 | Disposal method
1440 | Disposal date
1441 | Disposal reason
1442 | Ability to track the information associated with property released to an owner, including but not limited to:
1443 | Released to
1444 | Drivers license or other government ID of person
1445 | Released by
1446 | Date of release
1447 | Ability to document that proper checks were run to ensure that the claimant can receive property.
1448 | Property should not become eligible for disposal until it is cleared under all cases with which it is associated.
1449 | Ability to require multiple levels of approval prior to property becoming eligible for disposal.
1450 | Ability to produce scheduled reports showing property eligible for disposal.
1451 | Ability to view a destruction report and perform the following:
1452 | Accept or reject a piece of property/evidence for destruction
1453 | Change property/evidence status of those accepted to "flagged for destruction"
1454 | Ability to generate a report of property eligible for return to owner.
1455 | Ability for user to view a "return to owner" report and perform the following:
1456 | Accept or reject a piece of property/evidence for return
1457 | Change property/evidence status of those accepted to "flagged for return to owner"
1458 | Generate a notice to property owners that their property is ready to be retrieved.
1459 | Ability to generate a report of items eligible for auction.
1460 | Ability to view an auction report and perform the following:
1461 | Accept or reject a record
1462 | Assign an auction value
1463 | Add auction comments
1464 | Note auction location
1465 | Flag an item for auction
1466 | Record the date of auction
1467 | Ability to assign a batch disposition of all items by the following:
1468 | Date
1469 | Bin location
1470 | Ability to assign disposition of all items attached to a case at the same time.
1471 | Reports and Output
1472 | Ability to generate a Property Disposition report for appropriate officers identifying the following:
1473 | Officer:
1474 | Name
1475 | Serial/Badge Number
1476 | Division
1477 | Property:
1478 | Number
1479 | Case number
1480 | Type
1481 | Date
1482 | Seized from
1483 | Location
1484 | Victim
1485 | Owner information
1486 | Item number
1487 | Quantity
1488 | Property type
1489 | Disposition
1490 | [NAME]
1491 | Reason for hold
1492 | Ability for report to provide fields for investigating officer to provide recommended actions (e.g., hold, dispose, return, etc.)
1493 | Electronic Evidence Management
1494 | Ability to provide a database to store electronic media (e.g., videos, photos, audio, etc.)
1495 | Ability to store both:
1496 | Compressed Video
1497 | Uncompressed video
1498 | Ability to link electronic media to a master record, including:
1499 | Name record
1500 | Vehicle record
1501 | Location record
1502 | Incident Record
1503 | Organization Record
1504 | Ability to link multiple pieces of a electronic media to a master record.
1505 | Ability to attach electronic media to an incident report.
1506 | Ability to attach electronic media to a property record.
1507 | Ability to flag files that notify user evidence is not be released.
1508 | Asset and Supply Management
1509 | Supplies and Equipment Acquisition
1510 | Ability to provide dedicated fields to record the receipt of an inventoried item:
1511 | Item type
1512 | Item name
1513 | Item description
1514 | Inventory or asset number (e.g. bar code)
1515 | Date received
1516 | Date ordered
1517 | Expiration date
1518 | Warranty information
1519 | Ordering party (e.g., individual, unit, agency, etc.)
1520 | [NAME] approving party
1521 | Serial number
1522 | Quantity
1523 | Ability to record the receipt of inventory by scanning a bar code.
1524 | Ability to update inventory totals:
1525 | Upon receipt of new inventory
1526 | Upon assignment of inventoried items
1527 | Ability to generate an automatic alert to designated personnel when inventory levels fall below an agency-defined level.
1528 | Ability to track vendor information:
1529 | Company name
1530 | Point of contact
1531 | Address
1532 | Telephone number
1533 | Order history
1534 | Supplied goods (e.g., item vendor supplies)
1535 | Supplies and Equipment Assignment
1536 | Ability to provide dedicated fields to capture, maintain and track equipment, supplies and clothing assigned to personnel, including, but not limited to, the following:
1537 | Issued to:
1538 | Name
1539 | Rank/Title
1540 | Agency
1541 | Serial/Badge No.
1542 | DES
1543 | Assignment (e.g., Patrol, Communications, Property, etc.)
1544 | Item name (agency defined items)
1545 | Status (issued, returned, total currently issued)
1546 | Date issued (for each item)
1547 | Disposal date
1548 | Expiration date
1549 | Inventory number (e.g., barcode)
1550 | Make
1551 | Model
1552 | Serial number
1553 | Replacement date(s)
1554 | Service date
1555 | Tag number
1556 | Description
1557 | Size
1558 | Cost
1559 | Comments
1560 | Ability to capture history of equipment assigned to an individual.
1561 | Ability to track history of assigned equipment, specific to the equipment.
1562 | Ability to an associate a disposition with equipment
1563 | Ability to "deactivate" equipment (e.g., maintain a record of a piece of equipment that is not issued).
1564 | Ability to record acknowledgement from personnel that they received issued equipment.
1565 | Ability to perform batch updates related to a single individual (e.g., remove multiple pieces of equipment from an individual as opposed to singularly removing each piece of equipment).
1566 | Ability to track the daily assignment of items (e.g., weapons, vehicles).
1567 | Ability to track multiple pieces of the same type of equipment assigned to one individual.
1568 | Ability to capture, maintain, and track firearms and ammunition assigned to personnel, including, but not limited, to the following information:
1569 | Agency defined identification number
1570 | Serial number
1571 | Date issued
1572 | Employee ID
1573 | Department ID
1574 | Employee name (assigned to)
1575 | Inspected by
1576 | Inspected date
1577 | Issued by
1578 | Maintenance requirements (description)
1579 | Maintenance performed (description)
1580 | Quantity issued
1581 | Received by
1582 | NCIC codes identifiers (model, make, serial number, caliber, color) with a default for agency-defined standard issue
1583 | Ability to provide dedicated fields to gather information on  department assets assigned to vehicles, stations, locations, and departments (e.g. computers, video cameras, etc.) including, but not limited to, the following information:
1584 | Asset tag number
1585 | Bar code number
1586 | Brand
1587 | Classification
1588 | Cost
1589 | Date issued/acquired
1590 | Description
1591 | Diameter
1592 | Disposal date
1593 | Equipment type
1594 | Length
1595 | Location in station
1596 | Location on vehicle
1597 | Manufacturer
1598 | Model
1599 | Part number
1600 | Serial number
1601 | Size
1602 | Station/company assigned to
1603 | Vehicle assigned to (e.g., Vehicle ID)
1604 | Warranty information
1605 | Ability to easily transfer equipment to a different vehicle/location without re-keying descriptive data (e.g. drag and drop or a quick transfer function).
1606 | Ability to track when equipment is sent for repair/replacement.
1607 | Ability to track the status of equipment no longer in possession of agency (e.g., sent to manufacturer for repair).
1608 | Ability to document purchase orders.
1609 | Equipment Return
1610 | Ability to check equipment back into inventory.
1611 | Ability to unlink equipment from personnel upon check-in.
1612 | Ability to track replaced equipment:
1613 | Date replaced
1614 | Reason replaced
1615 | Disposition of equipment
1616 | Condition of equipment
1617 | Equipment Maintenance and Replacement
1618 | Ability to create maintenance schedules for equipment requiring regular maintenance.
1619 | Ability to generate reports listing equipment due for maintenance during a user-defined time period (e.g. generate a report on the first of every month for equipment that needs to be replaced by the end of that month).
1620 | Ability to generate reports listing expired equipment during a user-defined time period.
1621 | Ability to document maintenance for a piece of equipment.
1622 | Ability to create replacement schedules for equipment requiring replacement after a period of time (e.g. bullet-proof vests every five years).
1623 | Ability to  generate reports listing equipment due for replacement during a user-defined time period (e.g. generate a report on the first of every month for equipment that needs to be replaced by the end of that month).
1624 | Ability to automatically generate and print, at a user-defined interval, reports listing equipment overdue for replacement (e.g. generate a report on the first of every month for equipment for which replacement is overdue).
1625 | Ability to generate alerts to individuals that their equipment is due for maintenance or replacement.
1626 | Bar Code Tracking System
1627 | Ability to manage and track inventory using a bar code system including, but not limited to, the following functions:
1628 | Perform a mass update
1629 | Locate item by bar code
1630 | Generate bar code
1631 | Read bar code using remote or connected hand-held device
1632 | Track specific item information (e.g., description, quantity, status, etc.)
1633 | Ability to automatically update (e.g., download) inventory information into system.
1634 | Ability to print bar code labels.
1635 | Ability to provide inventory management using a bar code system.
1636 | Standard Asset Management Outputs
1637 | Ability to generate a physical inventory report based on:
1638 | Asset category
1639 | Asset age
1640 | Asset location
1641 | Officer
1642 | Ability to generate a physical inventory exception report.
1643 | Ability to generate a check-in/check-out log for temporarily assigned assets.
1644 | Ability to generate a report showing asset history.
1645 | Offender Registration
1646 | Ability to track registered convicted offenders.
1647 | Ability for the County to define types of convicted offenders for which registration is required.
1648 | Ability to link offender registration records to master indices.
1649 | Ability to provide dedicated fields to capture the following information for each registrant:
1650 | Name
1651 | Aliases
1652 | Social security number
1653 | Date of Birth
1654 | Home Address (multiple)
1655 | Work Address (multiple)
1656 | School Address (multiple)
1657 | Parental information
1658 | Therapist information
1659 | Spouse information
1660 | Telephone Numbers (multiple)
1661 | Physical descriptors
1662 | Classification (multiple)
1663 | State statute requiring registration
1664 | Age of victim at time of offense
1665 | Age of registrant at time of offense
1666 | Offense case disposition
1667 | Modus operandi
1668 | Date registered
1669 | Date updated
1670 | Date review needed (one month prior to date registered/updated and one month later)
1671 | Registration expiration date
1672 | Where convicted (county or state)
1673 | Year convicted
1674 | Vehicle information (type, color, make, model)
1675 | Suspect actions
1676 | Comments
1677 | Employer Information
1678 | Conviction Information
1679 | [NAME]
1680 | Activity
1681 | Relationship Information
1682 | Ability to flag registrants in the Master Name Index.
1683 | Ability to associate probation officer information with each registrant.
1684 | Ability to maintain a history of a registrant's addresses.
1685 | Ability to track law enforcement visits to sex offenders.
1686 | Ability to attach files to registrant records.
1687 | Ability to identify an offender as no longer requiring registration (registrant status).
1688 | Ability to record the date of a registrant photograph.
1689 | Ability to print a report of registrants whose re-registration date is approaching.
1690 | Ability to generate a report of registrants whose did not re-register by the registration date.
1691 | Ability to generate and print a report showing activity related to registrants (e.g. number of registrations, number of visits, number of notifications, etc.).
1692 | Ability to perform a cross-check of the current residence of the registrant with the list of restricted addresses (e.g. schools, day care facilities, etc.).
1693 | Civil Service
1694 | Ability to provide dedicated fields to create Civil Service records, including:
1695 | Civil/Case Number
1696 | Date Issued
1697 | Date Received
1698 | Title/Jurisdiction of agency initiating action
1699 | Expiration Date
1700 | Docket Number
1701 | Court Date(s)
1702 | Plaintiff
1703 | Defendant:
1704 | Subject
1705 | Address
1706 | Status (drop down)
1707 | Status Date
1708 | Officer
1709 | Comments (free form)
1710 | Ability to input narrative (free form)
1711 | Ability to search Master Name Index for potential name matches based on name or identification information.
1712 | Ability to auto-populate Civil Service records with existing information in the Master Name Index.
1713 | Ability to indicate people who have hazards attached to their Master Name record.
1714 | Ability to attach files to Civil Service records.
1715 | Ability to provide dedicated fields to capture information related to the management of civil document service, including, but not limited to:
1716 | Civil Process Number
1717 | Date of Entry
1718 | Time of Entry
1719 | Entry Operator
1720 | Type of Process (agency defined drop down menu)
1721 | Court
1722 | Date of Process
1723 | Process Expiration Date
1724 | Attorney [NAME]
1725 | Attorney Name
1726 | Attorney [NAME]
1727 | Responsible party
1728 | Deposit Amount
1729 | Deposit Method
1730 | Fee type
1731 | Fee amount
1732 | Plaintiff Name
1733 | Defendant Name
1734 | Defendant Address
1735 | Defendant Alternate Address
1736 | Serving Officer
1737 | Ability to update or modify responsible party.
1738 | Ability to provide fields to track due diligence/service attempt history:
1739 | Date of attempt
1740 | Time of attempt
1741 | Location of attempt
1742 | Person(s) contacted
1743 | Attempt successful (Y/N)
1744 | Public safety personnel attempting service
1745 | Agency attempting service
1746 | Located outside of jurisdiction (Y/N)
1747 | Number of attempts
1748 | Method of service
1749 | Reason for nonservice
1750 | Ability for officers in the field to document civil service activity on their mobile computers.
1751 | Ability to update most current address upon learning of new address (e.g., when attempting to serve).
1752 | Ability for data entered in the mobile environment to update the Civil Service module in the RMS.
1753 | Ability for public safety personnel to provide free form narrative on the service of document.
1754 | Ability for administrative officer to input notes/instructions onto the document for view by public safety officer serving the document.
1755 | Ability to query Civil Service records by:
1756 | Officer
1757 | Date range
1758 | Type of document (drop down)
1759 | Process expiration date
1760 | Involved party
1761 | Ability to accommodate multiple fees on one Civil Service record.
1762 | Ability to accommodate multiple fee types on one Civil Service record.
1763 | Ability to create a billing statement that tracks all financial transactions associated with a case.
1764 | Ability to produce an internal tracking document depicting all accounts receivable information.
1765 | Ability to support the electronic routing of Civil documents.
1766 | Trespass Notices and Protection Order Requirements
1767 | Ability to provide dedicated fields to record trespass notices and orders of protection in the system, including, but not limited to, the following information:
1768 | Type of order (e.g., orders of protection, no trespass, injunctions against harassment, orders of release)
1769 | Petitioner information:
1770 | Name
1771 | Date of birth
1772 | Social security number
1773 | Relationship to order
1774 | Respondent information:
1775 | Name
1776 | Date of birth
1777 | Social security number
1778 | Relationship to order
1779 | Terms
1780 | Date of service
1781 | Clearance date, person, reason
1782 | Conditions, including:
1783 | Issuing authority
1784 | Effective time period
1785 | Location
1786 | Restrictions
1787 | Type of contact prohibited (free form text narrative field)
1788 | Arrest clause (Y/N)
1789 | Civil or criminal?
1790 | Ability to attach a photo to a trespass notice or protective order.
1791 | Ability to capture and maintain protection order data as required to conform to NCIC 2000 Protection [NAME] format.
1792 | Ability to generate an alert when a protection order record requires validation based on a user-specified validation schedule.
1793 | Ability to populate protective orders with standard language upon entering NCIC code.
1794 | Ability for user to update NCIC from within the protection order module upon entry or update of a protection order.
1795 | Ability to change an order from temporary to permanent order and update NCIC accordingly.
1796 | Ability to scan a protection order and attach it to a record.
1797 | Ability to update master indices upon entry a protective order.
1798 | Ability to link protective orders to MNI.
1799 | Ability to attach an alert to a person in the MNI if a protection order against that person exists in the system.
1800 | Ability to link a trespass order to a location.
1801 | Ability to maintain history of protective orders for individuals (victims and defendants).
1802 | Ability to generate a report showing who is excluded from a user-defined geographic location.
1803 | Standard Trespass Notice and Protection Order Module Outputs
1804 | Ability to generate the following standard reports:
1805 | Expired orders
1806 | Soon-to-expire orders (based on user-defined time period)
1807 | Orders that have been served
1808 | Cancelled orders
1809 | No trespass orders
1810 | Expungements and Redactions
1811 | Expungements
1812 | Ability to establish and modify purge criteria.
1813 | Ability to comply with Washington State Law Enforcement Retention Guidelines as set by the Secretary of State.
1814 | Ability for system to automatically purge and retain records based upon Washington State Law Enforcement Guidelines.
1815 | Ability to maintain compliance with Washington State Law Enforcement Retention Guidelines.
1816 | Ability to attach purge notes to records.
1817 | Ability to override preset purge criteria and log reason.
1818 | Ability to accommodate the following types of record closings:
1819 | Sealed records
1820 | Expunged records
1821 | Records destroyed by court order
1822 | Vacated records
1823 | Ability for authorized users to provide a system utility to selectively edit and purge information.
1824 | Ability to "de-activate" a record (e.g., makes record unavailable, however, if reactivated, previous record information still exists within the system)
1825 | Ability for authorized users to selectively edit and expunge or seal case information and/or arrest records, including but not limited to:
1826 | Single record
1827 | Single charge
1828 | Group/all records
1829 | All except specific records
1830 | Specific information from a single record
1831 | Ability for expungement utility to differentiate between adult and juvenile.
1832 | Ability for expungement utility to automatically remove appropriate entries from the MNI.
1833 | Ability to selectively purge records and subject information based on user-defined criteria (date, age, etc.).
1834 | Ability to delete a case from the system without deleting an entire person.
1835 | Ability to seal a case without sealing an entire person.
1836 | Ability to seal a person without sealing an entire case.
1837 | Ability to prevent all users without the authority to see a sealed record from seeing that the record exists.
1838 | Ability for a user who is authorized to view a sealed record to see that it exists in the system (e.g., search for the record).
1839 | Ability for an authorized user to view a sealed record.
1840 | Ability to track the following when an authorized user views a sealed record:
1841 | User name
1842 | Date and time stamp
1843 | Court order number
1844 | Redaction
1845 | Ability to electronically redact information.
1846 | Ability to electronically redact user selected information throughout the report (including data fields and narratives).
1847 | Ability to redact information via keyword search.
1848 | Ability to redact information via information type (e.g., redact all name fields)
1849 | Ability to print a redacted report.
1850 | Ability to maintain a log of all redaction requests.
1851 | Ability to maintain a log of all redactions.
1852 | Ability to provide an audit trail of redactions.