{"text_format":"2","workbook":"xlsx","n_sheets":9,"sheets":["Instructions","Admin","CAD","Financial","Jail","Mapping","GIS","Personnel","System"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Instructions","index":0,"n_rows":19,"n_cols":4,"rows_kept":19,"cut":false,"hidden":false,"merged":[]}
["Instructions"]
[]
[null,"Vendors must respond to each requirement by placing an \"X\" into the correct column and adding comments as necessary."]
[]
[null,null,"Yes","Proposed solution meets or exceeds the requirement."]
[null,null,null,"Comment is optional."]
[]
[null,null,"Future","The proposed solution does not currently meet the requirement, but a planned future release will meet the requirement."]
[null,null,null,"Comment is required, and must include a date (mm/yy) when functionality will be built."]
[]
[null,null,"Modify","Proposed solution can be modified to meet the requirement. "]
[null,null,null,"All modifications must be included in the price of the proposal."]
[null,null,null,"Comment is required, and must include a statement about the price being included in the proposal."]
[]
[null,null,"No","Proposed solution does not meet the requirement."]
[null,null,null,"Comment is optional."]
[]
[]
[null,"A failure to enter a response for a given requirement will result in that requirement being defaulted to \"No.\""]

{"sheet":"Admin","index":1,"n_rows":137,"n_cols":8,"rows_kept":137,"cut":false,"hidden":false,"merged":[]}
["Administration"]
[]
["General"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AA1","The system should allow authorized users to create and maintain other users' accounts."]
[null,"AA2","The system should allow authorized users to create and maintain administrative users' accounts."]
[null,"AA3","The system should allow authorized users to create and maintain user groups."]
[null,"AA4","The system should allow authorized users to maintain user permissions by individual users or by user groups.",{"$nulls":4},"Can create user groups for individual users."]
[null,"AA5","The system should fully incorporate user accounts (login, etc.) with personnel records for that user, ensuring that any changes which need to be made to a user's account are made in a single place in the system."]
[]
["Policy Manual"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AB1","The system should provide a means for entering, maintaining and viewing the agency’s policy manual."]
[null,"AB2","The system should organize the policy manual with sections and subsections."]
[null,"AB3","The system should allow authorized users to add and update sections and subsections within the policy manual."]
[null,"AB4","The system should allow formatting options in the policy manual such as boldface and italics."]
[null,"AB5","The system should include a spellchecker for the policy manual."]
[null,"AB6","The system should allow authorized users to view a list of sections/subsections of the policy manual which need to be updated."]
[null,"AB7","The system should allow authorized users to specify effective dates and target re-evaluation dates for sections and subsections of the policy manual. "]
[null,"AB8","The system should track changes to the policy manual and generate a change log."]
[null,"AB9","The system should display a table of contents for the policy manual with links to each section."]
[null,"AB10","The system should display, as part of the table of contents, indicators showing each user any sections he or she has not yet read and any sections which have been updated since he or she last read them."]
[null,"AB11","The system should allow users to navigate between sections of the policy manual."]
[null,"AB12","The system should allow the policy manual to be searched by section or subsection title or by any term found within the text. "]
[null,"AB13","The system should allow users to bulk print desired sections of the policy manual."]
[null,"AB14","The system should generate a log for the policy manual that lists each time a user accessed each section or subsection, including how long the user spent viewing it."]
[null,"AB15","The system should allow a user to read the policy manual which was in force as of a specific date (and not just the most current version of the manual)."]
[null,"AB16","The system should allow authorized users to determine who has read recent policy manual changes or additions and to save, email or print a list of the sections each user still needs to read to be current."]
[]
["Fleet Management"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AC1","The system should allow authorized users to create and maintain agency vehicle records."]
[null,"AC2","The system should allow agency vehicles to be assigned to individual employees, divisions, or sections. "]
[null,"AC3","The system should allow authorized users to maintain lists of service types, service groups and vehicle acquisition methods."]
[null,"AC4","The system should allow agency vehicles to be added to service groups (that is, to bulk assign service schedules)."]
[null,"AC5","The system should allow fleet services types to be configured and scheduled for specified mileage or hour intervals for each vehicle."]
[null,"AC6","The system should allow each agency vehicle to track either odometer or hour-meter readings."]
[null,"AC7","The system should display the latest odometer or hour-meter reading for each vehicle in a highly visible manner. "]
[null,"AC8","The system should provide a means for tracking equipment assigned to each vehicle. "]
[null,"AC9","The system should provide a means of tracking damage to vehicles and the corresponding restitution payments (as appropriate) for that damage."]
[null,"AC10","The system should be able to alert users to upcoming vehicle retirements."]
[null,"AC11","The system should be able to retain retired vehicle records indefinitely."]
[null,"AC12","Agency-defined custom fields should be available in Fleet Management."]
[]
["Vehicle Services"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AD1","The system should allow users to create and maintain fuel records and service records (oil changes, tire rotations, etc.) for each agency vehicle."]
[null,"AD2","The system should calculate each vehicle’s fuel efficiency from the fuel history entered. "]
[null,"AD3","The system should be able to alert users to upcoming scheduled vehicle maintenance. "]
[null,"AD4","The system should allow fuel records and service records to have files attached to them via upload or scanner."]
[]
["Equipment"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AE1","The system should allow authorized users to create and maintain agency equipment item records."]
[null,"AE2","The system should allow authorized users to maintain lists of equipment acquisition methods, disposal types, locations, makes, models, names, types and vendors."]
[null,"AE3","The system should be able to track the specified number of years over which to depreciate an equipment item."]
[null,"AE4","The system should be able to automatically calculate the current value of equipment items using straight line depreciation."]
[null,"AE5","The system should be able to generate an equipment depreciation report for a specified date range."]
[null,"AE6","The system should allow target replacement dates to be specified for equipment."]
[null,"AE7","The system should track assignment of equipment to employees, vehicles, service dogs, divisions, sections, or disposal."]
[null,"AE8","The system should allow authorized users to determine which users or user groups may assign equipment to each division, section, etc."]
[null,"AE9","The system should allow users to create unlimited audit reports for an employee's issued equipment. This report should include all issued equipment and the status of the item at the time of the audit."]
[null,"AE10","The system should be able to generate an assignment history for each equipment item."]
[null,"AE11","The system should allow equipment to be assigned in bulk."]
[null,"AE12","The system should allow equipment items to be assigned barcodes for identification."]
[null,"AE13","The system should support lookup of an equipment item record by scanning the equipment item's barcode."]
[null,"AE14","The system should allow equipment item records to have files attached to them via upload or scanner."]
[null,"AE15","Agency-defined custom fields should be available in Equipment."]
[]
["Inventory"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AF1","The system should allow authorized users to create and maintain inventory item records which are separate from equipment item records. Examples of inventory items might include such things as ammunition and cleaning supplies."]
[null,"AF2","The system should allow authorized users to maintain a list of inventory item statuses, categories and locations."]
[null,"AF3","The system should show whether inventory items are available for use."]
[null,"AF4","The system should provide an alert for low inventory items."]
[null,"AF5","The system should allow inventory items to have barcodes assigned to them."]
[null,"AF6","The system should support lookup of an inventory item record by scanning the inventory item's barcode."]
[null,"AF7","The system should allow inventory items to be added, transferred, and reduced."]
[null,"AF8","The system should allow authorized users to view a list of inventory items that are below agency-defined minimum levels."]
[null,"AF9","The system should allow inventory item records to have files attached to them via upload or scanner."]
[null,"AF10","Agency-defined custom fields should be available in Inventory."]
[]
["Inventory Requests"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AG1","The system should allow authorized users to request additional inventory items."]
[null,"AG2","The system should allow authorized users to track the status of inventory requests."]
[null,"AG3","The system should allow inventory request records to have files attached to them via upload or scanner."]
[null,"AG4","Agency-defined custom fields should be available in Inventory Requests."]
[]
["Purchase Requisitions"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AH1","The system should allow authorized users to complete purchase requisition forms."]
[null,"AH2","The system should allow purchase requisition forms to be assigned to specified users for approval."]
[null,"AH3","The system should allow purchase requisitions to be assigned to specified users (when approved) for purchase of the requested items."]
[]
["Canine Management"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AI1","The system should allow users to create and maintain canine/service dog records."]
[null,"AI2","The system should allow authorized users to maintain lists of activity types for canines."]
[null,"AI3","The system should allow authorized users to assign a canine to a handler."]
[null,"AI4","The system should allow users to track canine activities, certifications, vaccinations, medical visits, and other costs."]
[null,"AI5","The system should allow activity records, certification records, vaccination records, medical visit records, and other cost records to have files attached to them via upload or scanner."]
[null,"AI6","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual canine records or canine activity records."]
[null,"AI7","The system should allow users with access to canine records or canine activity records to use the custom forms to enter and maintain the associated data."]
[null,"AI8","Agency-defined custom fields should be available in Canine Management."]
[]
["Notes"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AJ1","The system should allow authorized users to create general notes which will display on every user's dashboard as configured."]
[null,"AJ2","The system should allow notes to be set as sticky so they will continue to display at the top of the notes list even when other notes are newer."]
[null,"AJ3","The system should allow general notes to have files attached to them via upload or scanner."]
[]
["Administration Reporting"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"AK1","The system should provide a report generator for building custom statistical and analytical reports from administration data. The report generator should be provided by the same vendor and not be a third-party application."]
[null,"AK2","The system should restrict access to the report generator and individual report templates by user or user group."]
[null,"AK3","The system should not allow a user who does not have access to particular data via the application user interface to gain access to that data via the report generator."]
[null,"AK4","The system should allow the creator of the report template to build reports for any data entered into the administration product."]
[null,"AK5","The report generator should allow the creator of the report template to control layout and formatting options for each administration report template. This includes such options as field arrangements, column widths, label text, font sizes, and line spacing."]
[null,"AK6","The report generator should allow the creator of each administration report template to choose which users can access and/or run the report and/or modify the report template."]
[null,"AK7","The report generator should support the use of aggregate (math) functions including Sum, Average, Count, Count Blank, Minimum, and Maximum."]
[null,"AK8","The report generator should allow data to be grouped or sorted by any data element."]
[null,"AK9","The report generator should allow multiple data filters to be applied using \"and/or\" logic."]
[null,"AK10","The report generator should allow administration reports to be saved (as PDF, .XLS, or .CSV), printed, or emailed directly from the report."]
[null,"AK11","The report generator should allow administration report templates to be saved and modified at a later time."]
[null,"AK12","The report generator should support adding the administration reports to user's dashboards."]
[null,"AK13","The report generator should allow recurring administration reports to be scheduled and automatically uploaded to a file-system or e-mailed to specified users on certain days and times."]
[null,"AK14","The report generator should support ad-hoc queries."]
[null,"AK15","The report generator should support creation of administration reports such as the following:\n -  Weapon Assignments\n -  Equipment Issued to Personnel\n -  Inventory\n -  Current Vehicle Assignments\n -  Negative Citizen Feedback\n -  Personnel Birthdays\n -  Personnel Specialties\n -  Personnel Years of Service\n -  Vehicle Replacement Schedule "]
[]
["Interface A"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[]
[]
[]
["Interface B"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]

{"sheet":"CAD","index":2,"n_rows":294,"n_cols":8,"rows_kept":294,"cut":false,"hidden":false,"merged":[]}
["Computer Aided Dispatch (CAD)"]
[]
["General"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CA1","The system should be multi-jurisdictional, allowing dispatching for multiple agencies, including law enforcement, fire, and medical responders."]
[null,"CA2","The system should allow authorized users to design and enforce an agency-wide standard CAD window layout to ensure consistency among workstations, but also to allow users flexibility in configuring their own CAD displays as allowed by the agency."]
[null,"CA3","The system should include a minimum of the following for CAD window layout options: window sizes and arrangements, column options, widths, font types, font sizes, and default list-view filters."]
[null,"CA4","The system should allow customized CAD windows to retain a user or agency’s preference for all layout options."]
[null,"CA5","The system should support both command line and point-and-click entry for all CAD commands."]
[null,"CA6","The system should support drag-and-drop issuance of CAD commands."]
[null,"CA7","The system should allow authorized users to maintain lists of beats and beat plans."]
[null,"CA8","The system should allow authorized users to maintain a list of bulletin types in addition to BOLOs and special instructions."]
[null,"CA9","The system should allow authorized users to maintain a list of CFS dispositions."]
[null,"CA10","The system should allow multiple dispositions to be specified for a single CFS."]
[null,"CA11","The system should allow calls for service to be set up to require dispositions before they can be closed."]
[null,"CA12","The system should allow authorized users to maintain a list of CFS link types (for example, Duplicate of and Related to) to tie multiple calls into the same physical event."]
[null,"CA13","The system should allow authorized users to maintain a list of CFS list filters (to organize information on the primary CFS windows)."]
[null,"CA14","The system should allow authorized users to maintain CFS priority levels."]
[null,"CA15","The system should include inactivity alarm and unit status alarm values, along with the colors, for each CFS priority level."]
[null,"CA16","The system should allow authorized users to maintain a list of CFS response codes."]
[null,"CA17","The system should allow users to maintain a list of recurring scheduled calls for service, such as pager or siren tests."]
[null,"CA18","The system should allow authorized users to maintain a list of fire and/or EMS stations."]
[null,"CA19","The system should allow authorized users to maintain a list of CAD terminals."]
[null,"CA20","The system should allow authorized users to maintain a list of dispatch timers used to alert call-takers and dispatchers to calls waiting to be dispatched."]
[null,"CA21","The system should allow authorized users to set up additional web sites to open within CAD windows, without the standard browser controls or navigation features."]
[null,"CA22","The system should support Caller Location Query, CLQ, functionality."]
[null,"CA23","System should allow for bulletin records to be linked to the master name index. "]
[null,"CA24","System should allow for bulletin records to be linked to the master vehicle index. "]
[null,"CA25","System should allow for bulletin records to be linked to the master address index. "]
[]
["Calls for Service"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CB1","The system should track reporter/complainant data, including name, address, and call-back number."]
[null,"CB2","The system should allow unlimited narrative details to be added to a CFS."]
[null,"CB3","The system should provide automatic date/time stamping and user ID tracking for all call-taker and dispatcher actions to track CFS activity, unit activity, radio log, etc."]
[null,"CB4","The system should allow authorized users to manage check-in times for units based on CFS type. When a unit exceeds the allotted time, the system should provide visible and audible warnings to the call-taker or dispatcher."]
[null,"CB5","The system should include an override/reset feature for the unit check-in time warnings."]
[null,"CB6","The system should allow for filtering subsets or sorting the active or waiting calls within the CFS control panel."]
[null,"CB7","The system should display key information about each CFS, such as incident number, call for service type, priority, status, assigned units, and incident address within the CFS control panel."]
[null,"CB8","The system should allow the information displayed for a CFS within the CFS control panel to be configured per user or per agency."]
[null,"CB9","The system should allow authorized users to manage dispatch timers based on CFS type and priority. The system should provide a visible and/or audible warning, alerting the call-taker or dispatcher that too much time has elapsed without assigning a unit(s) to the CFS."]
[null,"CB10","The system should make narrative details available to all stations in real time. "]
[null,"CB11","The system should clearly display the SOP to the call-taker and dispatcher when a CFS is created with an incident code that has an SOP. "]
[null,"CB12","The system should be able to display the active and waiting calls for service through the CFS control panel."]
[null,"CB13","The system should allow the call-taker and dispatcher to enter free-text log entries for a CFS."]
[null,"CB14","The system should auto-save narrative details after a specified period of inactivity on a CFS."]
[null,"CB15","The system should allow a CFS to be created with a single click or keystroke from either the CAD product or from the mapping product."]
[null,"CB16","The system should be able to immediately dispatch a new CFS without any mandatory fields."]
[null,"CB17","The system should allow users to create traffic stop calls for service, with fields for entering key traffic stop data, including location and license plate number, in the order specified by the agency."]
[null,"CB18","The system should allow the dispatch display to provide access to all CFS information, including incident type, nature of call, address, reporter and complainant names, and narrative."]
[null,"CB19","The system should provide duplicate CFS suggestions based on address location."]
[null,"CB20","The system should, after a dispatcher verifies a duplicated call, link the duplicate to the original call to provide access to the additional data."]
[null,"CB21","The system should allow calls for service to be manually linked for any agency-defined reason."]
[null,"CB22","The system should allow a \"use caution\" flag to be placed on any CFS.",{"$nulls":4},"Color coded Alerts in RED, YELLOW, and BLUE"]
[null,"CB23","The system should allow a CFS to be modified with priority modifiers such as Routine, Just Occurred, and In Progress throughout the life of the call. "]
[null,"CB24","The system should allow calls for service to be cleared at any time, including prior to dispatch."]
[null,"CB25","The system should allow a call-taker and/or dispatcher to specify an unlimited number dispositions or reasons for clearing a CFS."]
[null,"CB26","The system should allow authorized users to view cleared calls for service but prevent unauthorized users from making any modifications to these cleared calls."]
[null,"CB27","The system should allow reactivation of recently cleared calls for service and should also allow additional activity and dispatching of units to the original CFS."]
[null,"CB28","The system should be able to generate a sequential reference number for a CFS for each jurisdiction/responding agency. "]
[null,"CB29","The system should provide a list of all state/NCIC queries run and associated returns. This list should be filtered by date, query type, user, and/or terminal."]
[null,"CB30","The system should allow users to easily attach a state/NCIC query to a call for service so that the query and all returns are linked to the call."]
[null,"CB31","The system should allow NCIC queries to run automatically when a vehicle or name is added to a CFS."]
[null,"CB32","The system should allow all information captured within a CFS to be transferred to and available via the resulting Case report."]
[null,"CB33","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual calls for service."]
[null,"CB34","The system should allow users with access to calls for service to use the custom forms to enter and maintain the associated data."]
[]
["Incident Codes"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CC1","The system should allow authorized users to maintain a list of CFS types (incident codes), including default priority levels and default modifiers."]
[null,"CC2","The system should allow authorized users to determine if incident reports are required for given incident codes or if incident reports will be automatically created in CAD."]
[null,"CC3","The system should allow users to enter an unlimited number of incident codes for a CFS."]
[null,"CC4","The system should allow incident codes to be associated with specific N-DEx codes for state and federal reporting."]
[null,"CC5","The system should allow map icons to be assigned to each incident code for display of that incident/CFS on the map."]
[null,"CC6","The system should allow incident codes to be changed at any time during the CFS."]
[null,"CC7","The system should allow incident codes to be defined by the agency such that they will trigger the appropriate response assistance from 911 EMD systems, if so configured."]
[]
["Unit Management"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CD1","The system should allow authorized users to maintain lists of unit information such as unit alarm times, unit details, unit list filters, unit locations, unit shifts, unit specialties, unit statuses, unit types, and the units themselves."]
[null,"CD2","The system should allow authorized users to determine the length of unit alarm times and the frequency of the alarm tone."]
[null,"CD3","The system should support filtering on the CAD window to select the units which meet specified criteria (has defibrillator, etc.). "]
[null,"CD4","The system should allow unit drill-down. That is, the user should be able to select a unit and use links to locate information about the personnel, vehicle, and equipment associated with that unit and jump to those records (if authorized)."]
[null,"CD5","The system should have one or more CAD unit control windows which allow filtering and sorting units by key data."]
[null,"CD6","The system should include key information about each unit in the CAD unit control window, such as unit type, call sign, details, status, incident assignment, beat, and location, configurable per user or per agency."]
[null,"CD7","The system should allow a call-taker or dispatcher to view a list of active and waiting calls for service from the CAD control unit window and to dispatch the units to calls for service."]
[null,"CD8","The system should allow a call-taker or dispatcher to update unit information such as status, location, and details from the CAD control unit window."]
[null,"CD9","The system should allow call-takers and dispatchers to dispatch units from a displayed list of available units in the CFS control panel.",{"$nulls":4},"Units list allow dispatch 1+ units"]
[null,"CD10","The system should allow call-takers and dispatchers to issue unit commands directly from the CFS window. ",{"$nulls":4},"Command line"]
[null,"CD11","The system should support pre-built shift rosters and allow call-takers or dispatchers to place multiple units on shift with a single command.",{"$nulls":4},"Command line"]
[null,"CD12","The system should be able to re-assign a unit from one CFS to another with a single command and stack the original CFS against the re-routed unit."]
[null,"CD13","The system should provide unlimited unit stacking for calls for service."]
[null,"CD14","The system should allow a re-assigned unit to be sent back to the original CFS when the unit is cleared."]
[null,"CD15","The system should allow one unit to be exchanged with another, automatically recording in the log that the first unit was initially dispatched and then switched with the second unit."]
[null,"CD16","The system should be able to group units so that subsequent commands apply to all units in the group. ",{"$nulls":4},"Unit Option window has all the actions for the units"]
[null,"CD17","The system should support the use of cross-staffed units."]
[null,"CD18","The system should allow the call-taker or dispatcher to enter free-text messages from an officer in the CFS log."]
[null,"CD19","The system should allow the CFS log to be queried by unit to generate a record of an individual officer's activity for a given time period."]
[]
["Addresses and GIS"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CE1","The system should display a list of potential matches as characters for addresses are typed into the CFS address field. These potential matches should be reduced as additional characters are typed until only the matching address(es) is/are listed. "]
[null,"CE2","The system should allow users to suggest adding new addresses when existing address information does not exist."]
[null,"CE3","The system should allow the call-taker to select a suggested match at any time to auto-populate the address field."]
[null,"CE4","The system should, when possible, auto-populate the city, state and zip code based on the street address entered (if the address is already in the master address database)."]
[null,"CE5","The system should allow intersections to be entered as CFS addresses."]
[null,"CE6","The system should allow mile markers to be entered as CFS addresses."]
[null,"CE7","The system should allow the assignment of common address names such as \"Prospect Bank\" to actual addresses, allowing call-takers and dispatchers to enter either one in a CFS. "]
[null,"CE8","The system should allow the assignment of street name aliases. For example, \"BBR\" might be assigned as a street alias for \"Blue Bell Road\" Call-takers and dispatchers may choose to enter either the address or the alias."]
[null,"CE9","The system should automatically alert the call-taker and/or dispatcher of a possible duplicate call based on address data."]
[null,"CE10","The system should be integrated with GIS. Please describe the GIS integration.",{"$nulls":4},"Utilizing ArcGIS Pro file types "]
[null,"CE11","The system should support specifying and auto-populating the beat and/or zone for a CFS."]
[]
["Command Line"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CF1","The system should allow authorized users to maintain a list of CAD commands, including the actions which the system performs within each command."]
[null,"CF2","The system should allow call-takers and dispatchers to enter commands via the command line using a few keystrokes."]
[null,"CF3","The system should allow authorized users to create agency-specific commands for the command line."]
[null,"CF4","The system should allow the command line to use natural language rather than cryptic key codes or a specific information order."]
[null,"CF5","The system should use business logic to dynamically display only the necessary fields for the selected command in the command line."]
[null,"CF6","The system should allow authorized users to arrange traffic stop fields in a CAD command to match the order they are called out to dispatchers at the agency."]
[null,"CF7","The system should default the CFS number from the current CFS to the command line embedded in the CFS detail screen.",{"$nulls":4},"All actions use the default CAD#"]
[null,"CF8","The system should support multiple instances of the command line on multiple displays from the same workstation."]
[null,"CF9","The system should allow users to post brief messages directly to Twitter from the command line based on templates containing pre-defined call elements."]
[null,"CF10","The system should allow users to run common state/NCIC queries directly from the command line."]
[]
["Call-taker/Dispatcher"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CG1","The system should allow authorized users to take over any call-taker or dispatcher position."]
[null,"CG2","The system should be able to be set up for a call-taker and/or dispatcher workflow, or for one user to fill both roles using the same windows. "]
[null,"CG3","The system should support either local or remote call-taker and/or dispatcher positions."]
[null,"CG4","The system should support an unlimited number of call-taker and/or dispatcher positions."]
[null,"CG5","The system should allow multiple call-takers or dispatchers or mobile users to enter data on the same CFS simultaneously."]
[null,"CG6","The system should allow for units to be dispatched simultaneously with call-taking activities."]
[null,"CG7","The system should make information immediately available to all stations as soon as any dispatcher, call-taker, or mobile unit updates a call. A CFS update indicator (for example, flashing text) should be visible to all stations."]
[null,"CG8","The system should make all functions available from the call-taker and dispatcher positions for officer-initiated incidents (quick calls) and traffic stops."]
[]
["Relationships"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CH1","The system should allow users to add unlimited involved persons to a CFS."]
[null,"CH2","The system should allow authorized users to set up an unlimited number of custom, configurable relationship types."]
[null,"CH3","The system should allow authorized users to extend the list of CFS relationship types to include such types as arrestee, cited, reporter, driver of vehicle, and passenger."]
[null,"CH4","The system should automatically check all involved persons’ names against the master name index. "]
[null,"CH5","The system should allow for the entry of anonymous reporters such as concerned citizen or anonymous female without creating a master name record for these entries."]
[null,"CH6","The system should automatically transfer all names, including any involved persons, from the CFS record to any associated case reports. "]
[]
["Service Vehicles"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CI1","The system should include a list of service vehicle providers that need to maintain a rotation schedule, such as wreckers or private ambulances."]
[null,"CI2","The system should automatically position the second company in the first position after the first company has been selected."]
[null,"CI3","The system should allow the user to dispatch the next company, when unable to reach the first company in line, without manually moving the first company to the bottom of the rotation sequence."]
[null,"CI4","The system should allow the user to override the rotation in the event a specific provider is requested."]
[null,"CI5","The system should track attempts to contact service vehicle providers and the results of each attempt."]
[]
["Tow Calls"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CJ1","The system should allow authorized users to maintain lists of tow call information such as tow call statuses, tow operators, and tow operator schedules."]
[null,"CJ2","The system should provide a means for recording when a vehicle needs to be towed, including vehicle identifying data, vehicle location, comments, and attempts to contact service vehicles."]
[null,"CJ3","The system should allow vehicle data from a call for service to automatically populate the tow call.",{"$nulls":4},"Officer Initiated call form"]
[null,"CJ4","The system should ensure that tow calls are recorded as links for the related master vehicle records."]
[null,"CJ5","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual tow calls."]
[null,"CJ6","The system should allow users with access to tow calls to use the custom forms to enter and maintain the associated data."]
[]
["Unit Recommendations"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CK1","The system should allow authorized users to maintain a list of run cards."]
[null,"CK2","The system should allow agency-configurable run cards to define the required responders for each incident code."]
[null,"CK3","The system should allow authorized users to define run cards by particular map layer(s) or by individual addresses.",{"$nulls":4},"by individual address"]
[null,"CK4","The system should allow run cards to be applied to a single incident code or to multiple incident codes."]
[null,"CK5","The system should allow run cards to be based on/include the following additional criteria: day, time of day, number and type of units."]
[null,"CK6","The system should allow units which match up with run card criteria to be differentiated with a tiebreaker (such as which one has been inactive for the longest period)."]
[null,"CK7","The system should prioritize units for recommendation based on factors including the following:\n -  Department/jurisdiction\n -  Specialties, training skills, and equipment\n -  Closest path/shortest routing time to   incident location\n -  Time since last CFS assignment\n - Unit status"]
[null,"CK8","The system should allow the dispatcher to assign a recommended unit, assign all recommended units, or expand the list of units to view more recommendations."]
[null,"CK9","The system should support the use of cascading unit recommendations."]
[]
["Vehicles"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CL1","The system should store all vehicle information which is added to a CFS entry in the master vehicle index."]
[null,"CL2","The system should allow multiple vehicles to be added to a CFS. "]
[null,"CL3","The system should include the following vehicle relationship types: traffic stops or traffic accidents, towed vehicles, abandoned vehicles, and unlimited agency-defined relationships types. "]
[null,"CL4","The system should automatically transfer vehicle information from a CFS to any associated case reports. "]
[]
["Hazards and Alerts"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CM1","The system should visibly notify call-takers, dispatchers and officers of any alert information for names, addresses, and vehicles involved in a CFS. "]
[null,"CM2","The system should integrate hazards and alerts between all products so that alerts entered in one area are available in all others (for example, a dispatcher is alerted in CAD that a complainant has an outstanding warrant in RMS)."]
[null,"CM3","The system should allow unlimited narrative text for an alert."]
[null,"CM4","The system should include both urgent and non-urgent alerts."]
[null,"CM5","The system should allow alerts to be deactivated, if no longer relevant, but still maintained in the alert history."]
[null,"CM6","The system should allow users to set an expiration date for each alert. Expired alerts should be retained but clearly marked as expired and non-urgent."]
[null,"CM7","The system should display alerts triggered from any non-CAD area of the system to dispatchers in real-time based on the people involved, addresses, vehicles, etc. For example, any alerts for warrant hits or sex offender status should display when a reporting party name is entered in CAD."]
[null,"CM8","The system should allow authorized users to create other name alert types, such as medical alerts, protection orders, etc."]
[null,"CM9","The system should directly link alerts (such as warrant hits) to the triggering information."]
[null,"CM10","The system should alert the call-taker and dispatcher and/or officer if hazardous material is stored at a site, including material name, amount, location on site, and cutoff information (if the data is available on the master address record). "]
[null,"CM11","The system should link hazardous material alerts to the relevant text from the Hazmat Guide stored in the system."]
[null,"CM12","The system should alert the call-taker and dispatcher and/or officer to protection system details for an address, such as fire alarm panel locations and sprinkler system details (if the data is available on the master address record)."]
[null,"CM13","The system should be able to alert the call-taker and dispatcher and/or officer to water supply details for an address (if the data is available on the master address record)."]
[null,"CM14","The system should alert the call-taker and dispatcher and/or officer to any officer safety warnings for an address such as unlocked firearms, and vicious dogs (if the data is available on the master address record)."]
[null,"CM15","The system should allow authorized users to create other address alerts such as known crash pads, drug sites, etc."]
[null,"CM16","The system should allow authorized user to create agency-defined vehicle warnings."]
[null,"CM17","The system should alert the call-taker and dispatcher and/or officer to any vehicle warnings. "]
[null,"CM18","The system should allow name, address, and vehicle alerts to be created during the call-taking and/or dispatch process."]
[null,"CM19","The system should provide a means of granting or denying users permission to view or create specific name, address, and vehicle alert types so that these alerts can be used to store data such as confidential investigative information."]
[]
["Call Scheduling"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CN1","The system should allow scheduling calls for future dispatch to help manage special events such as parades, festivals, funeral escorts, and prisoner transport.",{"$nulls":4},"Call is created, then scheduled. Sits in Pend/Sched tab until active."]
[null,"CN2","The system should automatically create a CFS when the scheduled activity occurs."]
[null,"CN3","The system should allow scheduled calls to be set up to notify call-takers and dispatchers in advance of the actual event."]
[null,"CN4","The system should allow a user, when scheduling a CFS, to specify which terminal will handle the CFS."]
[null,"CN5","The system should remind a user who schedules a CFS to check the CFS date when calls are scheduled for dates that are not in the near future."]
[null,"CN6","The system should allow scheduled calls to include unlimited narrative details."]
[null,"CN7","The system should support location overrides for scheduled calls."]
[null,"CN8","The system should be able to display a list of scheduled calls, either future or past."]
[null,"CN9","The system should allow a CFS to be scheduled to recur according to a number of different times (for example, daily, the first Friday of the month, every other month, etc.)"]
[]
["External Messaging"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CO1","The system should include the ability to send messages externally via smtp and sms."]
[null,"CO2","The system should support rip and run messaging via email or fax for communication with external agencies."]
[null,"CO3","The system should allow authorized users to maintain lists of paging groups and paging message types."]
[null,"CO4","The system should send automatic pages based on incident types."]
[null,"CO5","The system should be able to notify users or groups via smtp or sms when specified calls for service are received."]
[]
["Internal Messaging"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CP1","The system should allow instant messages to be sent to multiple recipients, such as via a public message room accessible by all on-duty call-takers, dispatchers and officers."]
[null,"CP2","The system should allow instant messages to be sent to specified user(s)."]
[null,"CP3","The system should provide visible and/or audible alerts or to bring the alert to the front of all other open windows when the user receives an instant message."]
[null,"CP4","The system should allow for the inclusion of a number of different tones to designate different types of audible alerts."]
[null,"CP5","The system should include an e-mail function that is internal to the system, allowing users to send e-mail-style messages to other users on the system."]
[null,"CP6","The system should allow e-mail-style messages to include links to records within the system."]
[null,"CP7","The system should allow a single e-mail-style message to be sent to one or more users."]
[null,"CP8","The system should allow users to store or delete received e-mail-style messages."]
[null,"CP9","The system should log all sent e-mail-style messages."]
[null,"CP10","The system should provide a note pad function that allows call-takers and dispatchers to type in unlimited text and store the text within the system."]
[null,"CP11","The system should stamp note pad entries with the date and time and user who created them."]
[null,"CP12","The system should allow note pad entries to be set to automatically expire."]
[null,"CP13","The system should be able to notify users or user groups via internal system messaging, or e-mail when specified calls for service are received."]
[null,"CP14","The system should allow for call-takers and/or dispatchers to notify users and/or user groups of a CFS during any point of the call-taking or dispatching process."]
[null,"CP15","The system should allow bulletins such as BOLOs and special instructions to be issued to groups of officers based on type, jurisdiction, beat, etc."]
[null,"CP16","The system should immediately make BOLOs available to the system’s mobile units."]
[null,"CP17","The system should allow BOLOs to have files attached to them via upload or scanner."]
[]
["Alarm Billing"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CQ1","The system should allow an alarm billing record to be created from an incident code with a false alarm disposition when the CFS is completed."]
[null,"CQ2","The system should integrate the alarm billing with the financial product provided by the same vendor."]
[null,"CQ3","The system should be able to automatically create invoices to bill persons or businesses for false alarms."]
[null,"CQ4","The system should allow users to manually select charges for alarm billing."]
[null,"CQ5","The system should allow users to save, print or email an alarm billing record directly from the record window."]
[null,"CQ6","The system should allow users to sort and filter alarm billing records within the list-view window."]
[null,"CQ7","The system should allow users to save, print or email a summary list of alarm billing records from the list-view window."]
[null,"CQ8","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with alarm billing records."]
[null,"CQ9","The system should allow users with access to alarm billing records to use the custom forms to enter and maintain the associated data."]
[]
["CAD Reporting"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CR1","The system should provide a report generator for building custom statistical and analytical reports from CAD data. The report generator should be provided by the same vendor and should not be a third-party application."]
[null,"CR2","The system should restrict access to the report generator and individual report templates by user or user group."]
[null,"CR3","The system should not allow a user who does not have access to particular data via the application user interface to gain access to that data via the report generator."]
[null,"CR4","The system should allow the creator of the report template to build reports for any data entered into the CAD product."]
[null,"CR5","The report generator should allow the creator of the report template to control layout and formatting options for each CAD report template. This includes such options as field arrangements, column widths, label text, font sizes, and line spacing."]
[null,"CR6","The report generator should allow the creator of each CAD report template to choose which users can access and/or run the report and/or modify the report template."]
[null,"CR7","The report generator should support the use of aggregate (math) functions including Sum, Average, Count, Count Blank, Minimum, and Maximum."]
[null,"CR8","The report generator should allow data to be grouped or sorted by any data element."]
[null,"CR9","The report generator should allow multiple data filters to be applied using \"and/or\" logic."]
[null,"CR10","The report generator should allow CAD reports to be saved (as PDF, .XLS, or .CSV), printed, or emailed directly from the report."]
[null,"CR11","The report generator should allow CAD report templates to be saved and modified at a later time."]
[null,"CR12","The report generator should support adding the CAD reports to user's dashboards."]
[null,"CR13","The report generator should allow recurring CAD reports to be scheduled and automatically uploaded to a file-system or e-mailed to specified users on certain days and times."]
[null,"CR14","The report generator should support ad-hoc queries."]
[null,"CR15","The report generator should support creation of CAD reports such as the following:\n -  Area/section activity\n -  CFS priority analysis\n -  Daily or shift-based CFS summary\n -  CFS by month, by day of week, by hour of day\n -  CFS by nature of call\n -  CFS by source, by disposition\n -  CFS by station, by call-taker or dispatcher\n -  Response time analysis by area, section, priority\n -  Summary of activity for an address or business name\n -  Unit assignments "]
[]
["ANI/ALI Interface"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CS1","The system should include an interface to the 911 service provider."]
[null,"CS2","The system should receive the raw spill data from the 911 service and import it into the CFS via a serial or IP connection."]
[null,"CS3","The system should intelligently handle ANI/ALI rebids through the interface."]
[null,"CS4","The system should allow E911 calls, upon being answered, to automatically generate and populate the CFS entry window with all known data (for example, address, registered name, and phone number) from the call-in number."]
[]
["Rip and Run Interface"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"CT1","The system should include an interface to fax and email services."]
[null,"CT2","The system should allow CFS information to be transmitted via this interface to third-parties (such as fire departments)."]
[null,"CT3","The system should allow authorized users to manage the settings for this interface (SMTP configurations, etc.)"]
[]
["Interface A"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[]
[]
[]
["Interface B"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]

{"sheet":"Financial","index":3,"n_rows":87,"n_cols":8,"rows_kept":87,"cut":false,"hidden":false,"merged":[]}
["Financial"]
[]
["General"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"FA1","The system should include a fully integrated financial product provided by the same vendor, and not a third-party application."]
[null,"FA2","The system should support any number of different funds with separate ledger accounts and preconfigured fees (invoice items)."]
[null,"FA3","The system should allow authorized users to set user and user group permissions separately for each fund."]
[null,"FA4","The system should support either cash or accrual basis accounting."]
[null,"FA5","The system should support an unlimited number of general ledger accounts."]
[null,"FA6","The system should support general ledger accounts of the following types: Income, Expense, Asset, Liability and Equity."]
[null,"FA7","The system should support the creation of account groups."]
[null,"FA8","The system should assign account reference numbers to each account."]
[null,"FA9","The system should allow authorized users to deactivate general ledger accounts."]
[null,"FA10","The system should allow authorized users to define fiscal years with any start month."]
[null,"FA11","The system should allow authorized users to close fiscal periods"]
[null,"FA12","The system should prevent the creation of any new source documents in closed fiscal periods."]
[null,"FA13","The system should prevent changes to any source documents dated in closed fiscal periods."]
[]
["Source Documents"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"FB1","The system should allow source documents (Invoices, Receipts, Deposits, Checks, Bank Deposits, Disbursements and Bills) to write to the general ledger upon save."]
[null,"FB2","The system should make the general ledger transactions made by each source document viewable directly from that source document."]
[null,"FB3","The system should allow source documents to be configured for manual rather than automatic posting."]
[null,"FB4","The system should ensure that authorized users are the only ones who may generate manual general ledger entries for saved source documents."]
[null,"FB5","The system should allow authorized users to define default amounts for preconfigured fees (invoice items)."]
[null,"FB6","The system should allow collected fees to be disbursed in accordance with a predefined schedule."]
[null,"FB7","The system should allow scheduled disbursements to be based on a fixed disbursement amount, a percentage of the collected amount, or the remainder of the fee amounts collected."]
[null,"FB8","The system should support the creation of invoices with multiple preconfigured fees, adjustable amounts and descriptions."]
[null,"FB9","The system should allow invoices to be set up with a due date based on a default time period."]
[null,"FB10","The system should allow authorized users to override the default due date on invoices as needed."]
[null,"FB11","The system should print mailable invoices from the system for the customer, including both a configurable payment remittance address and a corresponding text area."]
[null,"FB12","The system should allow multiple payments to be made on a single invoice."]
[null,"FB13","The system should allow remaining invoice balances to be designated as uncollectable and placed into an uncollectable expense account in the general ledger."]
[null,"FB14","The system should link invoices to other records such as Inmates, Warrants, Pistol Permits, Tow Calls, Bicycle Registrations, Alarms, and Protections Orders."]
[null,"FB15","The system should allow source documents to have files attached to them via upload or scanner."]
[null,"FB16","The system should allow individual user permissions to be set for viewing, editing and removing each type of source document."]
[]
["Receipt Payments"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"FC1","The system should include both paid for and paid to parties on receipt payments."]
[null,"FC2","The system should allow receipt payments to track the type of payment and the check or payment reference number."]
[null,"FC3","The system should allow receipt payments made on invoices to include the automatic calculation of payment amounts by a predefined payment priority schedule set by each fee."]
[null,"FC4","The system should allow a single receipt payment to be applied against multiple open invoices."]
[null,"FC5","The system should allow a single receipt payment to specify the exact amount applied to each fee across multiple open invoices."]
[null,"FC6","The system should allow a fixed or percentage based fee to be added to receipt payments, based on the type of payment (for example, 3% for a credit card payment)."]
[]
["Accounts"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"FD1","The system should allow deposits to be tracked by customer."]
[null,"FD2","The system should allow deposits to be used for payments on future receipts or refunded to the customer."]
[null,"FD3","The system should support bank deposits to track the receipt payment funds collected and deposited into a bank account."]
[null,"FD4","The system should support bank reconciliation records to validate each bank account balance against deposited funds and payments made from accounts."]
[null,"FD5","The system should display a chart of accounts with current balances."]
[]
["Payables"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"FE1","The system should track payables by bills to be paid, allowing multiple expense accounts to be added for each vendor payable."]
[null,"FE2","The system should allow multiple payment checks to be entered to satisfy a single payable."]
[null,"FE3","The system should record payment to external parties by specifying payment money type and expense accounts per payment."]
[null,"FE4","The system should support check printing on pre-printed stock as well as full check printing with account information on MICRS printers."]
[]
["Financial Reporting"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"FF1","The system should provide a report generator for building custom statistical and analytical reports from financial data. The report generator should be provided by the same vendor and not be a third-party application."]
[null,"FF2","The system should restrict access to the report generator and individual report templates by user or user group."]
[null,"FF3","The system should not allow a user who does not have access to particular data via the application user interface to gain access to that data via the report generator."]
[null,"FF4","The system should allow the creator of the report template to build reports for any data entered into the financial product."]
[null,"FF5","The report generator should allow the creator of the report template to control layout and formatting options for each administration report template. This includes such options as field arrangements, column widths, label text, font sizes, and line spacing."]
[null,"FF6","The report generator should allow the creator of each financial report template to choose which users can access and/or run the report and/or modify the report template."]
[null,"FF7","The report generator should support the use of aggregate (math) functions including Sum, Average, Count, Count Blank, Minimum, and Maximum."]
[null,"FF8","The report generator should allow data to be grouped or sorted by any data element."]
[null,"FF9","The report generator should allow multiple data filters to be applied using \"and/or\" logic."]
[null,"FF10","The report generator should allow financial reports to be saved (as PDF, .XLS, or .CSV), printed, or emailed directly from the report."]
[null,"FF11","The report generator should allow financial report templates to be saved and modified at a later time."]
[null,"FF12","The report generator should support adding the financial reports to user's dashboards."]
[null,"FF13","The report generator should allow recurring financial reports to be scheduled and automatically uploaded to a file-system or e-mailed to specified users on certain days and times."]
[null,"FF14","The report generator should support ad-hoc queries."]
[null,"FF15","The system should include the following pre-defined financial reports:\n -  Balance sheet\n -  Income statement\n -  Trial balance\n -  Disbursement\n -  Receipt income\n -  Accounts payable aging\n -  Accounts receivable aging\n - Customers by balances, receipts, checks, or unapplied funds \n - Customer statements\n - Vendors by payables, checks, or disbursements "]
[null,"FF16","The report generator should allow authorized users to create any number of additional reports from the financial data stored in the system."]
[]
["Interface A"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[]
[]
[]
["Interface B"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]

{"sheet":"Jail","index":4,"n_rows":322,"n_cols":8,"rows_kept":322,"cut":false,"hidden":false,"merged":[]}
["Jail Management System (JMS)"]
[]
["General"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JA1","The system should include a list of current inmates with key identifying data such as inmate numbers and cell assignments."]
[null,"JA2","The system should visibly notify users when multiple inmates are in custody with the same first and last names."]
[null,"JA3","The system should provide a main JMS window that displays such information such as inmates in queue for booking, upcoming court appearances and releases, a list of inmates who are out on work release, and scheduled contacts and activities. This window should be configurable."]
[null,"JA4","The system should allow authorized users to locate any inmate at any time."]
[null,"JA5","The system should be capable of creating an audit trail for every inmate's movements. This trail should list the inmate, where s/he was originally, where s/he is going (new location) who initiated movement (officer), who is receiving the inmate, and the date and time of the movement."]
[null,"JA6","The system should allow authorized users to maintain a list of reasons for sealing inmate records."]
[null,"JA7","The system should allow authorized users to seal inmate records."]
[null,"JA8","The system should allow authorized users to restrict user or user-group access to sealed inmate records, per record."]
[null,"JA9","The system should allow authorized users to expunge (remove) an inmate record."]
[null,"JA10","The system should generate the following output forms, at a minimum:\n -  Bond forms\n -  Application for good time\n -  Probable cause forms\n -  Record of time served\n -  Release extradition waivers\n -  Release of posted bond forms\n -  Room and board notices\n -  Transfer of custody forms\n -  Trip background reports\n -  Wanted posters"]
[null,"JA11","The system should ensure that forms capture, store, and print with electronic signatures."]
[]
["Facilities"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JB1","The system should allow authorized users to maintain lists of multiple jail facilities and the cells in each facility. "]
[null,"JB2","The system should track data for inmates held in multiple facilities. "]
[null,"JB3","The system should allow authorized users to configure cell blocks, pods, houses, etc., as well as the beds within each."]
[null,"JB4","The system should allow authorized users to configure locations which are not cells, such as kitchens, hallways, rec rooms, etc."]
[null,"JB5","The system should allow authorized users to restrict users' access to specific cell blocks, pods, houses, etc."]
[null,"JB6","The system should allow a different classification form to be defaulted for each facility."]
[]
["Intake"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JC1","The system should provide a guided step-by-step process (aka \"wizard\") for performing the intake for an individual."]
[null,"JC2","The system should allow a user to continue the booking process from someone who has been through the intake process without re-entry of any previously entered data."]
[null,"JC3","The system should allow an inmate to go through intake from a case, a warrant or nothing."]
[null,"JC4","The system should allow an inmate without a name to go through intake."]
[null,"JC5","The system should allow a user to not book an individual after the individual has gone through the intake process."]
[]
["Booking"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JD1","The system should provide a guided step-by-step process (aka \"wizard\") for booking an inmate to ensure that all necessary steps are completed."]
[null,"JD2","The system should allow authorized users to configure the booking wizard to conform to the agency's needs. Configuration should include defining which form (property form, approved visitors form, medical screening form, etc.) is next in the sequence as well as which forms are required and which are not."]
[null,"JD3","The system should include a means for recording inmate property as part of the booking process.  "]
[null,"JD4","The system should include a means of issuing agency property to an inmate as part of the booking process."]
[null,"JD5","The system should allow the booking process to be suspended at any time without losing data, and resumed at a later time from that same point by any authorized user.  "]
[null,"JD6","The system should display a visible indicator on the booking list that shows which inmate booking processes were suspended and which ones were completed."]
[null,"JD7","The system should display alerts triggered from any non-JMS area of the system when booking an inmate, including outstanding warrants, sex offender status, medical alerts, and potential threats to officer safety."]
[null,"JD8","The system should allow authorized users to manage a medical/mental screening questionnaire which is used as part of the booking process."]
[null,"JD9","The system should provide all information from a person's master name record during the booking process, including prior relationships, previous bookings, sex offender status, and any other alerts on the master name."]
[null,"JD10","The system should carry over basic inmate information from a prior booking into a new booking without requiring re-entry."]
[null,"JD11","The system should allow users to select an inmate from the inmate list for rebooking."]
[null,"JD12","The system should include an intake function that does not require the full booking process."]
[null,"JD13","The system should allow users to place person in a queue for full booking, after completing the intake function."]
[null,"JD14","The system should handle multiple sentences, both concurrent and consecutive, and perform sentence calculation, including reductions such as good time."]
[null,"JD15","The system should track charge data such as offenses, bonds, and bond amounts."]
[null,"JD16","The system should allow users to enter an inmate's victims during the booking process to support their notification upon the inmate's release.",{"$nulls":4},"Appriss VINE Interfacing"]
[null,"JD17","The system should allow multiple mugshots per inmate."]
[null,"JD18","The system should allow for tagging pictures as scars, marks, and tattoos, as well as recording the location of those items on the body."]
[null,"JD19","The system should be able to generate a booking summary form."]
[null,"JD20","The system should include agency-customizable forms with the ability to trigger other requested information based on data entered, such as: alerts, classifications, medical condition, no contacts, etc. "]
[]
["Transports"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JE1","The system should allow inmate transports to be tracked."]
[null,"JE2","The system should allow authorized users to maintain a list of transportation types."]
[null,"JE3","The system should allow authorized users to maintain a list of transportation vehicles, including the number of seats for each vehicle."]
[null,"JE4","The system should ensure that all no-contact rules are followed for transports."]
[null,"JE5","The system should capture that all passengers and drivers explicitly listed for a given transport."]
[null,"JE6","The system should allow transportation rates to be defined on a time or distance basis."]
[null,"JE7","The system should allow for a variety of costs to be tracked for a given transport, including personnel, mileage, meals, and lodging."]
[null,"JE8","The system should allow transport costs for a given transport to be shared between two agencies."]
[null,"JE9","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with transport records."]
[null,"JE10","The system should allow users with access to transport records to use the custom forms to enter and maintain the associated data."]
[null,"JE11","The system should allow transport records to have files attached to them via upload or scanner."]
[]
["Bonds"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JF1","The system should allow authorized users to maintain a list of approved bond companies."]
[null,"JF2","The system should allow authorized users to maintain a list of bond agents."]
[null,"JF3","The system should be able to track filing dates, agent license expiration dates, and maximum bond amounts for bond agents/companies."]
[null,"JF4","The system should allow each bond company to be set up to use multiple insurance companies."]
[null,"JF5","The system should be able to track bond payments including amount, money type, and the name of the bond agent.",{"$nulls":4},"No bond agent"]
[]
["Digital Lineups"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JG1","The system should allow authorized users to create digital lineups using mugshots stored in the system."]
[null,"JG2","The system should allow users to choose demographic criteria to select mug shots for inclusion in digital lineups, including eye color, hair color, height, and weight."]
[null,"JG3","The system should support exporting digital lineups to a ZIP file."]
[null,"JG4","The system should allow users to randomly select photos for a digital lineup. "]
[]
["Classes"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JH1","The system should allow authorized users to maintain a list of classes for inmates."]
[null,"JH2","The system should allow court-mandated class registrations to be included in the booking wizard."]
[null,"JH3","The system should allow classes to be defined as billable or non-billable."]
[null,"JH4","The system should allow inmates to be included in waiting lists for classes."]
[null,"JH5","The system should ensure that all no-contact rules are followed for classes."]
[null,"JH6","The system should allow class records to have files attached to them via upload or scanner."]
[null,"JH7","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual class records."]
[null,"JH8","The system should allow users with access to class records to use the custom forms to enter and maintain the associated data."]
[]
["Classifications"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JI1","The system should include an agency-defined form in the booking process to classify inmates for cell assignment."]
[null,"JI2","The system should assign point-based classification levels to inmates from data entered on the agency-defined classification form. "]
[null,"JI3","The system should be able to subtract classification points for stabilizing or mitigating factors. "]
[null,"JI4","The system should allow authorized users to manually override system-calculated inmate classification levels. "]
[null,"JI5","The system should provide cell recommendations from classification levels. "]
[null,"JI6","The system should ensure that classification takes into account data entered into specific booking wizard questionnaires that match tags on specific cells, such as \"handicapped accessible\" or \"juvenile holding.\""]
[null,"JI7","The system should allow users to configure automatic reclassification schedules based upon initial inmate classification type."]
[null,"JI8","The system should allow multiple forms to be created for classifications. "]
[]
["Holds"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JJ1","The system should include the appropriate data entry forms in the booking process based on the selected hold reason(s)."]
[null,"JJ2","The system should allow authorized users to maintain a list of hold reasons, including which fields are displayed for each hold reason. Hold reasons should include charged, sentenced, warrant, additional hold, and unlimited agency-defined reasons."]
[null,"JJ3","The system should allow users to enter multiple hold reasons per inmate, and should adjust the forms to show only the fields needed for the selected reason(s)."]
[null,"JJ4","The system should allow hold reason records to have files such as documents or scanned documents attached to them as part of the booking process.",{"$nulls":4},"Attachment of images, documents, or scans."]
[null,"JJ5","The system should allow for the sealing of hold reasons, bookings, and incident reports. "]
[null,"JJ6","The system should allow for the expungement of charges."]
[null,"JJ7","Agency-defined custom fields should be available in Holds."]
[]
["Stay Scheduling"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JK1","The system should allow for scheduling inmate stay segments.",null,null,null," "]
[null,"JK2","The system should allow authorized users to set up stay schedules for inmates serving segmented (\"weekender\") sentences.",null,null,null," "]
[null,"JK3","The system should allow scheduled segments to put time toward total sentence length, optionally including or excluding days checked out of the facility.",null,null,null," "]
[null,"JK4","The system should allow inmates to be checked in and out of the facility with no need to release and re-book."]
[null,"JK5","The system should allow for configuration of different stay schedule types."]
[]
["Release"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JL1","The system should display upcoming user releases on the user's dashboard."]
[null,"JL2","The system should provide a guided step-by-step process (aka \"wizard\") for releasing an inmate to ensure that all necessary steps are completed."]
[null,"JL3","The system should allow authorized users to configure the release wizard to conform to the agency's needs."]
[null,"JL4","The system should provide a warning to a user who attempts to release an inmate before the sentence has been completely served."]
[null,"JL5","The system should allow users to enter multiple release reasons per inmate, and should adjust the forms to show only the fields needed for the selected reason(s)."]
[null,"JL6","The system should capture the following as part of the release wizard, at minimum:\n -  Record of time served\n -  Release and custody form\n -  Bond form\n -  Release posted bond form"]
[null,"JL7","The system should allow release reasons to be recorded for each of an inmate’s hold reasons. Individual hold reasons should be resolved prior to overall inmate release."]
[null,"JL8","The system should alert users when an inmate to be released has additional holds in the system."]
[null,"JL9","The system should release remaining inmate funds as part of the release process."]
[null,"JL10","The system should be able to release inmate funds to the inmate or another person, or hold the funds until a later date for pickup by a specified person."]
[null,"JL11","The system should be able to generate a check for the release of inmate funds. "]
[null,"JL12","The system should include release of inmate property in the inmate release process."]
[null,"JL13","The system should be able to release inmate property to the inmate or to another person, or hold it until a later date for pickup by a specified person."]
[null,"JL14","The system should generate inmate fund and inmate property release forms that can be signed (manually or electronically) to verify receipt of funds and property."]
[null,"JL15","The system should clearly display a \"Released” status on an inmate’s record once that inmate has been released."]
[null,"JL16","The system should be able to print a release summary."]
[null,"JL17","The system should allow authorized users to maintain a list of release reasons, including which fields are displayed for each release reason. Release reasons should include bonded out, furlough, judge ordered, sentence served, transferred, and unlimited agency-defined reasons."]
[null,"JL18","The system should allow authorized users to undo a release that was performed in error."]
[]
["Housing"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JM1","The system should track an inmate’s original cell assignment and all subsequent cell transfers."]
[null,"JM2","The system should allow authorized users to override inmate cell recommendation assignments."]
[null,"JM3","The system should be able to generate a report of current cell assignments ordered by cell block."]
[null,"JM4","The system should be able to generate a report of inmates housed in a selected cell or cell block during a specified time period."]
[null,"JM5","The system should include an integrated financial product (not a third-party application) to track inmate billing for room and board, medical expenses, and other fees."]
[null,"JM6","The system should allow authorized users to set up billing rates for inmate housing."]
[null,"JM7","The system should allow authorized users to set up different billing rates for each agency or entity for which inmates are housed. "]
[null,"JM8","The system should support automatic billing for room and board fees."]
[null,"JM9","The system should be able to generate invoices for inmate housing, including summary invoices for outside agencies."]
[]
["Activities"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JN1","The system should allow authorized users to maintain a list of common activity types, locations, and default locations for each activity type."]
[null,"JN2","The system should allow authorized users to configure common activity types to track times including \"in and out\" and \"log in and log out\" times."]
[null,"JN3","The system should track inmate activities such as cell checks, meals, recreation, group meetings, medical appointments, trustee work and work releases."]
[null,"JN4","The system should allow activities to be recorded as they occur or scheduled in advance."]
[null,"JN5","The system should provide reminders for scheduled inmate activities."]
[null,"JN6","The system should provide a warning to prevent inmates from logging into activities at the same time and location as another person for whom they have a \"no contact\" order."]
[null,"JN7","The system should be able to capture an inmate’s acceptance or refusal of an activity."]
[null,"JN8","The system should include a comment field for each activity record."]
[null,"JN9","The system should allow users to add inmate activities in bulk."]
[null,"JN10","The system should provide log of inmate activities, both for all inmates and for an individual inmate."]
[null,"JN11","Agency-defined custom fields should be available in Activities."]
[null,"JN12","The system should flag when a user tries to schedule conflicting activities. "]
[null,"JN13","The system should track work hours for trustee inmates."]
[null,"JN14","The system should configure the rate at which trustee inmates earn time off. "]
[]
["Visitors/Contacts"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JO1","The system should allow authorized users to maintain a list of visitation notification attempt types including phone, in person, mail, and email."]
[null,"JO2","The system should allow users to capture inmate contacts, including person contacted, contact type (phone, visit, etc.), and relationship."]
[null,"JO3","The system should allow visitors to be defined as approved or unapproved. "]
[null,"JO4","The system should show if a visitor is an approved or unapproved visitor for another inmate."]
[null,"JO5","The system should be able to bring approved and unapproved visitors forward from previous bookings. "]
[null,"JO6","The system should automatically check all visitors for alerts such as warrants, safety threats, etc."]
[null,"JO7","The system should allow users to perform state/NCIC checks on visitors. "]
[null,"JO8","The system should alert users to an inmate's upcoming visits."]
[null,"JO9","The system should allow users to log incoming mail and packages, including the sender’s name."]
[null,"JO10","The system should log visit notification attempts with the date and time."]
[null,"JO11","The system should allow the logging of multiple visitors at once."]
[]
["Work Release"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JP1","The system should track work release hours, include check-in and check-out times, employers, and PBT and search results upon check-in."]
[null,"JP2","The system should flag inmates who are eligible for work release."]
[null,"JP3","The system should provide a list of inmates who are out on work release."]
[]
["Jail Incidents"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JQ1","The system should allow authorized users to maintain a list of incident types."]
[null,"JQ2","The system should track incident reports. "]
[null,"JQ3","The system should track the outcomes of incident reports."]
[null,"JQ4","The system should provide a searchable incident log."]
[null,"JQ5","The system should include an approval process for incident reports."]
[null,"JQ6","The system should allow users to link an incident report to a case. "]
[null,"JQ7","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual incident report records."]
[null,"JQ8","The system should allow users with access to incident report records to use the custom forms to enter and maintain the associated data."]
[null,"JQ9","The system should allow authorized users to seal jail incident reports."]
[null,"JQ10","Agency-defined custom fields should be available in Jail Incidents."]
[]
["Disciplinary Actions"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JR1","The system should allow authorized users to maintain a list of inmate disciplinary offenses, including a severity level."]
[null,"JR2","The system should track disciplinary actions for inmates."]
[null,"JR3","The system should allow disciplinary actions to be linked to cases or incidents."]
[null,"JR4","The system should include an approval process for disciplinary actions."]
[null,"JR5","The system should allow users to include hearing and disposition information within the disciplinary action record."]
[null,"JR6","The system should allow disciplinary action records to have files attached to them via upload or scanner."]
[null,"JR7","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual disciplinary action records."]
[null,"JR8","The system should allow users with access to disciplinary action records to use the custom forms to enter and maintain the associated data."]
[null,"JR9","Agency-defined custom fields should be available in Disciplinary Actions."]
[]
["Event/Shift Logs"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JS1","The system should allow authorized users to maintain a list of common shift event types such as staff movement and meal passes."]
[null,"JS2","The system should provide an event or shift log to record shift activity."]
[null,"JS3","The system should support setting up a separate event or shift log for each cell block, or all cell blocks together."]
[null,"JS4","The system should capture shift start and end times and correctional staff on duty for each shift."]
[null,"JS5","The system should allow authorized users to log in or log out the entire shift roster of correctional staff at one time."]
[null,"JS6","The system should allow an unlimited narrative within an event record."]
[null,"JS7","The system should include a date, time, and username on every event record."]
[null,"JS8","The system should make a shift summary available to the next shift."]
[null,"JS9","Agency-defined custom fields should be available in Event/Shift Logs."]
[]
["Medical"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JT1","The system should be able to track medical appointments."]
[null,"JT2","The system should track medical/mental health expenses and should be able to create invoices to bill other agencies for these expenses."]
[null,"JT3","The system should allow the medical/mental health screening questionnaire to be updated at any time during an inmate's stay."]
[null,"JT4","The system should alert users to any key data from the medical/mental health screening questionnaire."]
[null,"JT5","The system should allow users to update an inmate’s prescription and non-prescription medication data at any time during an inmate's stay."]
[null,"JT6","The system should provide a list of medications to be dispensed at each medication pass to an individual inmate and to all inmates."]
[null,"JT7","The system should allow users to dispense medications with a bulk action (without having to go into each inmate's record individually)."]
[null,"JT8","The system should be able to capture an inmate’s acceptance or refusal of medication, along with comments."]
[null,"JT9","The system should provide a log of all medication dispensed to an inmate."]
[null,"JT10","The system should allow users to capture an inmate’s prescription and non-prescription medications, including administration times, amounts, and instructions during the booking process. "]
[null,"JT11","The system should allow authorized users to access medical and mental data for inmates. "]
[null,"JT12","The system should visibly flag key medical information and special dietary needs."]
[]
["Inmate Funds"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JU1","The system should intake any cash or other funds an inmate has on her/her person during the booking process and establish an inmate account with those funds."]
[null,"JU2","The system should generate a form that a user can sign (manually or electronically) to acknowledge receipt of cash or other funds."]
[null,"JU3","The system should include transactions in an inmate’s account such as deposits, withdrawals, release of funds, and audits."]
[null,"JU4","The system should be able to generate a receipt for each transaction that users, inmates and receiving persons can sign (manually or electronically) to acknowledge the transaction."]
[null,"JU5","The system should automatically update inmate account balances to reflect transactions."]
[null,"JU6","The system should allow an account summary to be printed at any time during an inmate stay."]
[null,"JU7","The system should allow additional funds received from visitors or by mail to be credited to an inmate’s account."]
[null,"JU8","The system should allow inmate funds to be released as part of the inmate release process."]
[null,"JU9","The system should carry forward inmate account balances (including negative balances) from previous jail stays."]
[]
["Inmate Property"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JV1","The system should be able to intake individual pieces of property."]
[null,"JV2","The system should include a comment field for each piece of property."]
[null,"JV3","The system should provide a means of duplicating a property item when most of the data remains the same from one item to the next."]
[null,"JV4","The system should generate a form that can be signed (manually or electronically) to verify inmate property intake."]
[null,"JV5","The system should allow authorized users to maintain a list of property locations."]
[null,"JV6","The system should capture the location of a piece of property, whether it is in a locker assigned to that inmate or in a shared/general-purpose location. The system should track the transferal of the property from one location to another."]
[null,"JV7","The system should allow additional property to be taken in at any time during an inmate stay, including property received in packages or from visitors."]
[null,"JV8","The system should be able to release individual pieces of inmate property at any time during an inmate stay. Date, time, and recipient information should be tracked for each property release."]
[null,"JV9","The system should be able to generate an inmate property intake receipt or release form that users, inmates and receiving persons can sign (manually or electronically) to acknowledge the receipt or release of property."]
[null,"JV10","The system should be able to print an inmate property summary or inventory at any time during an inmate's stay."]
[]
["Issued Property"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JW1","The system should be able to track agency property such as linens and clothing which are issued to inmates."]
[null,"JW2","The system should capture when property is returned or when additional items are issued."]
[null,"JW3","The system should track any items which are banned from use by an inmate and provide the user a warning message during the issuance process."]
[null,"JW4","The system should allow users to configure sets of commonly issued items and create a preset to issue or return them in bulk."]
[null,"JW5","The system should allow users to assign and print barcodes for issued property."]
[null,"JW6","The system should be able to display a real-time running total of available individual pieces of agency property."]
[]
["Jail Reporting"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JX1","The system should provide a report generator for building custom statistical and analytical reports from jail data. The report generator should be provided by the same vendor and should not be a third-party application."]
[null,"JX2","The system should restrict access to the report generator and individual report templates by user or user group."]
[null,"JX3","The system should not allow a user who does not have access to particular data via the application user interface to gain access to that data via the report generator."]
[null,"JX4","The system should allow the creator of the report template to build reports for any data entered into the jail product."]
[null,"JX5","The report generator should allow the creator of the report template to control layout and formatting options for each jail report template. This includes such options as field arrangements, column widths, label text, font sizes, and line spacing."]
[null,"JX6","The report generator should allow the creator of each jail report template to choose which users can access and/or run the report and/or modify the report template."]
[null,"JX7","The report generator should support the use of aggregate (math) functions including Sum, Average, Count, Count Blank, Minimum, and Maximum."]
[null,"JX8","The report generator should allow data to be grouped or sorted by any data element."]
[null,"JX9","The report generator should allow multiple data filters to be applied using \"and/or\" logic."]
[null,"JX10","The report generator should allow jail reports to be saved (as PDF, .XLS, or .CSV), printed, or emailed directly from the report."]
[null,"JX11","The report generator should allow jail report templates to be saved and modified at a later time."]
[null,"JX12","The report generator should support adding the jail reports to user's dashboards."]
[null,"JX13","The report generator should allow recurring jail reports to be scheduled and automatically uploaded to a file-system or e-mailed to specified users or user groups on certain days and times."]
[null,"JX14","The report generator should support ad-hoc queries."]
[null,"JX15","The report generator should support creation of jail reports such as the following:\n - Inmate summary forms with agency-defined fields \n - Current inmates by held for agency, cell block, etc.\n - Inmates currently in or out of the facility\n - Occupied cells or available cells\n - Recent bookings to provide to media outlets\n - Arrest reports for a specified time period\n - Inmates held year-to-date compared to previous years\n - Annual report of inmates held for outside agencies\n - Inmate days based on holding status, age, gender, etc.\n"]
[]
["Livescan/AFIS Interface"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JY1","The system should include an interface to Livescan/AFIS."]
[null,"JY2","The interface should also, once the inmate is fingerprinted and mug shots have been taken, send the mug shots back in the NIST file for addition to the inmates record in the JMS."]
[]
["VINE Interface"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JZ1","The system should include an interface to VINE."]
[null,"JZ2","The interface should allow demographic data to be sent to Appriss by way of an SFTP site upon booking and release of each inmate."]
[null,"JZ3","The interface should also support sending a daily population report to Appriss via the same SFTP site."]
[]
["N-DEx"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"JAA1","The system should package case reports in XML for N-DEx submission."]
[null,"JAA2","The system should allow for automatic submission of N-DEx data to the FBI or another repository that supports the N-DEx format."]
[]
["Interface A"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[]
[]
[]
["Interface B"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]

{"sheet":"Mapping","index":5,"n_rows":59,"n_cols":8,"rows_kept":59,"cut":false,"hidden":false,"merged":[]}
["Mapping"]
[]
["General"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"MA1","The system should use mapping functionality which is based on ESRI-compatible mapping components."]
[null,"MA2","The system should allow for unlimited map layers, including ESNs, counties, roads, railroads, postal zones, and aerial imagery."]
[null,"MA3","The system should allow users to click on any point on the map to view information such as an ESN, county boundaries, postal zones, address, coordinates, and nearest intersection."]
[null,"MA4","The system should include map panning and zooming functions."]
[null,"MA5","The system should allow the user to re-center the map on a CFS, unit, or default location."]
[null,"MA6","The system should allow users to calculate the distance between two points on the map."]
[null,"MA7","The system should allow users to toggle aerial imagery for the map."]
[null,"MA8","The system should allow authorized users to maintain a list of map marker types and assign corresponding map icons."]
[null,"MA9","The system should ignore city, state and zip code data when searching for addresses if there are no matches. "]
[null,"MA10","The system should allow authorized users to configure any of the standard map actions as system hot keys."]
[null,"MA11","The system should allow for geo-verification of addresses within CAD and JMS when the client map application is not open."]
[null,"MA12","The system should allow agency GIS personnel to maintain map data."]
["CAD"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"MB1","The system should integrate the mapping product with the CAD product and make the map accessible with a single click or keystroke from the CAD product."]
[null,"MB2","The system should allow all dispatch functions to be available from the map."]
[null,"MB3","The system should include map functions, such as zooming and plotting, on other dispatch windows."]
[null,"MB4","The system should allow users to issue CAD commands directly from the map."]
[null,"MB5","The system should automatically plot active and waiting calls for service on the map as they are entered, and automatically remove them from the map as they are cleared."]
[null,"MB6","The system should display key CFS data on the map, including address, coordinates, nearest intersection, cross streets, incident code, priority level, and assigned units. "]
[null,"MB7","The system allows the map to filter units so that only certain units are displayed on the map."]
[null,"MB8","The system should display dispatch alerts (if a CFS has been waiting past an agency-defined time to be dispatched) on the map."]
[]
["Markers"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"MC1","The system should allow the user to filter the units which are viewable on the map, such as on-duty units and/or off-duty units, or by unit type (law enforcement, fire, and EMS)."]
[null,"MC2","The system should display key unit data on the map, such as call sign unit type, and status."]
[null,"MC3","The system should display unit alerts for officer safety checks (based on agency-defined times) on the map."]
[null,"MC4","The system should allow map markers to expire and should allow those expired markers to either be removed from the map or grayed out upon expiration."]
[null,"MC5","The system should roll-up multiple markers for units so that they take up less space, if those units are all at the exact same location."]
[null,"MC6","The system should allow users to place agency-customizable map markers, without creating a CFS, for items such as controlled burns and road construction."]
[null,"MC7","The system should allow users to search on customized map markers."]
[null,"MC8","The system should plot the ESN on the map for Phase II calls."]
[null,"MC9","The system should display a shaded area which represents the uncertainty distance around the origination points for Phase I and Phase II calls."]
[]
["Routing"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"MD1","The system should include a routing function on the map which allows routes to be drawn between any combination of unit locations, CFS addresses, and other addresses, including intersections, mile markers, and latitude/longitude coordinates."]
[null,"MD2","The system should be able to mark road segments as closed for routing purposes. Barriers or closed segments should be displayed on the map."]
[null,"MD3","The system should allow users to create bookmarks which capture both the location on the map as well as the zoom level and any currently enabled map layers."]
[null,"MD4","The system should allow users to create a print preview of mapping routes. "]
[null,"MD5","The system should allow users to create a PDF of mapping routes and send them in an email. "]
[]
["Search"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"ME1","The system should include geospatial search which supports the following:\n -  Searching and pinning specific addresses including intersections, mile markers, and latitude/longitude coordinates\n -  Searching for addresses within a radius\n -  Searching for addresses within an area (polygon) drawn by the user\n -  Searching and pinning addresses by person or business name"]
[null,"ME2","The system should allow all of the search results to be exported to a CSV file."]
[]
["Interface A"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[]
[]
[]
["Interface B"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]

{"sheet":"GIS","index":6,"n_rows":9,"n_cols":8,"rows_kept":9,"cut":false,"hidden":false,"merged":[]}
["GIS Services"]
[]
["Data Migration and Scrubbing"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"GA1","The vendor should provide GIS data migration and scrubbing services as part of the implementation."]
[null,"GA2","The vendor should test the GIS data to ensure proper functioning."]
[null,"GA3","The vendor should set up the data with the needed configuration and load it into the ArcGIS format."]
[null,"GA4","The vendor should create address locator and network dataset files to support geocoding and map routing functionality."]
[null,"GA5","The vendor should be capable of providing additional GIS services without involving a third party."]

{"sheet":"Personnel","index":7,"n_rows":70,"n_cols":8,"rows_kept":70,"cut":false,"hidden":false,"merged":[]}
["Personnel"]
[]
["Personnel"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"PA1","The system should allow authorized users to create and manage employee records."]
[null,"PA2","The system should provide a guided step-by-step process (wizard) for entering a new person/user into the system to ensure that all steps are completed."]
[null,"PA3","The system should allow unlimited photos to be attached to each employee record."]
[null,"PA4","The system should allow bulk updating of employee records."]
[null,"PA5","The system should retain records indefinitely for employees who are no longer with the agency and track the date(s) employees were in and out of service."]
[null,"PA6","The system should allow authorized users to set up detailed permissions for each employee, both individually and within groups."]
[null,"PA7","The system should allow authorized users to generate a permissions audit report for an employee which shows all areas of the system to which that person has access, what type of access it is, and how it is granted."]
[null,"PA8","The system should allow authorized users to maintain lists of personnel job titles, personnel addressed as, personnel specialties, personnel groups, divisions, termination reasons and service types."]
[null,"PA9","The system should allow authorized users to view and print a log of the changes to an employee's personnel records."]
[null,"PA10","The system should allow authorized users to create unlimited custom form templates which are used to associate agency-specified data with individual personnel records."]
[null,"PA11","The system should allow users with access to personnel records to use the custom forms to enter and maintain the associated data."]
[null,"PA12","Agency-defined custom fields should be available in Personnel."]
[]
["Employee Promotions"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"PB1","The system should allow authorized users to create and maintain employee promotion records."]
[null,"PB2","The system should allow employee promotion records to have files attached to them via upload or scanner."]
[null,"PB3","Agency-defined custom fields should be available in Employee Promotions."]
[]
["Employee Commendations"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"PC1","The system should allow authorized users to create and maintain employee commendation records."]
[null,"PC2","The system should allow authorized users to maintain a list of commendation types."]
[null,"PC3","The system should allow employee commendation records to have files attached to them via upload or scanner."]
[null,"PC4","Agency-defined custom fields should be available in Employee Commendations."]
[]
["Employee Disciplinary Actions"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"PD1","The system should allow authorized users to create and maintain employee disciplinary action records."]
[null,"PD2","The system should allow authorized users to maintain lists of offense types and disciplinary action types."]
[null,"PD3","The system should allow employee disciplinary action records to have files attached to them via upload or scanner."]
[null,"PD4","Agency-defined custom fields should be available in Employee Disciplinary Actions."]
[]
["Employee Training"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"PE1","The system should allow authorized users to create and maintain training records for employees."]
[null,"PE2","The system should allow authorized users to manage lists of training locations, training certificates, and training categories."]
[null,"PE3","The system should allow users to view a list of courses which will soon expire."]
[null,"PE4","The system should allow training courses to be entered for an individual employee or entered in bulk with a single action for multiple employees (for example, all officers or dispatchers). "]
[null,"PE5","The system should be able to calculate the total training hours completed by each employee."]
[null,"PE6","The system should allow users to view the number of training hours completed by an employee within a specified time frame (for example, annual training hours completed). "]
[null,"PE7","The system should display upcoming training/certification expirations in a highly visible manner."]
[null,"PE8","The system should be able to list courses that were offered by the agency but declined by an employee."]
[null,"PE9","The system should be able to store default course data for common training courses."]
[null,"PE10","The system should allow training records to have files attached to them via upload or scanner."]
[null,"PE11","The system should allow authorized users to create unlimited custom form templates to associate agency-specified data with individual training records."]
[null,"PE12","The system should allow users with access to training records to use the custom forms to enter and maintain the associated data."]
[null,"PE13","Agency-defined custom fields should be available in Employee Training."]
[]
["Citizen Feedback"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"PF1","The system should provide a means for tracking citizen feedback."]
[null,"PF2","The system should allow authorized users to maintain lists for feedback types, feedback actions, and feedback dispositions."]
[null,"PF3","The system should allow a CFS or case report to be associated with the citizen feedback record."]
[null,"PF4","The system should allow one or more officers or other users to be associated with the citizen feedback record."]
[null,"PF5","The system should automatically check the reporting citizen's name against the master name index."]
[null,"PF6","The system should allow citizen feedback records to have files attached to them via upload or scanner."]
[null,"PF7","Agency-defined custom fields should be available in Citizen Feedback."]
[]
["Interface A"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[]
[]
[]
["Interface B"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]

{"sheet":"System","index":8,"n_rows":232,"n_cols":8,"rows_kept":232,"cut":false,"hidden":false,"merged":[]}
["System (Global)"]
[]
["General"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SA1","The system should allow all software products (CAD, JMS, etc.) to be configured and managed from one system window."]
[null,"SA2","The system should allow authorized users to change commonly altered variables without intervention from the vendor or IT."]
[null,"SA3","The system should allow multiple (unlimited) users to be logged into the system and using the same applications simultaneously."]
[null,"SA4","The system should allow multiple (unlimited) users to view, add, and edit information in the same records simultaneously."]
[null,"SA5","The system should provide global search functions for names, addresses, phone numbers, and vehicles."]
[null,"SA6","The system should ensure that these search functions include SOUNDEX, partial, and wild-card searches."]
[null,"SA7","The system should be able to generate a summary of each record displayed within these search results, including digital images."]
[null,"SA8","The system should be able to print, save or email the search summary directly from the summary window."]
[null,"SA9","The system should be able to print, save or email a list directly from the list view window."]
[null,"SA10","The system should be able to print, save or email a record directly from the record detail window."]
[null,"SA11","The system should allow the creation of an agency-specified header for use within printouts from the system. This header should include both an image and text."]
[null,"SA12","The system should allow authorized users to maintain a list of phone number types. "]
[null,"SA13","The system should allow authorized users to maintain a list of relationships (for example, spouse, neighbor, stranger, etc.)"]
[null,"SA14","The system should allow authorized users to maintain a list of agencies."]
[null,"SA15","The system should allow authorized users to electronically redact reports from within the built in print preview option. "]
[null,"SA16","The system should allow authorized users to identify text or images within the report by drawing a box overtop of the item, and then the system should replace the underlying item with the box."]
[null,"SA17","The system should convert redacted text to an image so that the text itself is no longer searchable or retrievable in any other fashion."]
[]
["Security"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SB1","The system should provide multiple levels of data security control, including access by user and user group."]
[null,"SB2","The system should be FIPS 140 compliant for all network communication, including wired and wireless communication. "]
[null,"SB3","The system should verify access by a username and its corresponding password."]
[null,"SB4","The system should support integration with Active Directory."]
[null,"SB5","The system should support integration with multiple Active Directory servers."]
[null,"SB6","The system should support dual-factor authentication with a username and password and a USB dongle that meets FBI Security Addendum Requirements."]
[null,"SB7","The system should never display passwords and should store passwords as hashed values in the database."]
[null,"SB8","The system should provide each user with a single username and password for the entire system."]
[null,"SB9","The system should include the following agency-configurable password parameters:\n - Minimum length\n - Case sensitive\n - Required to use uppercase and lowercase \n - Required to include a numeral\n - Frequency of password changes\n - Number of previous passwords which cannot be reused"]
[null,"SB10","The system should be able to display agency-defined password parameters when users create or change a password. "]
[null,"SB11","The system should allow authorized users to determine when any user’s password was last changed and to change any user’s password."]
[null,"SB12","The system should provide access levels, including view, edit, delete, and admin for each component of the system for users and user groups."]
[null,"SB13","The system should track the user who last entered or updated any record as well as the date and time of the modification."]
[null,"SB14","The system should store a read-only checksum for digital files and provide a means of determining if anyone has tampered with the file."]
[null,"SB15","The system should be able to create an audit record each time a record is created, edited, or viewed."]
[null,"SB16","The system should create an audit record each time an audio or video attached to a case report is exported from the system."]
[null,"SB17","The system should include a screen that displays users who are currently logged in. "]
[null,"SB18","The system should include a screen that displays successful and unsuccessful log-ins and password changes."]
[]
["Architecture"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SC1","The system should use an n-tier architecture."]
[null,"SC2","The system should use an SQL database."]
[null,"SC3","The system should allow connections to the SQL database via free ODBC drivers."]
[null,"SC4","The system should include all server hardware. Network equipment and workstations will be furnished by the agency."]
[null,"SC5","The system should include 30-minute rolling backups of all data to an offsite location (not within the city or county) during which the system performance cannot be degraded."]
[null,"SC6","The system should include a testing/training server."]
[null,"SC7","The system should ensure that the testing/training server includes the physical servers, server operating system software, server application and database software, installation, testing and configuration."]
[null,"SC8","The system should ensure that the testing/training server allows the users to work with a copy of the production data without influencing the production environment."]
[]
["User Interface"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SD1","The system should be able to perform data validation/error checking for fields in the system."]
[null,"SD2","The system should allow specific fields to be designated as required to force users to enter essential information before saving a record. "]
[null,"SD3","The system should visibly identify required fields (for example, by color-coding them). If a user attempts to save a record without completing all required fields, The system should visibly notify the user of the remaining required fields (for example, by causing the required fields to flash)."]
[null,"SD4","The system should provide auto-completion for frequently entered information. Once the user begins typing, the appropriate data should automatically populate into the record. "]
[null,"SD5","The system should use the tab key to move between fields."]
[null,"SD6","The system should include a spellchecker for narrative fields throughout the system. Users should be able to add words such as local place names to the spellchecker’s dictionary."]
[null,"SD7","The system should allow users to use a shortcut key to jump to any menu or submenu link on an open screen, even if that screen is not currently in focus."]
[]
["Integration"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SE1","The system should ensure that all of its modules integrate with other modules (CAD, JMS, etc.), are provided by the same vendor, and are not third-party applications."]
[null,"SE2","The system should use a single database, capable of being hosted on a single server, for all modules."]
[null,"SE3","The system should allow all modules (CAD, JMS, etc.) to be accessible to authorized users from the same application window. "]
[null,"SE4","The system should allow all modules (CAD, JMS, etc.) to be accessible based on assigned permissions. All modules should be accessible with a single click or keystroke, without launching a separate program or application."]
[null,"SE5","The system should provide a one-time, single point of data entry to allow information to be accessible from other modules in the system once it has been entered."]
[null,"SE6","The system should have consistent user interface design throughout."]
[null,"SE7","The system should ensure that all modules share the same master records for names, addresses, property and vehicles and that these master indices are located within a single database."]
[null,"SE8","The system should integrate alerts between all modules so that alerts entered in one area are available in all others."]
[null,"SE9","The system should ensure that all modules integrate with the vendor’s Financial module (not a third-party application) to support all financial features and functions."]
[null,"SE10","The system should provide an agency and user-customizable dashboard that displays summary information from any modules which the user has permission to access (for example, that user’s open case reports, the current jail roster, or a list of recently added warrants)."]
[null,"SE11","The system should be able to display dashboard reminders of overdue and soon-to-be-due tasks for users or user groups."]
[null,"SE12","The system should be able to display web links on the dashboard to provide direct links to third-party websites via the default browser."]
[]
["Master Name Index"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SF1","The system should use a single database, accessed from all modules, for storing the master name records. The system should link all activity of a person (or business) to a single master name record. If the system does not do the above, please explain the master name index architecture and functionality."]
[null,"SF2","The system should link the master name record to and provide a list of all activity with which the person was involved, including calls for service, case reports, jail bookings, citations, parking tickets, warrants, registered vehicles, and anything built with custom modules."]
[null,"SF3","The system should include links from the activity list on the master name record to any other record in which the person was involved, in the module the activity originated. Access to these records should be controlled by user permissions."]
[null,"SF4","The system should include links to the master name index from name fields found throughout the system.\n"]
[null,"SF5","The system should support advanced name searching based on any combination data elements in a master name record."]
[null,"SF6","The system should allow first, middle and last names to be entered in any order in name fields."]
[null,"SF7","The system should not require separate search fields for first, middle, and last names."]
[null,"SF8","The system should allow searching for persons and businesses by full or partial names."]
[null,"SF9","The system should connect the alias and the master name record so that searching for an alias finds that master record."]
[null,"SF10","The system should include the option of using SOUNDEX when searching for names. "]
[null,"SF11","The system should permit the use of age ranges, as well as specified ages on master name records."]
[null,"SF12","The system should eliminate the need to duplicate any name information after it has been entered into the system."]
[null,"SF13","The system should allow users to update any basic data fields and add or modify other information on the master name record once it has been created."]
[null,"SF14","The system should display the last modified date on each master name record."]
[null,"SF15","The system should cross-reference each master name record to all other records associated with a person or business."]
[null,"SF16","The system should automatically add names to the master name index when entered elsewhere in the system. "]
[null,"SF17","The system should allow users to manually enter names directly into the master name index."]
[null,"SF18","The system should have built-in checking to reduce the possibility of creating duplicate master name records for the same person or business."]
[null,"SF19","The system should have the ability to merge duplicate name entries, giving the user the choice of which name data elements to keep for the merged record."]
[null,"SF20","The system should allow users to select, view and merge multiple names at once to a single master name record rather than having to merge them one name at a time. "]
[null,"SF21","The system should store narrative comments linked to a name and display it upon inquiry for its master name record."]
[null,"SF22","The system should display an address history for persons including dates of address changes."]
[null,"SF23","The system should check all coded entries in the master name index for validity at the time of data entry."]
[null,"SF24","The system should automatically check a name against outstanding warrants, known sex offenders and current jail inmates and notify or alert users accordingly."]
[null,"SF25","The system should automatically display any user-entered name alerts (medical alerts, gang alerts, officer safety threats, and other agency-defined alert types)."]
[null,"SF26","The system should allow users to create new name alerts from or for a master name record."]
[null,"SF27","The system should allow users to specify expiration dates on name alerts. Expired name alerts should remain attached to master name records for historical purposes."]
[]
["Master Address Index"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SG1","The system should link all activity occurring at an address to a single master address record."]
[null,"SG2","The system should eliminate the need to duplicate any address information after it has been entered into the system."]
[null,"SG3","The system should allow users to update any basic data fields and add or modify other information on the master address record once it has been created."]
[null,"SG4","The system should use a single database, accessed from all software modules, for storing the master address index so that information entered about an address in JMS, for example, is available in RMS. If the system does not do the above, please explain the master address index architecture and functionality."]
[null,"SG5","The system should ensure that the each master address record includes a listing of all persons and businesses known to reside at the address, which are included in the master name index."]
[null,"SG6","The system should display the following related activities with master address records: calls for service and case reports. Activities should be listed in reverse chronological order for each master address record."]
[null,"SG7","The system should include links from the activity list to any record in which the address was involved, in the module where the activity originated. Access to these records should be controlled by user permissions."]
[null,"SG8","The system should provide a notification to the user that an address is either valid or invalid. For invalid addresses, the system should display a list of potential valid addresses."]
[null,"SG9","The system should link to the master address index from address fields anywhere in the system."]
[null,"SG10","The system should cross-reference each master address record to all other records associated with that address."]
[null,"SG11","The system should allow users to manually enter addresses directly into the master address index."]
[null,"SG12","The system should provide a report that shows manually added addresses."]
[null,"SG13","The system should have built-in checking to automatically merge differently-typed addresses that correspond to the same location (for example, \"103 W. Cherry St.\" and \"103 west cherry street\" should not create duplicate address records)."]
[null,"SG14","The system should be able to merge address records (for example, \"Berkot's Super Foods\" and \"1152 E. Walnut St.\" are the same address and should be treated as such)."]
[null,"SG15","The system should automatically display any user-entered address alerts (hazardous materials, alarm system, water supply information, officer safety threats, and other agency-defined alert types)."]
[null,"SG16","The system should allow users to create new address alerts from a master address record."]
[null,"SG17","The system should allow users to specify expiration dates on address alerts. Expired address alerts should remain attached to the master address record for historical purposes."]
[null,"SG18","The system should allow searching for address by house number, full or partial street name, state, or zip code."]
[null,"SG19","The system should ensure that searching for a merged address record finds the appropriate master address record (for example, searching on \"Berkot's Super Foods\" finds \"1152 E. Walnut St.\")."]
[]
["Master Vehicle Index"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SH1","The system should link all activity for a vehicle to a single master vehicle record."]
[null,"SH2","The system should eliminate the need to duplicate any vehicle information after it has been entered into the system."]
[null,"SH3","The system should allow users to update any basic data fields and add or modify other information on the master vehicle record once the master vehicle record has been created."]
[null,"SH4","The system should use a single database, accessed from all software modules, for storing the master vehicle index. If the system does not do the above, please explain the master vehicle index architecture and functionality."]
[null,"SH5","The system should include a listing in the master vehicle record, with history, of the vehicle's registered owners."]
[null,"SH6","The system should display the following related activities with the master address index: calls for service, traffic stops, tow calls, case reports, citations, field identifications, and parking tickets. Activities should be listed in reverse chronological order for each master vehicle record."]
[null,"SH7","The system should include links from the activity list to any record in which the vehicle was involved, in the module where the activity originated. Access to these records should be controlled by user permissions."]
[null,"SH8","The system should link to the master vehicle record from vehicle fields anywhere in the system."]
[null,"SH9","The system should cross-reference the master vehicle record to all other records associated with the vehicle."]
[null,"SH10","The system should allow users to manually enter vehicles directly into the master vehicle index."]
[null,"SH11","The system should have built-in checking to reduce the possibility of creating duplicate master vehicle records for the same vehicle."]
[null,"SH12","The system should check all coded entries in the master vehicle record for validity at the time of data entry."]
[null,"SH13","The system should automatically display any user-entered vehicle alerts (including agency-defined alert types)."]
[null,"SH14","The system should allow users to create new vehicle alerts from a master vehicle record."]
[null,"SH15","The system should allow users to specify expiration dates on vehicle alerts. Expired vehicle alerts should remain attached to the master vehicle record for historical purposes."]
[null,"SH16","The system should support searching for vehicles by full or partial plate numbers."]
[null,"SH17","The system should allow vehicles to be searched by any data element or combination of data elements (for example, vehicles registered to the name \"Smith\" and/or red pickup trucks)."]
[]
["Notifications/Messages"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SI1","The system should support \"if\", \"then\" and \"when\" business rules for notifications throughout the system."]
[null,"SI2","The system should include system-wide business rules that allow authorized users to configure unlimited notification scenarios for users and workgroups."]
[null,"SI3","The system should provide business logic which, from information entered into certain required fields, will automatically display other required and/or corresponding fields which pertain to the data already entered."]
[null,"SI4","The system should include business rules that notify users and/or open up the next sequential required field(s) and/or window(s) based on the information added to the record."]
[null,"SI5","The system should include system-wide business rules that allow users and user groups to be notified via multiple communication channels including internal system messaging, e-mail, paging, and/or SMS."]
[null,"SI6","The system should include an internal e-mail-style messaging system that supports the secure transmission of messages with attachments within the agency's network."]
[null,"SI7","The system should warn users that they have unfinished tasks when they attempt to log out. "]
[]
["Statutes"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SJ1","The system should include federal, state, and local statutes. "]
[null,"SJ2","The system should allow authorized users to create and update local statutes and/or ordinances in the system."]
[null,"SJ3","The system should provide a hotkey that can be used from anywhere in the system to search statutes by statute numbers, title, and/or text within a statute description. "]
[]
["Attachments"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SK1","The system should allow the attachment of files (for example, .DOC , .XLS, .JPG, .WAV) to specified record types. Attached files should be able to be opened or viewed on any workstation by authorized users who have the necessary third-party applications (such as MS Word or MS Excel)."]
[null,"SK2","The system should support scanning and attaching documents directly to records in the system without the need to first save them elsewhere."]
[null,"SK3","The system should store attached files on the vendor’s server within the vendor’s software (not on an open network folder) for security and ease of access."]
[]
["Custom Forms"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SL1","The system should allow authorized users to create custom data collection forms to support agency-specified functionality, without any intervention from the vendor or IT."]
[null,"SL2","The system should ensure that each custom form is associated with, and subordinate to, a non-custom form (the parent form)."]
[null,"SL3","The system should allow authorized users to create an unlimited number of custom forms."]
[null,"SL4","The system should ensure that the custom forms are integral with the rest of the system and not provided via a third-party application."]
[null,"SL5","The system should support printing the data from custom forms via an agency-defined output template and process similar to a mail merge."]
[null,"SL6","The system should allow authorized users to add unlimited data items from the parent form when creating a custom form.  "]
[null,"SL7","The system should allow authorized users to include as many fields for data collection as are necessary on custom forms, including entirely new fields (not previously stored in the database) as well as the following:\n -  Names from the Master Name Index\n -  Vehicles from the Master Vehicle Index\n -  Addresses from the Master Address Index\n -  Personnel, units, and other agency-defined lists"]
[null,"SL8","The system should support the following types of agency-defined fields for custom forms: \n -  Address\n - Automatic record sequence numbers\n - Multiple item select boxes\n - Vehicles/Dates/Times\n -  Dollar value\n -  Free form text\n -  Names\n -  Numbers\n -  Signatures  (for electronic signatures)\n -  Checkboxes\n -  Yes/No drop-downs\n -  Drop-downs from agency-defined lists"]
[null,"SL9","The system should allow a custom form to create a relationship on master name or master address records when those fields are specified within the custom form."]
[null,"SL10","The system should allow authorized users to specify the label for each field and data item on a custom form."]
[null,"SL11","The system should allow authorized users to specify if each field on a custom form is required or not required."]
[null,"SL12","The system should allow for setting the default value for each field."]
[null,"SL13","The system should allow the authorized users to arrange the data items and fields in any order on the form."]
[null,"SL14","The system should make the data items and fields on custom forms available to the built-in report generator."]
[null,"SL15","The system should allow records captured via custom forms to be saved to an external file, emailed and/or printed."]
[]
["Custom Modules"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SM1","The system should permit authorized users to create custom modules designed to meet specific data collection, management, reporting, and output needs without intervention from the vendor or any additional costs."]
[null,"SM2","The system should ensure that custom modules are part of the main software solution and not a third-party application."]
[null,"SM3","The system should allow authorized users to create as many custom modules as desired."]
[null,"SM4","The system should allow information captured in custom modules to be output from the system in accordance with agency-defined output templates."]
[null,"SM5","The system should allow authorized users to include as many fields for data collection as are necessary within custom modules, including entirely new fields (not previously stored in the database) as well as the following:\n -  Names from the Master Name Index\n -  Vehicles from the Master Vehicle Index\n -  Addresses from the Master Address Index\n -  Personnel, units, and other agency-defined lists"]
[null,"SM6","The system should support the following types of agency-defined fields for custom modules: \n -  Dates/times\n -  Dollar value\n -  Free form text\n -  Names\n -  Numbers\n -  Signatures  (for electronic signatures)\n -  Checkboxes\n -  Yes/No drop-downs\n -  Drop-downs from agency-defined lists"]
[null,"SM7","The system should allow authorized users to specify all of the field labels for a custom module."]
[null,"SM8","The system should allow authorized users to arrange and display custom module fields in any order."]
[null,"SM9","The system should allow all data included in a custom module to be searched and included in statistical reports."]
[null,"SM10","The system should allow a custom module to create an relationship on master name or master address records when those fields are specified within the custom module."]
[null,"SM11","The system should allow authorized users to define and filter the list view of the data included within the custom module."]
[null,"SM12","The system should allow records from custom modules to be directly converted to PDF files within the system."]
[null,"SM13","The system should allow records from custom modules to be attached to emails. "]
[]
["Support and Maintenance"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SN1","The vendor should provide a minimum of 3-4 major software updates (not bug fixes) per year as part of the vendor’s software maintenance agreement. Please include contact information for 5 existing customers older than 3 years who can verify this."]
[null,"SN2","The vendor should schedule and perform software updates at no additional cost to the agency as part of the standard maintenance agreement."]
[null,"SN3","The vendor should load all software updates on the vendor-provided testing/training server(s) before loading them on vendor-provided production servers."]
[null,"SN4","The vendor should provide server operating system software and database software as part of the complete system."]
[null,"SN5","The vendor should include all updates, enhancements, new versions, and upgrades of the server operating system software and database software as part of its standard software maintenance agreement. "]
[null,"SN6","The vendor should ensure that the agency will not have to purchase any third-party server operating system software updates and/or newer versions as long as its software maintenance agreement is maintained. "]
[null,"SN7","The vendor should be responsible for the vendor-provided physical server(s). As necessary to support proper system functions, the vendor should either replace components and/or the entire server(s) as part of the standard maintenance agreement. This includes ensuring that system performance criteria are met and that the server(s) continue to meet the server operating system and database software requirements."]
[null,"SN8","The vendor should provide, as part of the standard maintenance agreement, real-time 24x7x365 monitoring of the vendor-provided physical server(s) and operating system software to detect and manage any potential issues with the system."]
[null,"SN9","The vendor should load all system software updates to the server and then automatically load updates to each client machine at next startup without any intervention from the vendor or IT."]
[]
["Data Conversion"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SO1","The vendor should perform data conversion as part of the project."]
[null,"SO2","The vendor should convert the following data:\n - EmergiTech CAD\n - EmergiTech JMS"]
[null,"SO3","The vendor should complete all data conversion before the go live date for the new system."]
[]
["LEADS/NCIC Queries"]
[null,"ID","Requirement","Yes","Future","Modify","No","Comments"]
[null,"SP1","The system should include an interface to the LEADS/NCIC system."]
[null,"SP2","The system should allow authorized users to run LEADS/NCIC queries directly from within the system."]
[null,"SP3","The system should restrict access to run LEADS/NCIC queries to authorized users or user groups."]
[null,"SP4","The system should allow NCIC query returns to populate Master Name and Master Vehicle records."]
[null,"SP5","The system should provide a list of all LEADS/NCIC queries which have been run and the associated returns. This list should be filterable by date, query type, user, and/or workstation."]