CAD

1 2 3 4 5 6 7 8 9 10 11 Computer Aided Dispatch The software must allow for aliases on the validation sets in the event that authorized personnel must send codes to outside agencies. The software must be able to associate codes to more than one location or panel when the same validation table entries are used in multiple locations. A toolbar must provide the following tasks: Open, Save, Delete, Cut, Copy, Paste, New and Print. The toolbar must be flexible enough to add buttons for quick access to other installed applications. The system must provide the ability to quickly and easily assign default agency-defined status codes. The system must provide the ability to dispatch to a call type and create a corresponding call type for all agencies responding, including Law Enforcement, Fire and EMS. The software must utilize self-cleansing windows to allow users to open and use multiple (minimum of 20) child windows simultaneously and be able to tile and/or cascade the child windows. The software must have a tabular design, allowing access to multiple layers within the system. The software must allow authorized user(s) to define the screen layout (e.g., position and size of windows) and save the individual configurations based on the user’s login. The agency staff must be able to adjust commonly altered variables such as codes, tables, report parameters, etc., without the services of a professional programmer. The software must provide a table look-up capability for frequently entered information; once the data is selected the information will automatically populate the user’s data record. The software must provide the ability to verify the quality of data entered into the database by performing immediate error checking, prohibiting invalid data to be stored in the database. The software must provide the ability to input, access, and store an agency-defined level of historical data online. The software must have the capability to be used in a multi-jurisdictional environment. The software must provide the ability for multiple users to be on the system and in the same applications simultaneously The system must use consistent validation table processing. The system must allow for agency-defined validation tables. The software must provide agency-defined function keys and function key combinations. The software must provide the ability to use the command line to accomplish all CAD functions. The software must have the ability to enter multiple units via command line or mouse. The CAD system must fully integrate with the Records Management Software (RMS) provided by the same software vendor. Full integration includes the automatic transfer of CAD incident information to the RMS, such as reducing data entry and notifying dispatchers and officers of hazards/alerts on specific person and/or locations. Fully Compliant Modification/Custom Software Not available Comments 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 Computer Aided Dispatch The software must provide a one-time, single-point of data entry that allows information to be accessible from other applications. All applications must integrate tightly with each other to provide the greatest operator and system efficiency. The software must provide an online help feature available for all functions, including data entry, search/inquiry, menu, form and report generation. The system administrator must be able to identify an individual who last entered or updated any transaction as well as the date of the modification. The system must also identify an individual who initially created the CFS in CAD. The software must provide the ability for a user to create and store ad-hoc reports. The software must provide the ability to directly output from a data search to a printer upon user request and schedule reports to print. The software must provide the capability to add unlimited narrative to records, ensuring critical information is captured. Each agency must be able to maintain its own tracking number (ORI) separate and specific from other agencies in the system. The dispatch center can maintain a separate ORI from all other agencies. All commands can be modified to follow the dispatch center naming conventions and the ability for the system administrator to add new commands. The system must support command line, function key and drag and drop mouse capabilities for all dispatch functions. The system must use a combined call function that can create a single call to handle multiple Law Enforcement, Sheriff, Fire and EMS agencies. The ORI must be retained for each agency and dispatch center. Each Call Taker and Dispatcher position must be able to define the filter it sorts and determine how many to sort for the call control panel. The software must provide a separate message screen that shows all Call Taker, Dispatcher and MDT/MCT (mobile unit) messages sent to the Call Taker/Dispatcher position. The software must provide automatic date/time stamping and user ID tracking of all Call Taker and Dispatcher processes to track call and unit activity and all command processing. Fully Compliant Modification/Custom Software Not available Comments 36 37 All Call Taker/Dispatcher activity is logged and can either be printed or queried. 38 All cleared calls must be automatically transferred to the appropriate RMS. An incident/call number can be quickly created (quick call) entering the following minimal 39 information: incident type, location and priority of call. Any name entered by a Call Taker/Dispatcher must provide the capability to be associated or 40 added to the RMS master name database. 41 The Call Taker/Dispatcher position must be capable of being either local or remote. 42 The system must flag all incidents/calls that require a report submitted by the officer. The user must be able to access a command line with one keystroke from anywhere in the 43 system. 44 The system must provide the ability to view cleared calls. Cleared calls must have the appropriate security, defined by the agency, to prevent 45 unauthorized modification and viewing. 46 47 48 49 50 51 52 Computer Aided Dispatch The system must have the ability to reactivate cleared calls and allow additional activity/dispatching of units to the original incident number. The CAD Data Entry Window must show the closest cross streets. The CAD Data Entry Window must allow jacket and global vehicle processing. The CAD Data Entry Window must allow for a non-E911 person to be deleted. The CAD Data Entry Window must indicate (such as checkmarks) on the tabs if the tab contains information. The CAD Call Control Panel must allow users to customize the tool bar. The CAD Call Control Panel must allow for filters to be set, displaying just one type or any combination of call types (police, fire, EMS). Fully Compliant Modification/Custom Software Not available Comments 53 The CAD Quick Entry Call must support multiple license plates and driver’s license numbers. The software must allow multiple Unit Status Control Panels to be opened with different configurations. The software must have a list of values that can be used to facilitate the data entry process, 55 such as abbreviations, directions, case status codes, weather codes, etc. 56 The CAD Unit Status Control Panel must allow users to customize the toolbar. CAD Security The software must provide component (i.e., modules, entry screen) and document (i.e., case 57 documents, ticket documents) security to permit and restrict the rights of specific users and/or groups The software must have the ability to set up permission for all components, including add, 58 edit, view, delete, print, etc. 54 59 There must be three possible components permissions: granted, denied and not specified. 60 61 62 63 Authorization for ORI-based components must be defined by the ORI. Components must have the ability to restrict individual users or groups. Components cannot be changed or deleted by users. The software must support authorization templates, which are defined by name. 64 Authorizations must be identified by user name and corresponding confidential password. 65 Passwords must never be displayed. 66 The system administrator must have the ability to easily create users. 67 The system administrator must have the ability to easily change passwords. 68 A user’s password can be changed, but must not be displayed to the system administrator. 69 A user’s password must be encrypted when stored in the database. 70 The software must automatically date and time stamp all user’s login times and locations. 71 The software must automatically log all security violations. 72 The software must provide a purge for the security violation log. 73 The software must allow the user and system login log to be purged. The software must provide a flag to prompt a document’s author that individual permissions 74 must be set for a document when it is created. Computer Aided Dispatch The system administrator must have the ability to grant individual permissions to documents in the event that a document’s author is unavailable to do so. 76 The software must log access to documents by access type. 77 The software must allow the document access log to be purged. 75 CAD Call Taker Requirements/Dispatcher E911 calls must automatically generate and populate the call entry window with all known 78 data (e.g., address, venue, registered name, phone number, etc.) based on the call-in number. The Call Taker screen must capture a minimum of information, including: call type, agency, 79 status, phone number, address, cross street, nature of call, unlimited narrative and caller/complainant names. The system must provide agency-defined security features to restrict commands and usage 80 for each user. The Call Taker must provide the option to put an unlimited number of partially completed 81 call(s) on hold to retrieve at a later time. The system must automatically alert the Call Taker of a possible duplicate call when two 82 calls provide addresses that are in close proximity to each other – radius defined by the agency. The Call Taker must have the ability to override geo-based addresses and system document 83 overridden addresses. The Call Taker must provide easy access to the RMS name database for additional 84 information on the Caller/Complainant, such as missing person, outstanding warrant, prior incidents, hazards, etc. 85 Multiple Call Takers and Dispatchers must be able to work on the same call simultaneously. 86 The Call Taker must be able to enter individual officer activity. 87 The software must allow an unlimited number of Call Takers. The system must be able to schedule calls for future dispatch (i.e., parades, funerals, fairs, 88 etc.) and assign to a specific unit. 89 The system must be able to display a list of all scheduled calls. 90 The system must allow for agency-defined CFS types. 91 The icon displaying the CFS type on the map must be agency-defined. 92 Unit recommendations and overdue recommendations must be agency-defined. The software must provide the ability to exchange one unit with another, automatically 93 recording in history that the first unit was initially dispatched and then switched with the second unit. The system must be able to reroute a unit from one call to another in a single command and 94 stack the original call against the rerouted unit. 95 Command line text must be agency-defined. 96 Commands used in the command line must be agency-defined. 97 The command line must carry out all unit/call commands. 98 The system must add the following vehicle information to a CFS including: VIN State Fully Compliant Modification/Custom Software Not available Comments Computer Aided Dispatch Plate Color Year Make Model The software must allow users to select a vehicle already entered into the system and send 129 that information to State/NCIC. As the call is being entered, any potential associated call must be made known to the Call 130 Taker/Dispatcher. 131 The system must automatically track all activity by updating a CFS as part of the call. The Call Taker/Dispatcher/Officer working the call must be alerted of any known hazards or 132 alerts known for an address/name/vehicle, etc. 133 The incident number for all responding agencies must be easily displayed. 134 The ICR # not event a sequence. 135 The system must provide capability to add additional incident numbers for the CFS. All narrative entered into an incident must be immediately available to everyone working the 136 CFS. 137 The following information must be maintained with each CFS: NCIC Responses All Known Associated Persons Special Response Information All Associated Vehicles The system must allow a CFS to be canceled prior to dispatching it, recording the activity in 138 history. The software must maintain CAD commands and command descriptions, such as Open 139 CFS, Add Narrative to CFS, Change Unit Status, etc. CAD Dispatching Requirements/Call Taker E911 calls must automatically generate and populate the call entry window with all known data (e.g., address, venue, registered name, phone number) based on the call-in number. 140 (ANI and ALI data). SCSO PSAP currently uses the Positron VIPER digital hardware and Positron Power 911 software system. The software must provide Dispatchers with access to all CFS information, such as 141 narrative, hazards, unit information, etc. The dispatch screen must provide quick and easy access to all CFS information, specifically 142 type, agency, status, phone number, address, cross street, nature of call, unlimited narrative and caller/complainant name(s). 143 The system must provide the option to setup a dispatch position as Law Enforcement only, Fire only, EMS only, combined Fire and EMS, or combined Law Enforcement, Fire and EMS. Fully Compliant Modification/Custom Software Not available Comments The software must provide the option of restricting Dispatchers to only use related 144 commands for Law Enforcement, Fire or EMS. For example, a Law Enforcement only setup will not allow the Dispatcher to access Fire Run Cards. 145 Multiple Call Takers and Dispatchers must be able to work on the same call simultaneously. 146 The call control panel must display all calls that are assigned. 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 Computer Aided Dispatch The system must provide agency-defined security features to restrict commands and usage for each user. The software must provide Dispatchers with access to all unit recommendations and unit commands based on Law Enforcement, Fire and EMS access security. The software must provide the ability to access any CAD or RMS function based on authorized security. The system must provide the ability to filter (e.g., include or exclude) types of calls from the call control panel. function must be available from the dispatch position. The combined call The system must automatically alert the Dispatcher of a possible duplicate call when two calls provide addresses that are in close proximity to each other – radius defined by the agency. The software must provide agency-defined check-in times for officers to increase safety. When an officer exceeds the allotted time, the software must visually and audibly display a warning alerting the Dispatcher. The reminder must provide an override/reset feature. The software must provide agency-defined dispatch timers based on CFS type and priority. The software must visually display a warning alerting the Dispatcher that too much time elapsed without assigning a unit(s) to the call. The software must provide the Dispatcher with easy access to the RMS name database for additional information on the Caller/Complainant, such as missing person, outstanding warrant, prior incidents, hazards, etc. Officer initiated quick call and traffic stop call entry functions must be accessible from the dispatch position. The software must allow for officer initiated quick calls and traffic stops to be transferred to a regular incident/call. The software must allow Dispatchers to override geo-base addresses, run priority and unit recommendations. The software must have the ability to sort the CFS window up to two levels. The software must support an unlimited number of dispatch positions. The system must provide the ability to exchange one unit with another, automatically recording in history that the first unit was initially dispatched and then switched with the second unit. The system must be able to reroute a unit from one call to another in a single command and stack the original call against the rerouted unit. A call control panel must display active CFS. The call control panel must filter or subset the active calls by: Dispatched Calls vs. Non-dispatched Calls Law Enforcement Calls Fire Calls EMS Calls Specific Coverage Area/Beats Specific Priority The call control panel must sort by: Priority Unit Number Fully Compliant Modification/Custom Software Not available Comments Computer Aided Dispatch Call Type Case Number Agency Dispatchers must be able to quickly dispatch units from a displayed list of available units in 166 the call control panel. 167 The system must be able to dispatch units and perform call-taking activities simultaneously. All Dispatcher/Call Taker positions must be able to filter calls by agency including or excluding specific agencies. The system must provide a mapping interface with the ability to plot incidents/calls and the 169 units on a street map. The plotting of the incident/unit information must be a by-product of normal dispatch. Thehave access to the mappingcontrol the map from within the CAD The dispatcher must Dispatcher must be able to software that provides user maintainable 170 layers, such as hydrants, hot spots and known offenders. 171 Layers on the map, which can be turned on or off based on the level of detail required. 172 All dispatch functions must be accessible from the map. The system must be able to change a unit’s status by placing the cursor on the unit or the 173 map. To dispatch a unit, the software must allow the user to drag and drop a unit to the call control 174 panel. From the unit control panel, a dispatcher must have access to a list of available calls and 175 dispatch the units to calls. The software must maintain CAD commands and command descriptions, such as Open 176 CFS, Add Narrative to CFS, Change Unit Status, etc. CAD Personnel 168 177 The software must require first name, last name and ID number to enter a personnel record. 178 The software must allow name/badge number a chance for existing user. 179 The software must support personnel records by ORI and ID number. 180 Only authorized users may have access to a personnel record. When attaching a case to a personnel record, the software must only show the officer’s 181 name and agency. CAD Messaging The software must provide voiceless communications through messaging between 182 Dispatchers, Call Takers, Mobile Computing Terminals (MCT), and other agency-defined users. 183 The software must store/send message to user not yet locked up. The software must provide a separate message screen that shows all Call Taker, Dispatcher 184 and Mobile Computing messages sent to the Caller Taker/Dispatcher. The software must allow a CAD user to send and store messages to other users, groups, 185 positions or MCTs. 186 The software must allow a message to be sent to multiple recipients. 187 The software must allow a user to store a received message and delete a message. Fully Compliant Modification/Custom Software Not available Comments Computer Aided Dispatch 188 The software must be able to log all sent messages. CAD Call Scheduling The software must automatically schedule CFS for future dispatch to help manage special 189 events, such as parades, festivals, prisoner transport, etc. 190 The software must allow events to be created by a call or by sending a message. 191 The software must be able to display a list of all scheduled calls. 192 The software must allow a user to manually activate a call. 193 Authorized users must have the ability to activate a scheduled call at any time. 194 The software must send a message when the scheduled activity occurs. 195 The software must support location override for scheduled calls. CAD Call Stacking 196 The software must allow units to be assigned to multiple calls at the same time. The software must allow a user to view a unit’s call stack to see what call the unit is on, and 197 what calls the unit will be handling next. 198 The software must have only one call that is active per unit. The software must be set up by ORI to allow automatic dispatching of a unit when the unit is 199 available. The software must have the calls sorted in the order to be dispatched, with the original order 200 of first in, first out (FIFO). The software must allow the user to reorder the call stack, delete a call for service from the 201 stack, and transfer a CFS to another unit’s stack. The software must allow the flexibility of placing a CFS on a call stack and not have it 202 automatically dispatched with that unit. CAD Units Law Enforcement unit recommendations must be incident type specific and allow for multiple 203 levels of backup. 204 Law Enforcement unit recommendations must support different unit types (i.e., one-man, twoman or K-9) to respond to a CFS based on the incident type, priority and in-progress flag. Fully Compliant Modification/Custom Software Not available Comments 205 The software must support changing the unit’s assigned primary police beat during the shift. 206 The software must support second and third level police beats to be initially setup for a unit at the beginning of a shift or to be changed during the shift. 207 All Law Enforcement, Fire or EMS unit activity must be captured in a unit history database. 208 209 210 211 212 The Law Enforcement, Fire or EMS unit recommendation maintenance must maintain operating procedures on each incident type. All Law Enforcement, Fire or EMS unit personnel activity must be captured in a unit personnel history database. The software must allow agency-defined icons to represent unit types. The system must allow the agency to define an icon for each type of unit as defined by the agency. The system must include a pre-defined set of typical unit statuses that can be modified by the agency. Computer Aided Dispatch The software must allow the setup of timers based on ORI, Unit Type, Status and Priority. The software must allow authorized users to create timers for all unit types. The software must allow authorized users to update timers for all unit types. The software must generate a unit log, showing all actions that unit had taken. The unit log must show date/time of entry, status, action, CFS #, CFS type, CFS location and 217 unit location. 218 Maintenance on units must allow entry of the following: Agency-based Unit Type Unit Alias Radio Number Unit MCT ID CAD Hazards/Alerts The software must alert the Call Taker, Dispatcher and/or Officer of previous CFS at a 219 location. The software must alert the Call Taker, Dispatcher and/or Officer if an active warrant exists 220 for any person at the location or for the caller/complainant. The software must alert the Call Taker, Dispatcher and/or Officer if any gun permits are at 221 the location or guns are registered to the caller/complainant. The software must alert the Call Taker, Dispatcher and/or Officer if the caller/complainant is 222 a known offender, a suspect in an open case, or a career criminal. The software must alert the Call Taker, Dispatcher and/or Officer if hazardous material is 223 stored at a business site. The software must alert the Call Taker, Dispatcher and/or Officer if there is any serious 224 medical information concerning a person at the location. The software must alert the Call Taker, Dispatcher and/or Officer if the location has an 225 associated vacation check or house watch. The software must alert the Call Taker, Dispatcher and/or Officer if the location is a known 226 crash pad or drug site. The software must alert the Call Taker, Dispatcher and/or Officer if a school is in the 227 location. The software must alert the Call Taker, Dispatcher and/or Officer if a building pre-plan or 228 Geo-file information exists for the location. The software must alert the Call Taker, Dispatcher and/or Officer if orders of protection are 229 associated with the location and/or caller/complainant. The system must provide the ability to reactivate an alert if the system falsely expires that 230 alert. The software must alert the Call Taker, Dispatcher and/or Officer of a possible duplicate call 231 if two calls have addresses that are near each other. The software must alert the Call Taker, Dispatcher and/or Officer if a unit has gone over its 232 allocated time, as setup for the CFS type to increase officer safety. The software must have the ability to set a timer for call for service types based on priority. 233 This timer alerts the dispatcher that an agency-specified time has elapsed and no units have been assigned to the called. 234 The software must alert the Call Taker, Dispatcher and/or Officer on an as-needed basis. 213 214 215 216 Fully Compliant Modification/Custom Software Not available Comments Computer Aided Dispatch The software must allow the user to create an alert with a category, description, and duration of time and an assigned priority for the alert. 236 The software must allow the user to change the priority of system-generated alerts. 237 The software must allow for all alerts to be purged within an expired date range. The software must automatically purge all expired alerts and move them to the historical 238 alert log. CAD Note Pads The software must allow a note pad function that allows CAD users to type in any unlimited 239 text and store the text within CAD. 240 The software must have the ability to leave electronic shift notes 241 The software must support a subset of information by type. 242 The software must allow a document to be attached via standard document controls. 243 Note pad entries must be date/time stamped. 244 The software must allow note pads to be marked and only allow manual deletes. CAD Run Cards The software must allow the creation of run cards to define fire and EMS recommendations 245 that are used to dispatch units based on the CFS type, fire or EMS district, and time of day for a business. The software must allow the user to assign a priority to the CFS, and enter the date/time 246 range that the run card is active. The software must allow the user to define units or unit type/stations to a CFS based on Fire 247 district (quadrant) and CFS type. 248 The software must allow a user to define alarm levels for run cards. The software must support station dispatch, which allows all units or unit types within the 249 station to be placed in the status defined by the action. The software must allow for multiple backups so that if the first backup is unavailable, the 250 system will check for the next available backup. 251 The software must have the ability to add special response narrative for run cards. 252 The Supervisor must be able to maintain Fire/EMS unit run cards. The software must be able to create a Fire run card, an EMS run card and a joint Fire and 253 EMS run card listing and exception report. The software must allow units on a Fire and EMS run card to be placed in the assigned 254 status. 255 The software must recommend most functions for dispatchers. 235 256 Fire/EMS run card recommendations must be assigned by incident type based on activity for an address or business; overrides must be stamped by day of week and time of day. Fully Compliant Modification/Custom Software Not available Comments CAD Unit Recommendations Police unit recommendations must be specific to the CFS type and allow multiple levels of 257 backup. Police unit recommendations must provide for different types of units, such as one-man, two258 man or K-9, to respond based on the CFS type, priority and in-progress flag. Primary police beat can be assigned to a unit at the beginning of a shift or it can be changed 259 during the shift. Computer Aided Dispatch Second and third level police beat can be initially setup for a unit or it can be changed during the shift. 261 Fire/EMS unit recommendations must provide up to nine alarm levels. Fire/EMS unit recommendations must incorporate backup units, move-up units, stand by 262 units and backup stations. The software must provide the user with the ability to adjust the priority and the number of 263 recommended units. The software must be able to swap or exchange one unit with another, and record that the 264 first unit was initially dispatched, and then exchanged with the second unit. 265 All police, fire or EMS unit activity must be captured in a unit history database. The system must provide access to the unit recommendation process as part of the 266 incoming call. Dispatch must have access to all unit recommendations and unit commands based on 267 police, fire and EMS access security. As a part of the police, fire or EMS unit recommendation maintenance, the software must 268 maintain operating procedures on each CFS type. 269 The software must define the icon for the unit type using stand PC tools. CAD ORI Maintenance 270 The software must to maintain all ORIs, including operating ORIs and reference ORIs. The software must support corresponding values based on various CAD and RMS modules 271 for operating ORIs only. The software must require the following mandatory fields: ORI, ORI Abbreviation, Agency 272 Type, Agency Name, Full Address and the Maximum Juvenile Age. 273 The software must automatically dispatch stacked calls in order when a CFS is cleared. 274 The software must create an incident for a particular ORI. When mutual aid (different ORI) is being given, the software must always generate an 275 incident. 276 The software must have one operative case number for each responding agency. 277 The software must have one case number per agency. When mutual aid (different ORI) is being given, the software must generate an incident when 278 a unit of the same agency type responds. The system will provide services, including call input, call status maintenance, event notes, 279 field unit status and tracking, and call resolution and disposition. The system will provide complete integration with all modules within the Public Safety 280 System. The system will automatically query simultaneously the following when a request is submitted: CAD, NCIC, MN CJIS/BCA, RMS Warning/Caution/Previous call history, DMV 281 (Dept. of Motor Vehicles), Trespass Database, Civil Process Orders for Protection, Orders of Harassment. 282 The system will support the ability to enter data via keyboard/command line, or mouse. 260 Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 Briefing Notes The software must provide field officers with a daily summary report of updates, information and alerts. The daily summary report must include information on wanted/missing persons, outside alerts, stolen vehicles and personal/property crimes. The software must support BOLOs for vehicles, including make/model and narrative. The software must support BOLOs for people, including attributes for sex, race, height and narrative. The software must allow for an expiration to be setup for a BOLO. The software must support BOLO jacket and global vehicle processing. Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 CAD Mapping The software must have mapping capability to plot incidents/calls and the units on a street map. The plotting of the incident/unit information must be a by-product of normal dispatch. The dispatcher must be able to control the map from within the CAD display as to zoom, pan and layer control. All dispatch functions must be accessible from the map. The map must have a color-coded, user defined and maintainable layers that help identify real-time critical information, such as unit status and call type. The software must allow for the layers on the map to be automatically turned on based on the CFS and level of details shown. Map layers must be able to be turned on or off manually. The software must provide the ability to dispatch by placing the cursor on the unit or the map. The software must provide the ability to easily change unit status and dispatch units right from the map control panel For each call for service type, the icon that displays on the map for that call type must be agency definable. The map must display only the units within the dispatcher’s assigned ORI or beat. Standard right-click options must be available to map control. Examples include center map on the unit; override unit time; check-in unit; change status; and go-to command (to send a unit to a different location). The map must provide a tool tip on the unit displaying the unit ID and unit location when mouse-over the unit. The map must provide a tool tip on the CFS, which must display the CFS number, the CFS location, and the CFS type when rolling the mouse over the call. Standard right click options, such as center map, open, clear, cancel, service vehicle rotation, access questionnaire, must be available for the call for service. The CAD Mapping must meet the guidelines set forth by the FCC regarding wireless carriers to provide information about a caller as part of the 911 call. The software must have the capability to receive latitude and longitude information via the E911 interface. The software must have the capability to enter latitude and longitude of the caller’s location in the CAD Data Entry Window. The software must retain the latitude and longitude as original call location if the call taker changes the location to an actual address. The software must plot the cellular phone call on the map control panel using a special icon to designate a cell phone call. The software must provide the ability to right-click on a cell phone call to get a list of potential addresses within an agency-defined radius. The call taker must have the ability to select from a list of potential addresses in an agencydefined radius. The software must provide the ability to draw radius around incident and document said radius. The software must have the ability to plot, with agency-defined icon, known activity (e.g., street closures, parades, construction, etc.). Fully Compliant Modification/Custom Software Not available Comments CAD Mapping 25 The software must have the ability to open Call for Service from map. Fully Compliant Modification/Custom Software Not available Comments GIS Requirements 1 Software Solution must be built on the ESRI 9.2 platform. 2 Support the Enterprise Level of ArcGIS Server (ArcSDE). 3 Provide support for Pictometry Imagery. Provide ability to do data replication between a central master GIS database (ArcSDE) and 4 Vendor’s public safety GIS database (ArcSDE). 5 The system shall write spatial data directly to the ArcSDE geodatabase. The system shall provide real-time data sharing between the CAD system and the County’s 6 ESRI GIS system. 7 The system shall provide real time data sharing of GIS updates among CAD workstations. 8 The system shall utilize ArcViewSDE for map generation. 9 The system must be able to upgrade to the most current versions of ArcMap, ArcSDE and SQL Server as those versions become available and are deployed within the County. Fully Compliant Modification/Custom Software Not available Comments 10 The system shall support user-definable map symbology. Support the customization of how maps are displayed within the Vendor’s solution by use of 11 ESRI’s .MXD files. Provide the same advanced routing capabilities as available through ESRI’s Network 12 Analyst. Must be fully integrated into CAD solution. Support the use of ESRI’s 9.2 Dynamic Display technology for high performance display of 13 Units, CFS, etc. on the CAD Map. 14 Support a Services Oriented Architecture. 15 Support the use of an Enterprise Geodatabase. 16 Support Multiple Locator Services for Geocoding. 17 Support multiple maps for multiple agency configuration. Support the use of scale tolerances for map layers to allow certain layers to appear at 18 appropriate zoom levels. 19 Support the ability to use Agency defined icons for Units, CFS, etc. in the software. 20 Support the use of Hyperlinks within the CAD Map. 1 2 3 4 5 6 7 E-911 Interface The E911 interface must provide an interface between the phone company’s E911 system and the CAD system. (ALI and ANI data). SCSO PSAP currently uses the Positron VIPER digital hardware and Positron Power 911 software system. The interface must automatically link E911 data into the computer system via a communications port to a multi-user, multi-tasking workstation. The CAD software must be able to load data directly from an E911 system. The system must be able to accept data from a caller ID system. The interface must provide the ability to transfer and maintain the following data elements from the phone company’s database to the CAD system: Telephone Number Time of Call Date of Call Customer Name House Number House Number Suffix Street Name Zone (ESN) City/Community Class of Service Operator Position The interface must accommodate telephone file layout changes without needing a programmer on site. The interface must provide the ability to discriminate between class of service on the telephone ALI record and appropriately handle the class of service field on the CAD screen. Fully Compliant Modification/Custom Software Not available Comments 8 The interface must allow for validation checks against: Address verification file Active calls for service Previously entered hazards Activate various checks in an E911 control file Cell phone capability to plot caller location EMS Questionnaire AVL Building Watch Ability to Lookup Personnel History Ability to Log Ride-a-longs Accept or Override Priority Unlimited Filter Capability Store Window Preference Check Subject, Vehicle and Location Geo-file Ability to Add Narrative to Call 9 The interface must provide the ability to perform the following statistical analysis reports: 10 Total calls log within a user-selected data range. Number of calls within a user-selected date and time range within a user-selected geo11 graphic portion of the jurisdiction. E-911 Interface Reporting 12 E-911 History Listing Fully Compliant Modification/Custom Software Not available Comments Netclock Interface The Netclock/2 Interface must provide a real-time, interactive interface to NetClock time synchronization equipment. The Netclock/2 Interface must synchronize the server with the time provided by the NetClock 2 hardware and the operating system will synchronize the client with the server. 1 Fully Compliant Modification/Custom Software Not available Comments TDD Interface The system must provide an interface from a Terminal Device for the Deaf (TDD) to the dispatcher, enabling communication with the deaf person via the display station. 2 Must support a Telecommunications Device for the Deaf (TDD) interface. The software must support a TDD interface that provides a two-way communication between 3 the CAD user and the person using a TDD. The software TDD interface must allow entry of canned messages for quicker 4 communications. 1 Fully Compliant Modification/Custom Software Not available Comments Personnel Management/Administration Requirements The software must record and maintain the following personnel information no every 1 employee: Employee Full Name Employee Address Employee Badge or ID Number Social Security Number Home Phone Number Department Number and Extension Date of Birth Current Assignment Assignment History Current Rank Rank History Hire Date Termination Date Education, including Degrees, Certifications Special Skills Medical Information Department Injuries Blood Type Emergency Notification Information Employee Status or Promotions Reprimands Commendations Spouse's Name Driver's License Number Employee Demographic Information Disciplinary Actions 2 The software must maintain records of equipment issued to all personnel, such as: Item Type Quantity Serial Number Date Issued Condition of Item Returned Date Condition Returned The software must maintain records on employees with special skills, including, but not 3 limited to: Foreign Language Public Relations Training Bomb Disposal Training Fully Compliant Modification/Custom Software Not available Comments 4 5 6 7 8 9 10 11 Personnel Management/Administration Requirements First Aid Training SWAT Training Breathalyzer Training The software must provide the ability to perform weekly or monthly scheduling of employees for a minimum of 6 months. The software must track employee training and maintain records on: In-Service Classes Outside School Training Firearms Qualifications Training Basic Academy Training Automatically Re-Schedules Re-Certification Classes College Classes if Applicable The software must maintain the following data elements for training: Employee ID Number Training Course Title Training Location Re-certification Date Length of the Course Course Completion Date Course Comments Course Expenses College Credit Hours The software must provide the ability to print a summary report detailing all employees and all training conducted within a specified date range. The software must provide the ability to print a summary report of all training received by an employee during his/her course of employment. The software must provide the ability to print a detailed employee report with all fields of data in the personnel record. The software must the ability to print a summary department personnel listing sorted by Employee Name. The software must provide the ability to print a detailed department personnel listing sorted by Employee Name. Fully Compliant Modification/Custom Software Not available Comments Warrant Requirements 1 Auto generate warrant number Mandated Fields: Case number Entered by Date of entry Record type: Felony, Gross Misdemeanor, Misdemeanor, Petty Misdemeanor Date issued (by court) Issue by (Agency within county or out of county) Court assigned number Controlling agency Disposition Disposition/ date/ time Violation date (for juvenile warrants) Emancipation limits- state codes State entry - to default to auto entry or be able to manual take off Mis/ remarks open text/ state guidelines Name/ system to allow integration with all modules-be able to transfer data to appropriate field for entry without manually entering such data. Date of birth Physical descriptions - state mandated Address(es) show current and previous address, only current to transmit ID numbers: to include but not limited to Drivers license, Social security, FBI, state mandated regulations. 2 FBI, State Mandated Regulations Must be able to enter multiply AKA's, SMT or ID numbers - limit/restriction by state requirements Date assigned Agency assigned Officer assigned Service type Date served Served by Date returned Service status Offense: Currents offense MOC code, software to translate to Nibrs/UOC code, same with Original offense MOC code. Software to enter proper statute code. Bail Fine Bond type Bond amount Software to maintain and track all data on warrant, being active or cleared. Allow the 3 correction of errors and provide audit trail of changed data to the record. Fully Compliant Modification/Custom Software Not available Comments Warrant Requirements 4 Software to input state and national numbers into warrant record when submitted to same. 5 6 7 8 9 10 11 12 13 Software must change status of warrant records at any time with proper security and passwords. Software to determine distinction of Audit and Juvenile warrants. Software to provide distinction between active, served, and cleared warrants. Software to show all alerts on individual name. Software to be able to track whether hold is placed with another agency. Software to allow searches on outstanding warrants upon entry of name from any place in the system and notify the user with a warning (Alert) of possible match. Software to maintain records for unlimited time. Software must be capable of generating a printed report from all related fields, within specified time range. All entries to be transferred to the state/national level at time of entry. Fully Compliant Modification/Custom Software Not available Comments Interface Requirements CAD 1 The CAD and RMS systems must allow for full integration. Vendor must provide username and password access to database backend for customized 2 read only web based reporting. 3 Vendor must provide data dictionary and table relationships for CAD and RMS database(s). 4 System shall be SQL or other ODBC compliant database. E911 and TDD Interface Systems The CAD system shall interface to the 911 controller so as to populate the CAD workstation 5 event screen with ANI and ALI data. The Sherburne County Sheriff's Office PSAP currently uses the Position Power 911 software system. 6 CAD shall satisfy NENA standards for E-911 / CAD interface. The CAD system shall interface with the 911 system to allow TDD and TTY connections 7 through CAD. 8 Integrate TDD data capture from all CAD workstations. System shall support FCC-mandated Wireless 911 Call location receipt, per Phase I and II 9 of FCC Docket 94-102. Citation Writer The mobile client shall retain all previously run DVS/CJIS/NCIC query data on the local 10 machine or server in an XML or compatible format. DVS / CJIS / NCIC The system will have the ability to initiate CJIS/NCIC message types using pre-designed forms as part of the application. Responses to inquiries will be returned to the original 11 terminal requesting the inquiry and will give a visual and audio indication that the message is waiting to be viewed. The system shall automatically format and send CJIS/NCIC inquiries upon the entry of traffic 12 stop, which includes a license plate number, and (optionally) state of issue. The system shall automatically format and send CJIS/NCIC inquiries upon the entry of 13 subject data to include name, DOB and/or race and sex. The system shall automatically format and send CJIS/NCIC inquiries upon the entry of a 14 towed/impounded vehicle, boat, trailer, or other licensed object. The system shall automatically format and add a name into the Master Name Index MNI 15 upon the entry of CJIS / NCIC inquiries. When a vehicle registration is run in the system and the response returned, the system shall 16 read the name from the response and automatically form a CJIS/NCIC driver license query (QDP) to check for wanted hits on the person. The system shall include a set of the most common message formats used for preparing 17 CJIS/NCIC inquiries. The vendor will be responsible for updating the interface to the CJIS/NCIC system as the 18 State changes its specifications. Fully Compliant Modification/Custom Software Not available Comments Interface Requirements System must comply with CJIS/NCIC policies and procedure regarding security and 19 encryption. 20 The system will offer secure access to CJIS/NCIC include The Criminal Justice Information System (CJIS) is the system provides "hot file" information 21 and is accessed through CJDN (Criminal Justice Data Network). National Crime Information Center (NCIC). The Criminal Justice Data Network (CJDN) 22 provides the network access or interface to NCIC. All of the CJIS files that meet the federal criteria pass on information and data to the NCIC system. Computerized Criminal History (CCH). The State Bureau of Criminal Apprehension maintains the CCH files. Computerized criminal histories are a compilation of reports from 23 law enforcement, presecution, courts, and correction agencies in Minnesota. The iterface allows the criminal justice system to track an individual from his/her arrest through discharge and disposition of each offense. The Criminal Justice Data Communications Network (CJDN) is the overall system that provides criminal justice agencies computer access to data stored on the State and National 24 systems. All systems must meet their requirements and policies at the time of implementation. All inquiries to the State of Minnesota must adhere to State Query formats. The vendor will 25 be responsible for obtaining the latest policies for networking and the multiple formats required at the time of implementation. CJRS (MOC) / NIBRS (UCR) The Minnesota Criminal Justice Reporting System (CJRS) is a statewide centrally located computerized data collection repository of criminal information. The information is collected 26 from participating law enforcement agencies statewide. The information collected is submitted into the CJRS for processing and dissemination and is used primarily for statistical purposes. System shall integrate and transmit files to State of Minnesota for reporting according to 27 guidelines in "CJRS Manual". Sheriff's Office must seamlessly interface to this system for mandated reporting 28 requirements. CriMNet CIBRS The State of Minnesota collects person/incident information from state law enforcement 29 agencies through the CriMNet CIBRS System. The Sheriff's Office system must support the creation of batch export files in compliance with 30 "CIBRS XML Upload File Format Spec.v01.00" http://www.crimnet.state.mn.us/Standards/standards.htm Dynamic Imaging MRAP (Minnesota Repository of Arrest Photos) The Sheriff's Office Jail Management Module shall be able to interface with the State of 31 Minnesota Dynamic Imaging software used to capture photos of arrested persons. Fully Compliant Modification/Custom Software Not available Comments Interface Requirements The Jail Management Module shall manage booking intake information including, but not limited to, case number, date, time, location of arrest, arrested person's full name, DOB, 32 address, phone numbers, next of kin, arrest purpose, property inventory, cell placement and cell checks. 33 The system shall assign a booking number to each arrest. 34 The system shall be able to delineate between adults and juveniles. 35 The system shall remove redundant data entry into the Dynamic Imaging system by seamlessly export the above information into Dynamic Imaging's relationship table database. Fully Compliant Modification/Custom Software Not available Comments LiveScan Fingerprinting (BCA) The Sheriff's Office Jail Management Module shall be able to interface the LiveScan 36 Fingerprinting software used to capture fingerprints from arrested persons in the State of Minnesota. The Jail Management Module shall manage booking intake information including, but not 37 limited to, case number, date, time, location of arrest, arrested person's full name, DOB, address, country of birth, and one to many criminal counts for each arrested person. 38 The system shall be able to delineate between adults and juveniles. Statewide Supervision System (MN DOC) 39 The Sheriff's Office Jail Management Module shall be able to interface the State of Minnesota Department of Corrections "Statewide Supervision System" for arrested persons. The system shall manage booking intake information including, but not limited to, case number, date, time, location of arrest, arrested person's full name, DOB, adult/juvenile, 40 address, race, citizenship, date/time of booking, release information, and one to many criminal counts for each arrested person. MESSAGE SWITCH Ability to integrate previously entered information with current record and forward that record 41 to next recipient, i.e. CAD to Field report Field report to records management, records management to State mobile updates from centralized server. System will include message switching functionality with will support automated messages 42 and queries between a number of user applications. 43 System will have one of the following compliances: XML API (Application Programming Interface) Other System will facilitate bi-directional communications of integrated and non-integrated 44 applications. System will support communications between CAD, RMS, Mobile and also outside 45 mandated systems including, but not limited to, NCIC, III, State, etc.) System will support both workstation and remote devices (i.e., mobiles) to log on to the host 46 applications. Interface Requirements 47 System should run in a Windows environment. 48 System should satisfy the open architecture standards and provide multi-protocol support. 49 System should provide scalable expansion to prevent bottlenecks. System will allow all necessary middleware to interconnect all the applications to be run 50 through the messge switch. Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Civil Process Module Must convert data from old system to new. Must automatically assign civil process number. Must automatically assign date of entry. Must automatically assign date of ID of individual entering data. Must have ability to assign process to specific deputy - don't want it automatically assigned civil deputy isn't the only one that serves civil process, some civil process is also faxed out to other agencies to attempt service). Must have ability to assign date received. Must have ability to assign date of issue (re: documents issued by the court). Must have ability to define type of paper(s) to be served (should be able to edit/add/delete from menu of papers as well as free form for unusual documents). Would like to enter this information only once - so that it can be exported to the Certificate of Service once process is complete. Must have a long name field to accommodate long names, dba, fka, obo, businesses, etc. without cutting off. Would like to be able to copy certain information, and edit if needed (if there are multiple people being served the same documents - would like to be able to copy the information instead of entering for each individual/entity). Must be able to enter title of papers (x versus y). Would like to be able to select a person to reference and the Case name (x vs. y) to appear on the invoice. Invoice must also contain Process type (Subpoena, Summons and Complaint, etc.) and also Civil Process Number. Must have ability to assign date of service deadline. Must have ability to define how papers were received (Court, County Attorney, mail, fax, box in-person, etc.) Must have ability to assign number of papers received. Must have ability to assign number of people to be served. Must have the ability to enter multiple names if needed (may have to serve several different people related to the same process - we don't want to be repetitive and have to enter a separate process for each). Must have yes/no designation to be billed or not. Must be able to select who we want to bill. Would like yes/no designation for In Forma Pauperis service. Must have a detailed transaction record for billing purposes and accounts receivable (Advance payments, services fees, deputy time, mileage, etc - any charges associated with a process as well as any payments made and keep a running account balance). Must create invoice for each specific process without having to re-enter data. Would like area to enter service attempts if desired (but do not want an invoice automatically calculated based on these attempts). Fully Compliant Modification/Custom Software Not available Comments 25 26 27 28 29 30 31 32 33 34 35 36 37 Civil Process Module Must have our fee schedule built into system (that can be updated as fees go up or change) so that invoice can be automatically calculated. Must have a memo field in the accounting area so that charges can be explained in greater detail. Must be able to define status/disposition (open, closed). Must have ability to assign County of origin/what County papers were issued out of. Must have yes/no designation for Court appearance required. Must have ability to assign date and time of scheduled court date. Must have ability to enter Court case number. Must have ability to define/create role (plaintiff, petitioner, defendant, respondent, attorney, witness, DOC, other, etc.) Must have ability to define/assign status of Court Order (1 year order, 2 year order, 6 months, 2 weeks) Must have the ability to enter more than one address for potential service (work address or 2nd alternate address). Must have the ability to specify the address that process was served at (we may not know this address until it's returned from the deputy - may not be in the system yet and will have to be entered in order to generate a Certificate of Service). Must be able to enter phone numbers for specific name entry (home number, cell, work, business, etc.) Must have an optional Attn: line in the address part of the module (returning to Law Firm or Business not an individual). Fully Compliant Modification/Custom Software Not available Comments Must have ability to define/assign status/type of service (served, not served, served/posted, 38 served/given to, served/left with, etc. - as well as a free form area to type in specific details of service or non-service that can be printed on the Certificate of Service if desired. 39 Must be able to edit system generated invoices, certificates. Must have a "Notes" area that can be used for internal purposes as well as an area to 40 compile information to be shared with the client. Must have option to add notary designation to certificate of service (needed for some 41 Certificates - but not all). Must be able to generate/design specific reports to fit our needs (example: we need a report that will indicate how many individuals/entities that have been served - there may be several 42 individuals/entities served for one process number - i.e.: 5 witnesses served pertaining to one case/process). 43 Must be able to generate/design specific reports to fit our accounting needs. Would like to be able to select criteria for reports (may want to select a summary report, 44 totals only report, detailed report, etc.). Would like this program to interface with the other divisions of the Sheriff's Office - but read 45 only access. All editing/changes to be made by authorized personnel only. Civil Process Module Must integrate with other modules (pull information from master index - jail, records, etc) 46 have the ability to update - i.e.: current address/phone number etc. but keep the complete history intact. Must have several different query options (i.e.: name, address, civil process number, 47 document, date, status or any combination). Fully Compliant Modification/Custom Software Not available Comments Activity Reporting and Scheduling The module must have the ability to create department schedules. The module must have the ability to create department schedules by personnel. The module must have the ability to create department specific activities. The software must automatically update from training module. The software must have the look and feel of a monthly schedule. Must have the ability to track and document personnel hours. The ability to add personnel to specific units is required. The module must have the ability to update CAD with units and personnel. The module must have the ability to create a rotating schedule. The module must have the capability to create time reports. Must have the ability to run roll call reports. The module must be integrated with CAD. The module must have the ability to create agency specific reports on all captured fields or 13 combination of fields. 1 2 3 4 5 6 7 8 9 10 11 12 Fully Compliant Modification/Custom Software Not available Comments Briefing Notes/BOLOs 1 The module must provide field officers with a daily summary report of updates, useful information and alerts. 2 The report must serve as a single point of contact to maintain communication between administrators and officers. 3 The module must allow remote officers to access the report through a web browser on a password protected web page, so officers can remain in the field. 4 The report must support and allow continuous updates. 5 Authorized administrators must have the ability to enter narrative in free-form text on any subject, such as outside security jobs, charity work, etc. 6 Users must have the option to enter information under specific headings, such as missing persons, wanted, outside alerts (BOLOS), etc. Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 Career Criminal Registry Agency-defined categories are required, i.e., Sex offender, violent offender, DUI. Agency-defined violent vs. non violent is required. The module must have the ability to create agency-defined statuses. The software must track parole/probation agents. The module must capture terms and conditions. The module must capture complete registrant department history. The software must have the ability to document unlimited offenses. The software must capture dates of registration. Fully Compliant Modification/Custom Software Not available Comments 9 The module must have the ability to automatically create officer warnings throughout system. 10 The module must have the capability to attach photos. 11 The software must automatically create system wide alerts on all registrants. 12 The module must have complete access from CAD, Corrections and Mobile. The software must have the ability to create department -specific reports from any and all 13 captured fields. 14 The software must have the ability to quickly reference all activity of listed registrants. 15 The module must have the ability to quickly reference all registrants’ department activity. 16 The module must have quick access to photos. Case Management & Investigations Case Management & Investigations System will provide a means where the status, assignment, details and follow-up on any 1 individual case will be clearly accessible to entire agency. System will have the ability to automatically transfer entire case file and all related data to 2 Sherburne County (some scanned and digitized items included). 3 System will provide a means to track assignment of case to any investigator. System will track timelines of each case to include, but not limited to, case assignment date 4 and time, all follow-up dates and times, case charging date and time, case clearance date and time. 5 System will have the ability to assign and track statuses to include, but not limited to, active, inactive, pending assignment, unassigned, cleared by arrest, cleared by formal complaint, System will have the ability to assign and schedule follow-up reminders by anyone having 6 access to the case. System will have the ability to subset cases based on user defined criteria including, but not 7 limited to, type of case, status of case, etc. 8 System will have the ability to apply user defined solvability factors to any case. System will allow unlimited text narrative and attachment of any industry standard file format 9 to be imported into a case file. System wlil allow searching and subsetting certain file types to merge with standardized 10 notification documents (i.e., victim notifications, etc.). System will have a user defined notification capability. (i.e., notify property manager when 11 case assigned, etc.) System will have the ability to restrict, either temporarily or permanently, certain data 12 elements within a case file or an entire case file. System will have the ability to track monetary transactions as well as forefeiture transactions. 13 14 System will have the ability to track access and time stamp access to any case. System will have the ability to set user defined time parameters for archiving a case based 15 on mandatory State and/or Federal requirements. Fully Compliant Modification/Custom Software Not available Comments Records Management System System will be comprehensive and integrated to the CAD, Mobile, and Field Reporting 1 components. System will be integrated to the same shared databases used by Mobile and Field Reporting 2 including, but not limited to, location geofile, master name, juvenile and property. 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 System will allow query to master databases of names, locations, vehicles, and property from any module within RMS without entry disruption or exiting current entry area. System will provide a synopsis of RMS information on any event based on any query made to the master database files. System will also provide a synopsis of information already entered at time of event entry and modification to RMS. System will provide a means of alerting entry personnel to duplicate entries or events. System will assure that if a data element is modified on a master record is modified on a master record in the system, the change will be recorded in all modules or locations of that record within the system. The user interface shall be a Graphical User Interface (GUI) and utilize menus, shortcuts and function keys. System will provide input flexibility and multiple methods using mouse, keyboard or function keys (or any combination) for RMS entry. System will allow screen configurations to be user designed and defined and locked as a default if so desired. System will have consistent design and use of controls, functions keys, etc. to reduce user training and system administration. System will provide data validation at the field level to detect incorrect entries and incomplete forms prior to finalization of a record. System will provide data validation for all required State and Federal interfaces before record submittal. System will allow post-validation edits to a saved record versus re-entry of the record. System will return the cursor to the first position of an incorrect or incomplete entry and provide an explanation of the error. The system will then consecutively step through any additional errors or incomplete fields. If a field has defaulted or pre-defined values, the user shall be able to choose from only those defined values. The system will require user to log on using an employee number or user ID and unique password. The system should also allow for biometric log on capabilities. Fully Compliant Modification/Custom Software Not available Comments System will allow an Administrator the ability to assign identification, sign-on, passwords and privileges based on individual user, group of users or both. The system should be configured so as to allow multiple user logons at multiple 19 workstations. Records Management System The system will allow for user definable permissions including, but not limited to, view only, 20 change/update, reporting, non-viewable confidential, etc. System will allow Administrator to set parameters for display or non-display of restricted 21 information or fields. System must support multiple open windows and interfaces running actively and 22 simultaneously with the RMS program as well as all other standard Windows based features. Any text area within the system should be of unlimited length and have standard word 23 processing capabilities including, but not limited to, text editing, spell check, word swap, cut/copy/paste, find and replace, document formatting and screen print. 24 System will allow for user definable code tables throughout the RMS. If a drop down code table is utilized, the system will allow depressing enter key at a chosen 25 position and the field will be autofilled. System will always display cursor at the first entry position of screen on any new screen. 26 System will maintain a logical flow and appropriate input screens depending on entry type. 27 Only those screens and fields required for a particular entry type will be presented to reduce tabbing and redundant screen maneuvering. 28 System will provide text-sensitive on line and editable help screens. System will allow a systematic backup and archival process that does not impede records 29 entry operations. System must have the ability to acces other network resources while active in RMS and 30 without interrupting or halting RMS processes. In the event of screen configuration or code tables changes, system will have the ability to 31 easily and automatically download at next user log on. System will allow Administrator to perform training duties without effecting RMS records or 32 historic information. 33 System will allow multiple users to access or edit any one record at any given time. The RMS record will begin at the time event is received by CAD or mobile and will have a 34 unique event number assigned at that time. All location addresses in geomaster file will be verified and standardized using initial 35 validation from CAD. Any name or location entered into the RMS system will be validated against a single master 36 and attached at time of initial RMS entry. RMS will serve as the central repository for all information and shall be the standard when 37 data discrepancies occur. System will use the event number as the primary link to all RMS applications and record 38 areas. System will interface and/or link with all applicable State, Federal and local systems and 39 accept mandatory required parameters, including, but not limited to: NCIC/III Fully Compliant Modification/Custom Software Not available Comments Records Management System State CJIS / CJRS CIBRS / NIBRS Minnesota MOC MN Department of Vehicle Services (DVS) State BCA Laboratory Hennepin County (TIGER) Case Transmittal Hennepin County (JNET) Juvenile Transmittal Hennepin County Warrants HennRap (Hennepin Repository of Arrest Photos) Indentix Fingerprint System MRAP (Minnesota Repository of Arrest Photos) Statewide Supervision System (S3) 40 System will guarantee that various industry standard file structures can be easily imported and exported for use both within the RMS and for outside agency mandates as required. 41 System will allow multiple ways to query criteria of events to decide if additional data updates or modifications are necessary. 42 If any data element is changed in one area of RMS, system will be updated and changed in all areas of RMS. 43 All event records will be a part of the RMS regardless of diposition status including, but not limited to, cancelled events, events not assigned, events referred from or to other agencies, etc. 44 System must have the ability to select records to archive or purge based on multiple criteria including, but not limited to, event number or range, date or range of dates, event types, etc. 40 M 41 System will allow a designation between names of individuals and names of businesses. 42 System will allow entry of names with minimum elements of first and last name. System will allow name validation lookup utilizing soundex and with minimum of one 43 alphabetic character to initiate search. System will have date of birth and other parameters compliant with State and National 44 configuration requirements. (i.e., MMDDYYYY) System will accept names into master name file by multiple methods including, but not 45 limited to, manual data entry, mag or card swipe, etc. 46 System will allow for user configurable name types and involvement types. System will have a means to audit names and generate report for consolidation and allow 47 end user to consolidate one or multiple names in a single process. 48 System will have capability to record personal information including, but not limited to: Last Name First Name Middle Name Fully Compliant Modification/Custom Software Not available Comments Records Management System Date of Birth Street Address County/City State Zip Residence Phone Business Phone Alternate Phone Sex Race Ethnicity Citizenry Height Weight Eye Color Hair Color Social Security Number Driver License Number Driver License State Driver License Type State ID Number Federal ID Number Fingerprint Number Scars, Marks, Tattoos Arrest History Event History Case History Citation History Field Contact History Photos Warrants Aliases and Nicknames Gang Affiliations (State Defined per Statute) Known Associates Address History School History Employment History Relationship Information (Parents, etc.) Narrative System will automatically and dynamically track and calculate age and adult or juvenile 49 status on all name entries containing date of birth. Fully Compliant Modification/Custom Software Not available Comments Records Management System System will display age and age status (juvenile or adult) on initial screen for any name 50 queried in the master file. System will allow manual entry of juvenile or adult status to any record in master file with or 51 without recorded date of birth. Vehicle System will allow automatic population of any field within RMS that is being returned from a 52 State or National vehicle query. When entering information manually, system will audit all entries to ensure correct number of 53 characters in VIN, etc. and validate against all vehicles entered in internal database. System will allow vehicle make and model categories to be easily upgraded to NCIC standards and have those codes available to all users at first sign on after upgrade. System will allow for user definability of vehicle involvement codes to include, but not limited 55 to, accidents, citations and forfeiture tracking. System will allow user definability of relationships to vehicle to include, but not limited to, 56 owner, driver, passenger, etc. 57 System will have the capability to record vehicle information including, but not limited to: Vehicle Make Vehicle Model Vehicle Year Vehicle Identification (VIN) Vehicle Style Vehicle Type Vehicle Color Vehicle Features Vehicle Involvement Vehicle Status Vehicle Disposition Vehicle Value Vehicle Damage Vehicle Realtionship(s) Vehicle Registered Owner (See Names) License Plate Number License State License / Registration Year Vehicle Stolen / Recovered Location Vehicle Owner Notification Vehicle Forfeiture Information 54 Fully Compliant Modification/Custom Software Not available Comments Records Management System Location System will allow automatic population of initial event record with validated address from 58 CAD or moblie. Any subsequent address entry will automatically validate against geo-based master location 59 file if address is in local jurisdiction. 60 System will have the ability to record location information including, but not limited to: Street Number Street Name Street Type Street Direction Suite or Apartment Number County/City State Zip Location Name Cross Street or Intersection Cross Street / Inversection Type Location Type Occupancy Date Property ID (PIN) Number Lat / Long Coordinates Arrest User must be able to utilize information from CAD event and/or RMS to initiate the arrest 61 record with a minimal amount of duplication of effort. (3-4 keystrokes) Arrest application should have the capability for multiple charging and varying dispostitions 62 per charge. System must be interfaced and allow for all information entered during the booking process to populate arrest fields including, but not limited to, all arrestee personal identifiers and 63 information, charge(s) at time of arrest, disposition of arrestee, fingerprint and photo information. 64 System must allow for user-definable searchable fields for agency specific information. 65 System must allow clearance of multiple events with a single process. 66 System will have the ability to record arrest information including, but not limited to: Arresting Agency (ORI) Arresting Officer Arrest / Booking Number Arrest Date Arrest Type Arrest Code (UCR / MOC) State Statute Arrest Offense Level Fully Compliant Modification/Custom Software Not available Comments 67 68 Records Management System Arrest Disposition Hold Date and Time Release Date and Time Release To / Transfer Information Release Reason Reason Held Custody Risk County of Jurisdiction Warrant Information Mandated Welfare Status Checks System will have the ability to audit entries before submittal for accuracy and completeness. Fully Compliant Modification/Custom Software Not available Comments System will have the ability to interface and automatically transfer arrest records including, but not limited to: CriMNet (State) State Probation and Parole (S3) Department of Public Safety Fingerprinting Driver License Revocations Intoxilyzer Results Minnesota Court Information System "MNCIS" [Odyssey] Juvenile When there are individual involvements of juveniles, system will comply with requirements 69 stated in Section 3.0 Master File Name, with special notation to Subsection R.3.1.2 and R.3.1.3. System must provide that a juvenile record designation remains a juvenile record historically 70 regardless of age. 71 System must maintain juvenile records seperately from adult master file database. 72 System must allow security level that can restrict access to information on juveniles. System will have ability to easlily or automatically redact information from juvenile reports 73 when release of public information is required. System will allow user definable fields if they do not exist for entry of agency mandated data 74 to include, but not limited to: parent information, school information, diversion programs, number of times diversion used, school notifications, etc. System will allow designation of drug, alcohol, or other illegal substance involvement per 75 each juvenile event and will provide for that information to be summarized. 76 System must allow for a juvenile designation even if a date of birth is not available. System will provide juvenile designation in such a manner that it is immediately apparent 77 upon viewing a record. (See Section R.3.1, Master File, Name, Subsection R.3.1.20, R.3.1.21 and R.3.22). System will provide a means to search for in-custody individuals by adult or juvenile status. 78 Records Management System Crime Analysis Capabilities System will have the ability to provide basic crime analysis based on raw data including, but 79 not limited to: Activity Type (UCR, MOC or NIBRS based) Activity Type (User Defined) Time of Day Day of Week Combination Time of Day / Day of Week Date Range Address Range of Addresses Method of Operation Comparisons Time Comparisons (i.e., Year / Year) Level of Crime Case Clearance by Type Case Status by Type Frequency of Criminal Activity by Type Property Types Property Values Gang or Other Affiliations 80 System wil have the ability to pin map any analysis run on selected criteria. Inquiries and Reports System will have the capability to query on any field or combination of fields entered into the 81 system. System will have the ability to produce alarm invoicing based on alarm counts per year and 82 using sliding fee scale. Data Recall & Query System will have the ability to query on any field (or multiple of fields) and for any data set 83 that has been entered into the system, including narratives. System will have the flexability to search information in a number of ways including, but not 84 limited to: Equal values Greater than, greater than or equal to Less than, less than or equal to Range of values Averages Counts Sums Wild card entries Soundex 85 System will have the ability to search and print information in the form of summary data. Fully Compliant Modification/Custom Software Not available Comments 86 87 88 89 90 91 92 93 94 95 96 Records Management System System will have the ability to show number of records searched and number of records returned. System will have the ability to limit the number of records searched through user prompts and filters. System will have the ability to save and/or archive searches or queries for future use by compiler or others with appropriate access. System will have the ability to conduct basic queries to include all master files (names, locations, vehicles) while in any area or module of the system. System will allow for the ability to run a query interactively or to schedule the query for nonpeak usage times. System will provide adequate processing capabilities for priority queries and searches run during normal peak business hours. System will provide adequate interface to allow the capability to serach all system records, files and modules using one search process. System will provide for extraction of search results into multiple Windows based industry standard formats including, but not limited to, Word, Excel, Access, PowerPoint, Mail Merge, etc. System will provide ability to query from any CAD, Records or Mobile application. System willh ave the ability to query not only user supplied data items, but also on returns from outside agencies, etc. (i.e., license plate returns, driver registration information, etc.) System will provide multiple methods to initiate a query or search including but not limited to: Fully Compliant Modification/Custom Software Not available Comments Allowing a user to choose fields, define the sort order and apply filters for records displayed. Allowing a user to filter the records displayed in a list. Allowing the user to search for a record based on information in a single field. 97 System must provide some method of displaying search results in a browseable list. System must provide the ability to additionally subset a completed search and re-search the 98 subset. Online & Printed Reports System will provide a non-technical, easy way for any user to run a report or create an ad 99 hoc report. System must allow any query to be recorded into a reporting format and allow for use of a 100 graphics editor to create line, bar, pie charts, etc. 101 System must provide for some type of "ad hoc" reporting using English-like commands. System must allow flexibilty of user defined report appearance including, but not limited to: 102 Page Headings Column Headings Column Widths 103 104 105 106 107 108 Records Management System Page Numbering Sorting within a report Totaling and Sub-Totaling Variable font, margins, lines per page, page width Print to screen, print to printer, or both System must allow option of printing statistical data or totals only System will have the ability to save reports for future use by compiler or others with appropriate access. System will provide for exporting of report into multiple Windows based industry standard formats including, but not limited to, Word Excel, Access, PowerPoint, Mail Merge, etc. System will support comparative arguments including, but not limited to: Include Exclude And Or Equal to Greater than, greater than or equal to Less than, less than or equal to Range of values System will have the capability to support the comparative arguments for both alpha and numberic values. System will allow selection by multiple values for a field or matching fields from multiple files. Fully Compliant Modification/Custom Software Not available Comments 109 System will have the ability to merge reports. System will have ability to schedule report generation by day, day and time, day of week or 110 intervals. System will have a simple means for a use to cancel a report at any time i.e., to save or 111 better allocate resources, due to errors in field input in report request, etc. System must allow reports to be saved in common file formats that can be easily read on 112 most PC's. System must support standard SQL report writing software (i.e., Crystal Reports, Access, 113 ASP.Net etc.) System must provide a number of standard generic reports that might be used by any 114 agency (i.e., daily activity report). 115 System should have the ability to generate reports based on, but not limited to: Part 1 Crimes Part 2 Crimes Non-Criminal Activities Audit reports for State entries System will provide a non-technical, easy way for any user to run a report or create an ad 116 hoc report. Records Management System State & Other Mandatory Reporting System must support reporting to the National Incident Based Reporting System standards. 117 System must support reporting to the State CJIS and CJRS systems by use of MOC (Minnesota Offence Codes). System must support reporting to the State using IBRS (Incident Based Reporting) 119 standards. System must provide an open architecture allowing for reporting to any State or National 120 agency as may be required in the future. 121 (See "Interface" section) Record Control & Distribution System will have a user-defined ability to make automatic notifications based on change or 122 entry of data criteria including, but not limited to: Notify Based on Case Type Notify Based on Case Status Notify Based on Juvenile Involvement Notify Based on Task Force Involvement Notify Based on Public versus Non-Public Notify Based on External Mandatory Reporting Notify Based on Sealed Record 123 System should have the user defined ability to set parameters for victim notifications. System should have a means of document tracking any release of report to any outside 124 agency or others. Traffic and Citation Management Accidents System must allow for MN State accident reports to be written and drawn using the DVS web 125 site electronic forms and automatically downloaded into the Sheriff's Office. System must provide that all information collected including, but not limited to, persons, 126 vehicles, will be auto-populated into the RMS. System will allow integration of accident scene photos and accident reconstruction drawings 127 to be attached to an event. System will have the capability to capture DL photo and driver information and automatically 128 populate appropriate fields in the Sheriff's Office. System will have the capability to allow any part of an accident report to be done manually 129 and then added to previously electronically submitted data (i.e., add diagramming later, etc.) 118 System will allow for change in diagrams and will provide an audit trail of any changes or edits. System will have the capability to do lookups against the Master Name and Master Vehicle 131 files for previously entered individuals and vehicles. 130 Fully Compliant Modification/Custom Software Not available Comments Records Management System System willh ave the capability to capture information at a squad level and populate all 132 necessary information into RMS. System will support use of all captured information for use in statistical reports including, but 133 not limited to, frequency of location, vehicle types, seat belt usage, injuries, type of roadway, causes, alcohol or substance involvement, use of helmets, etc. System will be able to provide data for traffic management purposes including integration for 134 pin mapping. System will be able to provide data for traffic management purposes including integration for 135 pin mapping. Impounds and Towing System will have the ability to track tows, impounds, vehicle forfeitures, and repossessions. 136 System will allow a date and/or time notification to be set for impounds for forfeiture, impounds held as evidence, etc. 138 System will provide audit trail of impounds, notification of owners and dispositions. Impounds and tows will be integrated into the Vehicle Master for query and reporting 139 capabilities. Citations and Warnings System must provide the capability of capturing citation information using either a remote 140 field unit or an internal LAN PC. System will be integrated and perform a lookup in both Master Name and Master Vehicle 141 files to eliminate redundant entry. System will allow user to overwrite / update current master name or vehicle information and 142 system will attach new information as most recent. 143 System will allow for multiple offense charges on one single citiation. 137 144 145 146 System will allow for entry of multiple officers / badge numbers to a single citation record and denote primary and secondary assignment. System will allow entry of officer field notes but will provide a means to redact those notes from offender or public copies. System will allow a method of "copy over" for multiple citations written simultaneously to a single offender. This function should copy over all but additional charge information to eliminate redundancy. System will allow for integration of bar code, card swipe or other technology for gathering driver information and automatically transmit and populate citation fields in the RMS module and transmit citation data to State Court System. System will allow for issuance and printing of a citation from a remote unit. System will allow for information that is returned from a MN DL record inquiry to automatically populate the citation fields. Sytem will allow the driver license photo to be attached to the citation record. System will provide the ability to enter, track and audit all court assignments and dispositions with regard to a citation. Fully Compliant Modification/Custom Software Not available Comments 147 148 149 150 151 Records Management System System will allow for multiple types of citation to be created (i.e.; written, verbal, 152 administrative) System will allow entry to warnings that do not have an identifying number. System will allow 153 attachment to an individual or a vehicle. Fully Compliant Modification/Custom Software Not available Comments Equipment Tracking 1 The module must have the ability to document all department equipment. 2 The Equipment Tracking module must assign: Equipment by personnel. Equipment to station. Equipment to vehicle. 3 The module must have the ability to capture cost of equipment. 4 The software must capture purchase date. 5 The software must capture where equipment was purchased. 6 The module must have the ability to schedule replacement date. 7 The module must update personnel jackets with issued equipment. 8 The ability to search all department equipment from CAD is required. 9 Agency-defined maintenance by equipment type is required. The software must have the ability to schedule equipment for department-specific 10 maintenance. 11 The ability create department specific equipment categories is required. 12 The module must have the ability to define type by categories. 13 The module must have the ability to link to department- specific inventory number. 14 The module must have the ability to capture and report by equipment serial number. 15 The module must have the ability to create department -specific activity (maintenance). 16 The software must have the ability to schedule department activity. 17 The module must track the following: All maintenance and costs Equipment condition when assigned. Equipment condition when returned. Original cost. Department cost. Complete equipment history Fully Compliant Modification/Custom Software Not available Comments Field Investigations The module must seamlessly work with the field investigation feature in the base RMS package. The module must provide immediate and quick access to all information about 2 investigations. Authorized users must be able to access prior NCIC records and available state databases 3 to associate information. 1 4 The module must be able to link or group all known associates at a given criminal location. The module must track and maintain information sources, such as rumors, confidential informants and first-hand accounts from a law enforcement officer. The module must have a grading system available so law enforcement can grade the 6 credibility of each source. 5 Fully Compliant Modification/Custom Software Not available Comments Gang Tracking 1 The module must maintain and track critical information about gangs and members: Vehicles Weapons M.O. Personal Information Known Aliases Gang Name Gang Type Associated Location(s) 2 The module must allow a user to search for information using the gang name. When a location is entered into the system, the module must alert the user if it is a known 3 gang location. When a person is entered into the system, the module must alert the user if he/she is a know 4 gang member. When a vehicle is entered into the system, the module must alert the user if it is associated 5 to a gang/gang member. 6 The module must allow multiple vehicles to be associated with a gang/gang member. The module must allow multiple contact numbers to be associated with a gang/gang 7 member. 8 The module must allow multiple MOs to be associated with a gang/gang member. 9 The module must allow multiple weapons to be associated with a gang/gang member. 10 The module must support multiple activity records to be associated to a gang/gang member. 11 The module must require date, time, code and type to create an activity record. Fully Compliant Modification/Custom Software Not available Comments Gun Permits and Registrations 1 The gun permit application must track the details of an issued permit, including: Permit Holder Permit Type Permit Status Permit Issue Date Permit Expiration Date 2 The gun registration application must track the details of an issued registration, including: Registration Holder Registration Type Registration Status Registration Issue Date Registration Expiration Date Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Narcotics Management The module must have the ability to create agency defined investigation type. The module must have the ability to create agency defined status. The software is required to tie to location. The software is required to tie to vehicle. The software is required to tie to person or persons. The software must have the ability to create and manage own investigation numbering system. The module must manage assignments within the investigation. The module must document all activity within the investigation. The module must tie to department-defined intelligence information. The module must provide full access to subjects jacket and department history. The module must provided full access to vehicles jacket and department history. The module must provide full access to location history. The module must tie and document all confidential informants activity to investigation. The module must track all pending charges that could stem from investigation. The module is required to track all buys within investigation. The module is required to track all monies used in buy. The software must document all laboratory results tied to agency-defined buys.. The software is required to document all confidential informants. The software must track all monies paid to confidential informants. The module must have access to all captured information on confidential informants from master name index. The module must have the ability to document current confidential informant status. The module must track and document confidential informant reliability. The module must track all department specified funds and transactions. The module is required to provide a complete audit trail of funds. Fully Compliant Modification/Custom Software Not available Comments 25 The software must provide the ability to create department-specific intelligence database. 26 The module must tie intelligence to the following: Person Location Vehicle Ensuing investigation 27 The module must provide full department-defined security . 28 The module must provide the ability to lock down information. 29 The module must provide the ability to share department- specific and designed information. 30 The module must provide the ability to create department- specific reports on any captured table/data field. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Orders of Protection The module must provide agency-defined types. The module must track conditions/terms. The module must automatically create system wide alerts. The software must provide the ability to tie to location. The software must provide the ability to attach to subject. The module must be integrated with CAD, Corrections, and Mobile. The software must provide the ability to access the department history of the parties involved from the master name index. The module must provide the ability to set expiration dates. Access state/NCIC information from individual jackets is required. The module is required to associate with department case number. The module is required to associate with courts case number. The software must provide the ability to document issuing judge. The software must track the date served. The module must provide the ability to create department-specific reports on any captured table/data field. Fully Compliant Modification/Custom Software Not available Comments Pawn Shops 1 The module must support a listing of all pawn shops in individual master name files. 2 The module must track the following information within an agency-defined area: All Pawn Shop Sales Associated Owner Customer information The module must seamlessly trail pawn shop transactions and simultaneously check the 3 stolen property data list in the RMS to improve the chances of recovering stolen goods. Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 9 10 11 Property Room System will allow upgradeable tables based on manditory fields required by NCIC and State agencies. System will provide complete audit trail and ability to track any movement or change in status for any piece of property or evidence. System will provide automatic validation against all internal and external databases based upon entry of certain unique identifiers. Utilizing the validation above, system will provide a means to match stolen property with recovered property. System will alert entry personnel if like property is found based on serial number, make and model, etc., or a combination of identifiers. System will provide for every piece of property or evidence a complete tracking of chain of custody / property movement to include, but not limited to: Date and Time of Receipt Person Receiving Date and Time of Release Person Releasing Reason for Release Date and Time Returned or other Disposition System must allow entry and updating of property to an event or case file by either in-house or mobile personnel. System must also interface property records with agency master name, master location, and master vehicle datatbases and allow user to view, add, delete and/or edit. System must allow entry of the following information, including but not limited to: Event number Event Sequence Number (or autosequencing). Activity Code Property Record Type Property Type Released To Released From Property Make Property Model Property Size Property Color Property Serial, License or Unique Identifier Property Year Quantity Value Dates (Stolen, Recovered, Flagged, Transferred) Property Inventoried Location System will provide a means to easily replicate entries, if desired, when only minimal information changes (i.e. same property with different serial numbers only). System will automatically calculate total values, weights, etc. if multiple like items are listed in one property record. Fully Compliant Modification/Custom Software Not available Comments 12 Property Room System wil assure that all property objects can be queried by criteria including, but not limited to: Property Type Property Make Property Model Property Serial / Unique Identifier Date and Times Event Number Case File Number Location Bin / Tag Number Citation Number Property Status Person / Agency Holding Narrative Fully Compliant Modification/Custom Software Not available Comments 13 System will provide the capability to enter property record types including, but not limited to: Stolen Property Stolen and Recovered Property Recovered Property Lost Property Damaged Property Evidentiary Property Property for Safekeeping Found Property System will have some means of notifying property clerk/manager if property disposition is changed (i.e. ready to release, etc.) System will have some means of automatically calculating days property held and notifying property clerk/manager if overdue or ready for disposition. System will allow user-definable status changes and reasons for release, etc. System will be capable of obtaining and archiving electronic signatures. System will integrate with bar coding hardware and software. System will integrate with State and Federal systems including, but not limited to, State CJRS and CRIS, NCIC, etc. 14 15 16 17 18 19 State/NCIC Interface The CAD software must provide a link to the State/NCIC network to run license plate and warrant checks. The CAD software must provide a link to the State/NCIC network to automatically attach a 2 CAD inquiry to the incident/call database. The interface must have the capability for a single query to be directed to the State/NCIC, 3 the local database or both. 4 The State/NCIC interface must provide user-defined format screens. 1 5 The Interface must log all transactions into a history file for viewing and reporting purposes. 6 7 8 9 10 11 The Interface must provide or support an online interface from the CAD application to the State/NCIC database. The interface must provide access to NCIC forms within CAD. The interface must provide access to NCIC history within CAD. The software must allow authorized users to setup automatic transmission of license plate or driver license information based on CFS type. All automatic transmissions that are attached to a CFS must be logged on the call and be easily accessed. All responses that can be matched to the original transmission and is attached to a CFS will be logged on the call in the same area as the transmissions. Fully Compliant Modification/Custom Software Not available Comments Vehicle Tracking 1 The module must have the ability to track vehicles by dept. specific type. The module must have the ability to track department vehicles by deptartment issued unit 2 number. 3 The software must tie the vehicle to inventory number. 4 The module must have the ability to place the vehicle in service or take unit out of service. 5 6 7 8 9 10 The module must track the make of the vehicle. The module must tie the model to the make. The software must track the year of the vehicle. The software must track the VIN. The module must have the ability to assign vehicle. The module must track the following: Purchase price of vehicle Where vehicle was purchased Delivery date of vehicle In service date of vehicle In/out of service history Vehicle dimensions Fuel type Tire size and pressure Turn radius Maximum altitude Maximum operational grade Engine manufacturer Engine size Fuel tank size Transmission type Water tank size The module must have the ability to create department specific activity. The module must be able to schedule vehicle for all maintenance. The module must track all maintenance completed on vehicle The module must track vendor completing maintenance. The module must track costs of maintenance. The software must be capable of printing reports of vehicle history. The software must be capable of printing reports on all department vehicles. The module is required to create department-specific reports on any captured table/data field. Fully Compliant Modification/Custom Software Not available Comments 11 12 13 14 15 16 17 18 1 2 3 4 5 Public Safety Lineups/Mug Shots The module must support front and side view pictures of a person which are imported into the system and attached to the appropriate master name file. The system must support the use of mug shots in the following fashions: Electronic Lines-Ups Wrist Bands ID Badges Booking Cards The system must allow an authorized user to define specific criteria to create a digital lineup. The system must automatically display a minimum of six photos at a time meeting the criteria specified, saving the time of sifting through files. The system must provide an easy method of replacing a photo within the line-up. Fully Compliant Modification/Custom Software Not available Comments 6 The system must provide an easy method of viewing statistics on a person within the line-up. 7 The system must support a minimum of two methods of capturing photos. Digital Imaging The module must allow scanned documents or photos to be imported into RMS. The module must link electronic files to the master file of a person, property or case. Only authorized personnel can access electronic files. The module must support .jpeg (joint photographic expert group) files. The system must support multiple documents in one file. The system must allow the following documents to be scanned and imported into the 6 system: Crime Scene Fire Scene Case Notes Diagrams Personal Items Property Room Tags Fire Pre-Plans 1 2 3 4 5 Fully Compliant Modification/Custom Software Not available Comments Mobile Computing General System must interface to and allow flexibility of various types of mobile hardware including, 1 but not limited to, tablets, modular mobiles, fixed Mobile Data Computer, portable laptop, PDA, Pager, etc. System must be capable of interfacing to LAN or WAN and any type of wireless 2 communication including, but not limited to: CDMA GPRS 800 MHz EVDO 1, 2, 3, 4G, etc. System will be capable of multi-protocol support and assure that all protocols can be 3 combined into a seamless network. System will allow for future voice response input and text to speech output as well as multi4 media file formats. The user interface shall be a Graphical User Interface (GUI) and utilize menus, shortcuts, 5 and function keys. System must be designed or have user configurability for task buttons and font size for 6 readability and ease of use for the conditions of the mobile environment. System will allow integration with standard Microsoft Windows program applications and 7 allow those applications to be run on the same hardware as (and in conjunction with) the Sheriff's Office, fire or EMS applications. System will allow multiple forms of navigation including, but not limited to, touch screen, 8 mouse, function key, programmed key, icon, tabbing, etc. 9 System will allow prompted user-defined tables, screens and forms. 10 The system will provide text-sensitive on line and editable help screens. System will allow updates to all user defined tables, etc. to be dynamically downloaded at 11 next mobile logon subsequent to system update. System will allow, within any field that has a drop down table or for fields validating against a 12 master file, the ability to type in a single or a string of characters and immediately place cursor at that alphabetic location within the table. The system will require user to log on using an employee number or user ID and password. 13 The system should also allow for future biometric log on capabilities. 14 System will allow remote log on for support and maintenance. System will allow mobile application to be run from a personal computer in a LAN 15 environment for training, screen modifications, etc. System will allow system administration in the mobile environment either for an individual 16 unit or by mobile groups. System will allow flexibility of screen preferences in the mobile environment with a simple 17 method to return to defaulted preferences. System will make available all unread messages and responses at the time of individual's or 18 unit's next log on. 19 System will allow dispatchers to log mobiles on and off the system from CAD. System will perform a validation that will not allow multiple or duplicate log on for a single 20 device. Fully Compliant Modification/Custom Software Not available Comments 21 22 23 24 25 26 27 Mobile Computing System will provide a means to access, withough overtaxing bandwidths, commonly used data, including but not limited to: Minnesota State Statutes Local Ordinances and Code Department Manual Agency Personnel Lists Roll Call Informational Data Floor Plans System will provide both a visual and audible notification of any incoming traffic including, but not limited to, dispatches, dispatch updates, messages, returns, etc. System will automatically force the display of any dispatch or dispatch update to over-display anything currently on the mobile screen. System will allow dispatch information to dynamically display withough loss of information or placement in current program or without leaving current program to access and view the dispatch. System must provide a means to designate message types or message priorities. System must allow agency to define what events and processes within mobile application receive audio and visual alerts. System will provide a mechanism for both mobile user and CAD dispatcher to verify transmission and receipt of any type of comminication message. Fully Compliant Modification/Custom Software Not available Comments 28 System will allow for notification if transmission of a queued message does not complete. System will allow for multiple persons to be assigned to a unit and provide a means to manage all messaging, etc. going to an individual assigned to a shared unit. System will allow for user defined Internet access by individual user or groups to include full 30 access or limited access via proxy server. System must allow for bandwidth prioritization for emergency communications versus 31 standard messaging. System must have an open architecture to allow future expansion using third party 32 components. 33 System must allow for user definable toolbars. System must provide an officer emergency key which can be activated in a surreptitious 34 manner but cannot easily be activated in error. This emergency key will notify dispatchers and any other mobile units of officer/unit number and location at a minimum. System must work in conjunction with global positioning system (GPS) providing latitude, 35 longitude, speed and direction of travel. System will also support automatic vehicle location (AVL) through the GPS facility to allow 36 vehicle tracking. System will have a way to notify mobile user that additional information is available if it is not 37 totally presentable on one mobile screen. Dispatch Receipt System will provide for mobile communications using any of several means of wireless 38 topology. System will provide for display of all event information available at dispatch to the mobile unit 39 in a GUI, user-friendly format. 29 40 41 42 43 44 45 46 47 48 49 50 51 52 53 Mobile Computing System will assure that all dispatches to a mobile unit are forced or overlaid to the mobile screen no matter what program is currently in use by a mobile unit. System will dynamically display all updates to an event modified in CAD without requiring mobile user intervention. System will provide updates to an event in such a manner that mobile user does not have to scroll, page up, page down, or in any other manner intervene in order to recognize or receive the update. System will provide mobile user a method to perform simple functions, such as status change, acknowledgements, etc. with one keystroke, function key or programmed key. System will provide a means to automatically and dynamically provide the mobile unit with all histories, alerts, etc., that are provided to CAD at the time of location validation when the event is sent to the mobile unit. System will provide a means to run queries to interfaces via several methods including, but not limited to, card or magnetic swiping or manual entry. System will automatically query all local databases (RMS master location, name, etc.) when information is entered by the mobile unit. System will provide a means to run multiple queries simultaneously via single entry of name and DOB, license plate or license number including, but not limited to: Plate: MN Vehicle Registration Plate: MN Vehicle Clear Check Plate: MN DL on Registered Owner & 2nd RO Plate: MN Clear Check on RO & 2nd RO Plate: NCIC Clear Check on RO & 2nd RO Name or DL: MN DL on RO & 2nd RO Name or DL: MN Clear Check on RO & 2nd RO Name or DL: NCIC Clear Check on RO & 2nd RO System must have the ability to view all units presentlly signed into the system to include CAD terminals. System must have the ability to view all events either active or pending. System must have the ability to view and transmit photo images. System must have the ability to close out and dispose of an event utilizing user defined drop down options (including EMS information such as hospital transport location) and narrative text. System will automatically make a unit available upon final disposition of an event. System will allow for duplicate user defined receipt of all mobile communications to a supervisory mobile or terminal. Fully Compliant Modification/Custom Software Not available Comments 54 System must display the following data fields to the mobile unit including, but not limited to: Event number Event Date and Time Event Primary Location Event Revised Location Caller Name Caller Address Mobile Computing Caller Phone Received Date and Time Lat/Long Coordinates Event Type Event Priority Call Source Call Comments and Free Form Text Field Closest Intersection Event Disposition System must allow dispatcher ability to easily and directly transmit information directly from 55 CAD to mobile unit without editing, cutting, pasting, etc. System must allow for mobile unit to self-initiate an event and assign a case or event 56 number from the mobile unit that is within the sequential number used in CAD. 57 System will provide location validation against the master file for mobile self-inititated events. 58 System must allow mobile unit to override a validated location if desired. 59 System will provde an audit trail of all changes made to an event from a mobile unit. Mobile Data Searches External - National/State/County System must provide the capability to search non-agency databases without leaving mobile 60 aplication or initiating separate sessions, etc. 61 System must also allow query returns to be viewed without leaving mobile application. System must have the ability to search State and National databases including, but not 62 limited to: MNCIS State Database (CrimMNet) NCIC DVS (Department of Vehicle Services) MRAP (MN Repository of Arrest Photos) AFIS or Fingerprint Database Courts Federal, State, or County Warrants System must have the ability to search State and National databases for information on 63 persons, vehicles, or articles. System must have the ability to run multiple plates simultaneously and group the returns per 64 individual plate. 65 System must allow for easy viewing of multi-lined or paged returns to the mobile user. 66 System will archive all query returns for a user defined time limit at the mobile level. Internal - Agency RMS System will allow mobile search of all CAD and RMS events by multiple criteria to include, 67 but not limited to: Name (Partial or Full) Address or other Location Address Range Event Number Fully Compliant Modification/Custom Software Not available Comments Mobile Computing Date and/or Time of Event Event Type Plate Number Badge and/or Unit Number Disposition Code Query results presented to mobile user will be displayed chronologically beginning with the 68 most recent. Queries and searches will access the entire RMS database to include, but not limited to, 69 location master, name master, property module, citations, accidents, etc. System will allow access to other inter-department data to include, but not limited to (vendor 70 to define): Agency Personnel Lists Mobile Phone or Pager Numbers County/City Codes and Ordinances Alarm Vendor Data State Contacts and Numbers Federal Contacts and Numbers Outside SHERIFF'S OFFICE / POLICE Agencies Mutual Aid Contacts and Numbers Call Out Rosters Roll Call Updates Emergency Response Teams Narcotics, Gang or Specialized Units All searches should be printable either in the car or to the station. Both locations are 71 preferred. Citations System must allow for manual input, input from a bar code or magnetic stripe reader, and/or 72 State interface return to auto-populate the appropriate fields of the citation form as obtained from the driver license. System should allow for prompted drop down listings of State Statutes and County/City 73 Code/Ordinances with literal descriptions. System should automatically transmit all information from the citation as created in the 74 mobile unit into the RMS system. RMS module must have the ability to void the citation if necessary. System should automatically validate against the Master Name, Vehicle and Location files 75 before creation of a new record. 76 System should allow for printing of multiple copies of the citation at the mobile level. System should allow for differential of agency copy of citation versus defendant copy to 77 redact officer notes, etc. 78 System should allow mobile user the option to create an event number or to decline. System should allow for automatic electronic transmittal of the citation to the Hennepin 79 County Court without further user intervention or entry procedures. System will have same information and collectible data fields in mobile application as in 80 RMS. Alarms Fully Compliant Modification/Custom Software Not available Comments 81 82 83 84 Mobile Computing System will allow for an alarm card to be completed at the mobile level and will automatically forward all data to RMS. System will allow for a validation against the Master Name and Location files and autopopulate information from those files to include alarm company. System will allow integration with a field printer so that alarm notifications can be printed and left at the scene. System will allow for mobile user to designate either as chargeable or non-chargeable alarm. Fully Compliant Modification/Custom Software Not available Comments Field Contacts / Warnings System will allow for user definable contact types and reasons and will allow queries against 85 the data. 86 System will automatically attach contacts and warnings to the Master Name file. 87 System will allow field contact information for both individuals and vehicles. 88 System will allow use of a magnetic stripe or card reader and in squad printing capabilities. Equipment and Peripheral Integration System will integrate peripherals, including but not limited to thermal printers, optical and/or magnetic swipes, digital media, fingerprint security sign-on, handheld units (citation writers, 89 PDA units, etc.). (NOTE: Handheld and/or portable units are necessary for motorcycle, bicycle, parking enforcement and other non-squad activities.) Magnetic/Bar Code Reader 90 System will, upon scanning a driver's license from MN, understand the information on the license and transfer it to the appropriate form. 91 The system will support industry standard magnetic stripe and barcode readers. Digital Photo Integration The system will support the insertion of digital photos through a media card input port, CD or 92 other storage device. Printer 93 Two (2) printers will be needed for in-squad printing with one being a thermal printer. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Field-Based Reporting System must provide autofill of all data fields that have been previously supplied by CAD or the mobile user. System must provide logical flow and entry for any type of field report. User should not be required to navigate between many screens or open and close modules to complete a report. System must have user definable screens and data fields with option to disallow any fields Sherburne County Sheriff's Office chooses not to use. System must allow user definable drop down tables for entry of data fields. Field Reporting must be totally integrated to RMS and allow entry of reports including, but not limited to: Incident Report Arrest Report Property / Evidence Report Citation Field Interview or Contact Accident Reports or Info Exchange Tow Reports Residential or Business Alarms Standardized Department Templates and Forms Narrative Supplements System must download information captured in CAD or through a query or card swipe, etc. into appropriate fields in field report. System will allow user to override any captured information that has been autofilled into report fields. System will allow user to attach any type of industry standard digital, audio or multi-media files to a field report including, but not limited to, jpg, gif, wav, etc. System will allow use of a drawing program for such items as scene recreation, etc., that will attach to the field report. System will allow a report to be initiated at the field level and completed in house or initiated in house and completed in field. System will allow flexibility in transfer of report between field mobile unit and agency headquarters for review and approval by supervisory personnel. System will allow the user to easily assign temporary review priviledges to cover such events as vacations, shift changes, etc. System will automatically audit and track each report, update and transmission and provide logging. System will allow updating by supervisory personnel to include final review and addition of Minnesota Offense Code (MOC) or any other state or federally mandated coding. System will allow viewing of any report based on user priviledges while in any stage of editing or review. When report has been approved after final supervisory review, system will assure that it is available for viewing, printing, updating or supplementing by any user. Fully Compliant Modification/Custom Software Not available Comments Other Jail Modules & Functions Inmate Possessions 1 Module must include the following fields: Name and badge of staff entering each item Entry date and time Item (table driven by facility) check box for medications Dispostion: table driven by facility Location of property: table driven by facility Received from Notes: free hand text space Module must include the following functions: Add New Save Save & close Copy Cancel Edit History: a method to track who, what, when this module information was updated or changed. Delete: Administrative function or only allowed to certain users All items must display and property list must be printable. Property list must also print out on booking sheet with a space for inmate's signature Employer 1 Name of employer field 2 Occupation field 3 Contact field 4 Phone and address of business fields 5 Notes: free hand text space 6 Add New 7 Save 8 Save & close 9 Copy Cancel 10 Edit History: a method to track who, what, when this module information was updated or 11 changed. 12 Delete: Administrative function or only allowed to certain users Media 13 Must have a module to store color photo images, including mugshots 14 Mugshots must display on first page of booking 15 Media ID numbe field Capability of determining which photo image is primary when dealing with more than one 16 image. 17 Media Capture date field 18 Add File Fully Compliant Modification/Custom Software Not available Comments Other Jail Modules & Functions Add Image Save Save & close (one keystroke) Cancel History: a method to track who, what, when this module information was updated or 23 changed. 24 Delete: Administrative function or only allowed to certain users Must interface with mugshot software/computer: Booking information populates mugshot and 25 mugshot is sent back to JMS. 26 Must be able to upload or download photos from a variety of other sources Housing 27 Cell assignment field: table driven by facility Capability of automatic search of available cells for an inmate based on classification 28 selections. Must contain override for manually cell selection. 29 Date and Time Assigned fields All cell/housing location changes are automatically documented in the inmate's jail activity 30 log Housing areas are defined by facility. The housing has to be easily modified, added to, 31 deleted by administration. Booking Notes 32 An area similar to a Word document with same or similar features as Word Staff can either free-hand into a document, or copy/paste from other programs into a 33 document. 34 Multiple separate documents can be created per inmate 35 Ability to print selected documents 36 Add New 37 Save 38 Save & close (one keystroke) 39 Cancel History: a method to track who, what, when this module information was updated or 40 changed. 41 Delete: Administrative function or only allowed to certain users Associated Names: Field that defines how another person is associated to this inmate: IE; visitor, Victim, NOK, 42 Family, etc. 43 First and Last name fields (separate) 44 DOB field, juvenile indicator and age field 45 Gender, sex, Race, Ethnicity fields 46 Height, weight, eye color, hair color, complexion fields 47 Marital status, disability fields 48 Address fields 49 Add new 50 Save 51 Save & close (one keystroke) 19 20 21 22 Fully Compliant Modification/Custom Software Not available Comments Other Jail Modules & Functions 52 Cancel History: a method to track who, what, when this module information was updated or 53 changed. 54 Delete: Administrative function or only allowed to certain users Module interface: Allow interface to master name to see complete agency contact 55 information on individual 56 Multiple entries per inmate Release Notes 57 An area similar to a Word document with same or similar features as Word Staff can either free-hand into a document, or copy/paste from other programs into a 58 document. 59 Multiple separate documents can be created per inmate 60 Ability to print selected documents 61 Add New 62 Save 63 Save & close (one keystroke) 64 Cancel History: a method to track who, what, when this module information was updated or 65 changed. 66 Delete: Administrative function or only allowed to certain users Screening 67 Medical Screening: questions defined by facility 68 Mental Health Screening: questions defined by facility 69 Inmate Transfer Sheet 70 Ability to fill out forms on the computer 71 Ability to print forms 72 Ability to add new custum forms 73 save 74 Save & close (one keystroke) 75 Cancel History: a method to track who, what, when this module information was updated or 76 changed. 77 Delete: Administrative function or only allowed to certain users 78 Forms can be easily custom made in JMS or copied/pasted from another program Alerts Ability to add a jail alert, with image or icon; IE; Administrative Alert, Approved Firearm permit, Assaultive Behavior, conceal and Carry permit, Escape Risk, Gang Member, 79 Hazardous Materials, Jail booking, Juvenile Offender, No Contact, Open civil processing, Order for Protection, Outstanding Warrant, Risk, Security Threat Group, Sexula Offender, Temporary Restraining Order. 80 Ability to add a master name alert 81 Edit History: a method to track who, what, when this module information was updated or 82 changed. Fully Compliant Modification/Custom Software Not available Comments Other Jail Modules & Functions 83 Delete: Administrative function or only allowed to certain users 84 Administrative rights to add, change or delete alerts and their icons and images 85 Alerts are shared between dispatch, records and jail Insurance Information 86 Insurance is active field: yes or no 87 Coverage type field (builds own table, word recognition for future use) 88 Provider field: (builds own table, word recognition for future use) 89 Policy number field 90 Group number field 91 Effective Date field (drop down calendar) 92 End date field: (drop down calendar) 93 Agent Name and phone number fields 94 Add new 95 Save 96 Save & close (one keystroke) 97 Cancel History: a method to track who, what, when this module information was updated or 98 changed. 99 Delete: Administrative function or only allowed to certain users No Contacts 100 Last name field 101 first name field 102 Entered by field (table driven by facility) 103 Reason field 104 Remarks: free hand text entry 105 Approved by field (table driven by facility) 106 Begin date field (drop down calendar) 107 End date field: (drop down calendar) 108 Multiple contacts can be listed per inmate 109 Entry to this module creates an alert on the booking 110 No contacts print out on housing roster ID Numbers 111 Number field Number type field: Alien number, Deer Permit, Driver's License, Employment ID, FBI, Gun 112 Permit, Library Card, Local ID, School ID, Social Security, State ID, US Marshal Number, Passport 113 Number State field 114 Expiration date field 115 Driver's License Class field Driver's License Endorsements field: Farm Service, passengers, Hazardous Material, School 116 Bus, Tank Vehicles, Double Triple 117 Comments Field: Free hand text 118 Primary ID number indicator if there is more then one ID # 119 Add New Fully Compliant Modification/Custom Software Not available Comments Other Jail Modules & Functions 120 Save 121 Save & close (one keystroke) 122 Cancel History: a method to track who, what, when this module information was updated or 123 changed. 124 Delete: Administrative function or only allowed to certain users ID Marks Mark Type field: Amputee, Birth Mark, Burn, Dimple, Needle, Pierced, Pockmarks, Scar, 125 Tatoo 126 Mark Location field: State table driven 127 NCIC description field: state table driven 128 Comments Field: Free hand text Images: from mugshot software, automatically or manually interfaced to this module in the 129 JMS 130 Images: ability to get images from other sources 131 Add new 132 Add multiple entries which show individually in inmates booking 133 Save 134 Save & close (one keystroke) 135 Cancel History: a method to track who, what, when this module information was updated or 136 changed. 137 Delete: Administrative function or only allowed to certain users Phone Numbers 138 Phone Number field 139 Extension Field Phone Type: table driven: Residential, 24 hour, After Hours, Business, Caretaker Phone, 140 Cell Contact, Emergency, FAX, General Office, Home Phone, Message Number, Pager, Personal Office, Second Line, Toll Free, Vacation Home, Work 141 Primary check box 142 Unlisted check box 143 Add New 144 Save 145 Save & close (one keystroke) 146 Cancel History: a method to track who, what, when this module information was updated or 147 changed. 148 Delete: Administrative function or only allowed to certain users Aliases 149 Add New 150 Edit Module interface: Allow interface to master name to see complete agency contact 151 information on individual Fully Compliant Modification/Custom Software Not available Comments Other Jail Modules & Functions History: a method to track who, what, when this module information was updated or changed. 153 Delete: Administrative function or only allowed to certain users 152 Aliase Type field: AKA, Civil Process, Gang, Gang Moniker, Maiden Name, Nickname Transmission Log Automatically runs NCIC/Warrant/QP checks on all newly booked inmate. Records all 155 transmissions and replies and stores them in this module. 156 Automatically makes an activity log entry for all NCIC/Warrant/QP queries and replies Automatically runs NCIC/Warrant/QP checks on all inmates who are being released. 157 Records all transmissions and replies and stores them in this module. 158 Automatically makes an activity log entry for all NCIC/Warrant/QP queries and replies 159 Ability to manually run NCIC/Warrant/QP checks on any in-custody inmate. 160 All entries to the the transmission log are printable. Visitor Status Associated Names: Able to choose from all names in our system (records included) along 161 with adding new names. 162 Check boxes for "approved" "not approved" "restricted" "Active" 163 Fields for start and end dates 154 Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 9 10 Interfaces Inmate Phone system Vines MRAP Fingerprints Image Trend S3 / DOC Social Security Report Commissary (if it is not incorporated into JMS software) All interfaces must be compliant with state/CJIS requirements All interfaces must operate with automatic up and or down loads to and also have capabilities to be used manually by users with administrative rights. Fully Compliant Modification/Custom Software Not available Comments 11 All interfaces must comply with data privacy/HIPPA laws 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 Classification This module must contain all of the following fields that are table driven by the facility. Administrator must be able to edit and modify all tables. Security Threat Group Custody Status Education Medical Concerns Mental Concerns Escape Risk Current Charges Prior Charges Institution Behavior Classification Classified by: (staff) Date Classified Next classification date: (calendar drop down box) Prior to being able to close out this module, user is alerted to update the Next Classification Date. Function can be over-ridden by user. Notes: Free hand text Recommendations: Free hand text The information from this module must be printable in the inmate transfer sheet format This information must be safed and viewable from the inmate's booking add new save save & close (one key stroke) Copy Cancel History: a method to track who, what, when this module information was updated or changed. Delete: Administrative function or only allowed to certain users Field for staff name and badge number who is assigned as the classification officer for this inmate Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 7 8 9 10 11 12 System Administrator Personnel multiple security levels set by groups or individuals. Add, edit or delete users. Customized areas of access to the software for different users. Table maintenance by the system administrator. Badge number tracking and re-assigning capabilities. Permanent records of names and badge numbers associated with them even after the badge is re-assigned to someone else. Jail housing. Capability of adding / modifying new or old units, cells, beds, etc. Ability to build customized forms in the system for users. Ability as system administrator to correct booking errors, merge files, change inmate names, enable released jail bookings for editing, etc. Ability to give some of the supervisors certain administrative user rights. Ability to use extracts manually if needed. The different modes of this software have to allow for adding new, editing, saving, saving & closing (one key stroke), copy, cancel, history, delete. These functions must be addressed as different security levels for different users. Fully Compliant Modification/Custom Software Not available Comments Commissary Active Inmate Accounts Active Inmate Accounts: Individual accounts for each inmate; where you can deposit, 1 transfer, withdraw (via check) money. Show type of deposit, transfer, withdrawal and all details of those transactions. Deposits by credit card, mail, visitor, Huber, initial booking. Disbursements by inmate 2 release, 3rd party property release. Purchases by commissary and voucher sales, booking fee, clippers, notary OTC meds, phone cards and sick call. Receipts Most transactions require a receipt, some require 2 receipts. Receipts contain name, 3 pin, amount of deposit, balance (not on visitor receipt), housing unit and cell, transaction type, etc. 2 receipts needed for deposit by visitor, print duplicate receipt that can not have 4 inmate balance on it. 5 Ability to print a duplicate receipt for previous transactions. Account must maintain a running balance, handle negative balances, take ending 6 balances and forward them to a new account when the inmate comes back into custody. JMS needs to include an alert upon inmate release that indicates if there is a positive 7 balance in inmate account. 8 Ability to query inmate accounts: by PIN or Name, In or out of custody. Account must be able to transfer money from one account to another. Transfers 9 between inmate accounts for admin users only. Transfers to internal accounts by users. Multiple inmate selection for transactions. Inmate Account Balance Transfer to new 10 Booking Adjustments. Transaction information must reflect, time, date, inmate name, transaction type, 11 description of transaction, payment type, staff conducting transaction, amount of money, narrative section, who made it and documented it. Query Inmate Accounts 12 Ability to administratively freeze accounts deposits and/or withdrawals. 13 Ability to manually add or edit an account. Multiple Transactions Ability to select multiple inmates and apply a single transaction type to all of them, 14 including date, time, inmate name, pin, amount of transaction. Internal Accounts 15 Booking, clippers, notary, otc meds, phone cards, sick call, voucher, ZZ checks. Some Internal accounts must be able to take money from an inmate account even if it 16 has a negative balance, other internal accounts can not take money from an inmate account with a negative balance. 17 Ability to cut/copy/paste between accounts. Administrators need to be able to set security levels and function access for users. 18 Separate from JMS. Accounting Accounts 19 Cash, commissary, sales tax, inmate receivable. Fully Compliant Modification/Custom Software Not available Comments Commissary Drawer Accounts Must be able to close drawer after deposits are made to it, and print drawer report, balance account and start with 0 balance at beginning of each shift. Amount of closed 20 drawer transfers to cash account. Must be able to run and print a historical drawer report using multiple parameters; IE; summary, detail, for a date and time frame, by drawer; combination of any or all of these. Users assigned to one or more drawers. Booking, Admin, visiting, finance, money order. Need ability to run and print individual and combined drawer reports. Other Closed Accounts 22 Transaction List. 23 Ability to reverse transactions. Receipts must print on reversals. 24 Ability to reverse a reversal. Workstation Drawer Accounts 25 Workstation Receipt Printer. Ability to run reports on any individual account that will include all transactions for that 26 account, dates, times, transaction types and running balance. Inmate Account History Active Account Balance Account History 27 Soundex search capabilities. 28 Ability to run a report that will show all in-custody inmates and their balances. Diet Restrictions Add, edit & specify for Commissary Sales. Restrictions: Administrative Seg, Allergy, 29 Bland, Dental, Diabetic, Lactose Free, Low Fat, Low Sodium. Reports Inmate Account History: query by transaction type. Inmate Sales. Sentenced Inmates 30 with negative account balances. Query products sold (weekly, monthly, daily). Query inmates who purchased certain commissary products. Bank Reconciliations: Set-up similar to how reconciliations are done in Quicken or 31 Quickbooks. Check & Deposit Reconciliation With Bank: Include Outstanding, cleared and/or 32 voided checks. 33 Check Register: Track Payee Name and Address. Transactions: Ability to Search all: Deposits, disbursements, check purchases, 34 transfers, etc. Reports. Include beginning balance, cleared checks/deposits, outstanding 35 checks/deposits, new checks/deposits and ending balance. Reconciliation reports, Outstanding deposits, Active Inmate Account Balance with 36 option to Include Released Inmates: Include inmate, accounting & internal account balances to balance with cash balance. 37 Released Inmates: Ability to correct check numbers. Commissary Sales 38 Must be ten-key. 21 Fully Compliant Modification/Custom Software Not available Comments Commissary 39 Must be able to say if inventory is out of stock and/or restricted. Must be able to reverse single item(s) from an order without reversing the entire order 40 after receipt has printed. 41 Must be able to add or delete an item to an order. 42 Must be able to credit an inmate's account even if inmate's balance is negative. Must be able to calculate voucher sales (no charge to inmate) with a spending limit of 43 $10.50. 44 Must be able to calculate when TOTAL order goes over spending limit $65.00. 45 If over total spending limit, inmate only receives HYGIENE ONLY ordered. 46 Must be able to calculate when "FOOD" only total goes over the $45.00 limit. 47 If over food limit, inmate only received HYGIENE ONLY ordered. 48 Inmate is denied commissary if non-sufficient funds. 49 Commissary Sales Report. 50 Voucher Sales Report. 51 Trustee Shoe Report. 52 Ability to create voucher report for trustee shoes-one time. 53 Report of monthly/weekly daily sales of a particular item(s). Report of monthly/weekly/daily sales of individual inmate (to find if an inmate 54 purchased a particular item). Sales Tax Ability to change sales tax rate (July 1, 2009 sales tax rated increased from 6.5% to 55 6.875%). 56 Sales Tax reported monthly to MN Revenue and paid electronically. 57 Generate Monthly sales tax form. Include Gross sales, Adjusted Gross sales (no tax, Taxable sales, Non-Taxable sales 58 and Sales Tax. 59 Sales Tax due is rounded to the nearest dollar. 60 Sales Tax Account History Report. Voucher Sales 61 Spending Limit of $10.50. 62 Ability to change the weekly allowance. 63 Need to be able to stop at the specified allowance and not delete any item(s). Inventory 64 Inventory is done on weekly basis. 65 Inventory Report listing current item quantities. Generate an Inventory form to enter current quantities and inventory counts to get 66 variances. 67 Archive Reports or be able to download to Excel. 68 Enter Beginning Inventory Report item quantities. 69 Print counting sheets for inmates listing all inventory items. 70 Enter counts from counting sheets. 71 Print Ending Inventory Report to balance with totals on Inventory form. 72 Variances to be adjusted in inventory. 73 Variance Report. 74 Damaged Goods Log. Fully Compliant Modification/Custom Software Not available Comments Commissary Must be able to return an item that is "damaged", "spoiled" or "open package' and 75 exchange it. This would be auto logged into a damaged goods log and taken out of inventory as damaged, spoiled, or open package. 76 Damaged Goods Log Report, which should generate from computer/manually. 77 Product Cost Report. 78 Based on what ordered for week of inventory-total sales/revenue. 79 Inventory Sales Report. Product Ordering 80 Print Inventory report and check what needs to be ordered based on a re-order point. 81 re-order point on Inventory Report. 82 Need an Order sheet for each vendor. 83 Ability to print the order sheets and fax/e-mail/call order to each vendor. Product Receiving 84 Print Beginning Inventory Report. 85 Ability to receive all or part of an order received. 86 Back-ordered items. Ability to remove an item(s) that was ordered (not cost effective to have one item 87 shipped when I can just order it the following week). 88 Receiving Report. 89 Show how received items were adjusted. 90 Print Ending Inventory Report (automatically print inventory report). Vendor Management 91 Add/Edit/Inactivate all vendor information. 92 Address, contact, phone, fax line, customer number and e-mail address. Ability to link the items in Item Maintenance to which vendor a product is order from 93 (Maxima ID; refried beans). 94 Produce an order sheet based on vendor. 95 Currently have 12 vendors and possibly more in the future. Item Maintenance 96 Restrictions 97 Ability to add, edit and delete restrictions. 98 Ability to add, edit and inactivate items. 99 Inactivation of items but keep history. 100 Ability to change prices, sales tax, etc. 101 Month-end of Commissary Internal Accounts. 102 Clippers/OTC meds/booking/sick call/notary/phone cards. 103 Report for Disbursement of monthly sales. 104 Include total sales only of internal account on report. 105 Disbursement made in Internal Account by check. 106 Account History Report for all Internal Accounts. Fully Compliant Modification/Custom Software Not available Comments 1 2 3 4 5 6 Activity Logs Permanent, tamper proof, no editing allowed, method of recording and documenting inmate activities (individually and as a group), facility activities, inmate location changes (individually and as a group), that are time and date stamped by when they happened and also by when they were logged. Must reflect who the officer was making the entry. Must include: officer & badge number, inmate name and PIN Created by: computer stamp Date and time created: from table list Activity Type: selected by officer entering information Date and time of activity: from table list Fully Compliant Modification/Custom Software Not available Comments 7 Location of inmate/activity: Cell and Housing unit that the inmate is currently housed in 8 9 10 11 12 13 14 15 16 17 18 19 20 Remarks: Notes space. Ability to make it a scheduled activity. Ability to make it a facility activity. Ability to view, sort and print activity logs via activity type, inmate, date, staff, housing unit, etc. Ability to save and review all of these records permanently. Ability to record history of inmate's housing unit and cell assignments. Ability to enter documentation by inmate, activity, location or as a facility code. Ability to schedule activities for future reference. These records can not have a delete function. Once saved they can not be altered. Need verification from vendor, in writing, that these records are tamperproof and permanent. This is the largest amount of data the jail produces. We will require an enormous amount of storage for these logs. Ability to copy/paste, to speed a mutliple duplicate entries. and/or use Sessions to move groups of inmates from one location to another and then back again. Administrative rights to add activity types to the table. "Notes" section for free hand entry of documentation. The different modes of this software have to allow for adding new, editing, saving, saving & closing (one key stroke), copy, cancel, history. These functions must be addressed as different security levels for different users. Reports Billing 1 Reports must be sortable by Controlling Agency ORI. Ability to run all in-custody inmates by ORI (names in alpha order by ORI) without having to 2 select ORI. Basically a one-keystroke function. 3 Ability to run in-custody inmates for one ORI (names in alpha order). 4 Ability to run reports for any given date or any time frame. 5 Ability to set the Begin Date and Time for report to start. 6 Ability to set the End Date and Time for report to Stop. 7 Print & e-mail features. 8 Administrative ability to change the per diem rate. Ability to have different per diem rates for different ORI's and have the system calculate these 9 automatically. 10 Report must show the Billing Date or Date Range that is being reported on the document. 11 Header: Sherburne County Sheriff's Office / Jail Billing Report. All inmates per ORI are listed Alphabetically IE; Anoka county boarders are all together, ICE 12 inmates are listed together, etc. Report contains: Full Inmate Name, DOB, Alien #, Date and/or date range for boarding, # days, 13 Rate per day, Inmate total cost. At the end of each page are page totals as well as running totals for ORI's that are more then one page long. Totals include the number of inmates per page and the running accumulated 14 total on consecutive pages. It also contains the total dollar amount and the accumulated total on consecutive pages. Housing Roster 15 Must be sort able by housing unit, Inmates must be listed in report by housing unit. Must be able to run one housing unit, or a selection of housing units, or the whole facility (one 16 keystroke for whole facility). 17 Report must be printable with the ability to save it as a PDF to the computer or e-mail it. Must be able to run a housing report by inmate alpha order with their housing unit and cell listed 18 by their name. 19 Report Header: Sherburne County Sheriff's Office / Housing Roster. Report must contain the date of report, the housing unit, Cell and bed numbers, Booking # per 20 inmate, Full inmate name, and an expected release date if there is one. Inmate information is correlated with cell and unit assignment. 21 No contacts must be listed on reports, information comes from the "No Contacts" module. End of report reflects number of inmates included in the report and the number of beds in the 22 facility. Media 23 Ability to run reports for any given date or any time frame. 24 Ability to set the Begin Date and Time for report to start. 25 Ability to set the End Date and Time for report to Stop. 26 Print & e-mail features. 27 Report to contain only certain inmates (parameters to be set by facility). 28 Report to contain Full inmate name, address, age, charges. New Charges Fully Compliant Modification/Custom Software Not available Comments Reports Ability to run reports for any given date or any time frame to get a report of all new bookings during that time frame. 30 Ability to set the Begin Date and Time for report to start. 31 Ability to set the End Date and Time for report to Stop. 32 Print & e-mail features. 33 One keystroke daily calculation function. 34 Ability to run reports for adults OR reports for juveniles. Report must contain the reporting period date(s), book date and time, booking number, inmate's full name, DOB, Age, gender, Level of charge, address, arresting agency, Reason detained, 35 arrest city, release date, sentence end, release reason, disposition remarks, disposition authority. Court Calendar Ability to run reports for any given date or any time frame to get a report of all inmates who have 36 a scheduled court date during that time frame. 37 Ability to set the Begin Date and Time for report to start. 38 Ability to set the End Date and Time for report to Stop. 39 Print & e-mail features. 40 One keystroke daily calculation function. 41 Ability to run reports for adults OR reports for juveniles. Report must contain the reporting period date(s), book date and time, booking number, inmate's full name, DOB, Age, gender, Level of charge, address, arresting agency, Reason detained, 42 arrest city, release date, sentence end, release reason, disposition remarks, disposition authority. Jail Census Ability to run reports for any given date or any time frame to get a report of all inmates who are 43 in custody on at that time. 44 Ability to run a summary report as well. 45 Ability to set the Begin Date and Time for report to start. 46 Ability to set the End Date and Time for report to Stop. 47 Print & e-mail features. 48 One keystroke daily calculation function. Regular Report be in alpha order and must contain the reporting period date(s), book date and time, booking number, inmate's full name, DOB, Age, gender, Level of charge, address, 49 arresting agency, Reason detained, arrest city, release date, sentence end, release reason, disposition remarks, disposition authority. Summary report must be in alpha order and contain inmate full name, Booking #, Inmate #, 50 DOB, Gender, Race, Booking Date & Time, expected release date, Release date, cell and housing unit. Transmission Report 51 Ability to run a QP & warrant check report for an inmate's NCIC/warrant check. 52 Print & e-mail features. Inmate Classification Must be the same format as the current inmate transfer sheet that we use. Form is 53 recommended by the MSA. 54 Print & e-mail features. 29 Fully Compliant Modification/Custom Software Not available Comments Reports 55 must be able to save the report to appropriate inmate. 56 ability to save multiple reports to inmate. Must contain inmate name, DOB, reason for transfer of inmate; Writ/Warrant/Boarder/Other, current housing status; admin seg, disc. Det., prot. Cust., special needs, Security Group affiliations, escape risk, assaultive behavior, Medical or mental health issues, suicidal 57 tendencies, no contact issues, other holds, officer name and badge completing form, date and time completed, space for supervisor's signature, space for releasing officer's signature, space for transport officer's signature, space for receiving facility officer's signature, date field, our facility information. 58 Save and print. 64 All information from the classification module. Inmate Possessions Ability to select an inmate and print out the possessions that have been inventoried for them 65 and placed in property List should include all items currently on list and those that have been released, but the report 66 should indicate the items that have been released Booking Sheet 67 Header: Sherburne County Sheriff's Office / Booking Sheet / Booking # 68 Fingernail mugshot. 69 Booking #, Inmate #, housing unit and cell, location. Full Name, last, middle, first, SSN, Address, Alien Number, Phone #, Employer, book Date & time, Expected release date & time, Release date & time, Birthplace, Birthstate, DOB, physical 70 description, Status/class/risk: controlling agency, offense level, reason held, detention status, risk assessment. list charges; level of offense, MOC code and descriptor, case #, court #, Warrant #, Citation # 71 Arrest Date and time, offense date, offense type, offense disposition, controlling agency, arresting agency, arresting officer, arrest location, transport officer, arrest city, booking officer. 72 list of inmate possessions and their location in the property room. 73 Inmate signature and date line. 74 Staff signature and date line. Booking Notes 75 Ability to select an inmate and print out the booking notes associated with that booking. 76 Print & e-mail features. Jail Activity Log 77 See Jail Activity Log section for notes regarding required report features. Ability to run reports for any given date or any time frame, ability to run activity log reports based 78 on location, or inmate, or activity, or any combination thereof. 79 Ability to set the Begin Date and Time for report to start. 80 Ability to set the End Date and Time for report to Stop. 81 Print & e-mail features. 82 ability to run a report on in-custody or released inmates. Report must contain, the reporting period, location, inmate name, activity type, time that officer 83 made the log entry, time it was actually entered into computer, name and badge of staff making log entry, remarks. Fully Compliant Modification/Custom Software Not available Comments Reports Drawer Reports 84 See commissary for details required for drawer reports. 85 Report choice of summary or detailed information. 86 Report to include drawer name. 87 date and time period for report. Media: cash, check, money order, credit card, including totals for each and then a grand total for 88 all deposits. Specifically report date and time of deposit, PIN #, Inmate Name, transaction, media, deposit 89 amount, total, officer making entry. 90 Print & e-mail features. 36/48 Hour Report Daily report that calculates the time and day a new booking is allowed to get up to court before 91 they have to be released. Miscellaneous Reports: Ability to search and/or sort by any field in a booking to get a report on that information or range 92 of information. 93 Print & e-mail features. Fully Compliant Modification/Custom Software Not available Comments Booking General Booking Information 1 Search for in/out of custody inmates. 2 Search for in/out of custody inmates. 3 to edit any module of the jail booking to update or correct booking information. Inmates incorrectly booked as a new booking can be edited to match up with previous 4 bookings. 5 Automatic sequential booking number assigned. 6 Administrative ability to adjust number. 7 Start booking to PIN inmate and come back to finish booking later. 8 Automatic log to inmate's activity log regarding booking date and time. Automatically run a search for warrants, that includes notification of results. 9 Ability to print results of search. Warrant check automatically logs warrant check results in the inmate's activity log. Basic inmate/charge/vital statistic information gathered and displayed on first part of 10 booking for each inmate. 11 Master number associated with an individuals first booking. CHN New booking number (PIN) each time they are re-booked and still run the original 12 number (CHN) with each new booking. 13 Name: Separate Fields for Last, Middle, First. 14 Fields for names have to accommodate VERY LONG names and hyphenated names. Capability of matching a new booking name with an old booking for the same inmate. 15 Some booking information should transfer to new booking. Staff need capability of picking what items transfer to new booking. IE; address, phone, SS#, mugshot, etc. 16 17 18 19 20 21 22 23 24 25 26 27 28 Administrative access to correct bookings matched wrong or not matched at all Booking agency ORI Controlling Agency Multiple ORI's to choose from (table driven w/administrative ability to update) Multiple charges from multiple controlling agencies capabilities *Case Number Per charges capabilities Expected Release Date Actual Release Date & Time State ID # Date of Birth Age Sex Fully Compliant Modification/Custom Software Not available Comments 29 Juvenile: allow for a juvenile booking, but keep booking information as private data 30 31 32 33 34 This should put some type of alert on the booking to note that it is a juvenile. Race BCA Table Code Height Weight 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 Booking Booking Date & Time Not to be altered by anyone A/J Certification Adult or Certified Juvenile Offense Level Misdemeanor, Gross Mis, Felony, petty misd. Reason Held BCA Table Code Inmate Location Table driven by facility codes Release Reason BCA Table Code Cell Assignment Ability to search for open beds and make cell/bed assignments to new inmates. Record of date housing unit and cell are assigned Automatic entry to jail activity log under inmate's name of housing unit and cell. Initial Classification Multiple fields chosen by the facility. Each field is driven by multiple choice table. Categories and tables to be selected by facility. Initial Classification: Maximum, medium, minimum. This risk assessment is included with S3 interface along with required booking information. Mugshot (color) Booking information is interfaced to mugshot system and sent to MRAP, photo is interfaced back to JMS. Inmate Account Balance Show balance only on first page. Attributes Table driven by BCA codes: (mandatory) Eye Color, Hair color, Eye wear, hair length, Hair style, facial hair, general appearance, complexion, condition, disability, demeanor, build, teeth, speech, hand use, ethnicity, marital status, citizen, resident, religion. Address Separate Fields for address, city, state, zip, County, Country. Drop down boxes for appropriate fields. Automatic population of field, with over-write capabilities when using repetitive information already entered into jms. Country codes must be world wide. Booking officer name and badge # Court division Detention reason BCA Table Code Hold Status Narrative: Space for freehand text, notes Photographed by: Officer name & Badge # (table driven drop down box) Fingerprinted by: Officer name & badge # (table driven drop down box Search by: Officer name & badge#(table driven drop down box) Fully Compliant Modification/Custom Software Not available Comments Booking Type of Search Drop down boxes for appropriate fields. IE; Pat, Frisk, Strip, etc. NCIC check check box Warrant Check check box If warrant is active, sets an alert on booking Orientation Given check box Victim Involved check box, if yes, sets alert on booking Arrest (fields for all of the following): Arrest Date & time Arresting agency Arresting officer Arrest city Next Court Date/time Arrest Location/address Detainer/ 80 check box 36/48 hour rule: automatically configure from time of booking Towing Company: table driven by facility Transport Officer Remarks: space for freehand text Charge Sequentially order multiple charges Controlling Agency: table driven, contains 81 Multiple ORI's 82 field for case number Offense Code Information: Fields for MOC style offense code; including statute 83 numbers and written descriptions. All come from BCA driven tables. 84 Counts: 1 through? Field 85 Offense level: Field 86 Offense Type: (BCA table driven) 87 Offense date field Fields for: Offense city, offense location, court number, citation number, warrant 88 number. 89 check box for Pay For Stay 90 Charge purpose field, BCA table driven 91 Offense disposition field 92 Disposition Authority field 93 Disposition Date field 94 Finger print number field 95 Finger printed by field 96 Disposition Remarks: free hand text box for notes written by staff 97 Original Office field; including offense code, description and statute #. 98 Remarks field: free hand text box for notes written by staff History: a method to track who, what, when this module information was updated or 99 changed. Release Alerts show up in this module to warn you that you must notify a victim, you must 100 check for warrants, the inmate has money in their commissary account, etc. Automatically run a search for warrants, that includes notification of results. 101 Ability to print results of search. Warrant check automatically logs warrant check results in the inmate's activity log. 102 Reason Released field: table driven by BCA 103 Reason Satisfied field 73 74 75 76 77 78 79 Fully Compliant Modification/Custom Software Not available Comments Booking Release Date field Release Time Field Allow to accept of Early Release Date Releasing officer field: from site driven table of staff Show balance of $ released field check box for Pay For Stay check box for medications that are returned to inmate check box for medications that are kept by facility Released to field: Contain all ORI's Narrative field: free hand text box for notes written by staff Automatic activity log of release made for inmate Administrative ability to unlock release information for editing History: a method to track who, what, when this module information was updated or 116 changed. 117 Bond/Bail Information 118 Bond Type field: 119 Bail amount field 120 bond amount field 121 Receipt field 122 Bondsman field: table driven by site 123 Fine Amount field 124 Bond Remarks field for free hand text History: a method to track who, what, when this module information was updated or 125 changed. Offense 126 Charges must link with Offense information 127 Release function would move from charge module to offense module. 128 All Arrest information from above 129 All Charges/Offense information from above must duplicate to this module 130 Sentence Information module must automatically compute sentence outdates based on data entered into 131 this module including multiple offenses 132 Sequentially order multiple offenses Controlling Agency Allow for consecutive and concurrent sentences. Adjust sentence outdates 133 accordingly. 134 Sentence start date and time fields 135 Sentence length field ability to override automatic computer outdates so we can do them manually when 136 needed 137 Trustee, STS and Treatment good time 138 Over ride Good time capabilities 139 Good time field Editing ability after all information has been entered. Automatic sentence outdate 140 adjustment 141 Override Credit time served check box 104 105 106 107 108 109 110 111 112 113 114 115 Fully Compliant Modification/Custom Software Not available Comments 142 143 144 145 146 147 148 149 150 151 152 153 Booking Credit time served field Sentence end date and time field: without good time Expected release date: Sentence end date and time field: with good time Override expected release date check box Remarks: freehand text box History: a method to track who, what, when this module information was updated or changed. Release: Must have the same functionality as release module listed in offenses ability to release one offense and still keep them on another or on a charge. When an offense or charge is released the controlling agency ORI on the first page automatically updates to the next controlling agency ORI When a controlling agency change is made, it must update on the billing report The different modes of this software have to allow for adding new, editing, saving, saving & closing (one key stroke), copy, cancel, history, delete. These functions must be addressed as different security levels for different users. Fully Compliant Modification/Custom Software Not available Comments