Arizona State University Police Department Request for Proposals #: CAD/RMS/Mobile. Interface Functional Requirements

Transcription

1 Arizona State University Police Department Request for Proposals #: CAD/RMS/Mobile Interface Functional Requirements Item # Interface Functional Requirements S M A U Comments 1 SpectraCom 9383 NetClock 2 Ability to support a shared master time source via a one-way interface to the following applications and equipment: 3 CAD 4 Mobile 5 RMS 6 AFR 7 PCs 8 ANI/ALI controller 9 Voice recorders 10 Radio consoles 11 CAD consoles 12 Ability to time stamp all system transactions to the tenth of a second. 13 Esri ArcGIS System Functionality Modification Needed. At no extra Cost Modification needed at an additional cost Unable to meet the requirement Please explain any line items (from the left that are not an "out of the box" standard but are part of your overall proposal; specifically, why the particular line item is not an "out of the box" standard. Additionally, please identify what potential effect this may have upon meeting a January 13, 2020 implementation date. (Required for any items marked "M", "A", or "U") Your proposed solution will be evaluated based on the value of each of these items combined and will not negatively impact the proposal. Arizona State University Police Department Interface Functional Requirements 1 of 14

2 14 Ability to support a one-way interface from the University's Enterprise Geospatial Repository (EGR) to the geofiles used by: 15 CAD 16 Mobile 17 RMS 18 AFR (Automated File Retrieval) 19 Ability for application geofile(s) to receive updates from the EGR at agency defined intervals. 20 ACJIS/NCIC 21 Ability to support a two-way interface between the ArizonaCriminal Justice Information System (ACJIS)/National Crime Information Center (NCIC) and the following public safety applications: 22 CAD 23 Mobile 24 RMS 25 Ability to run ACJIS/NCIC queries from the command line. 26 Ability to run ACJIS/NCIC queries from a query mask. 27 Ability to query ACJIS/NCIC from the RMS. 28 Ability to copy/paste information from ACJIS/NCIC into an active or closed CAD event. 29 Ability to attach ACJIS/NCIC "hits" to the call for service. 30 Ability to send an attached ACJIS/NCIC "hit" to an officer's mobile application. 31 Ability to query ACJIS/NCIC from the mobile environment and populate the data returns into the following: 32 Reports 33 Forms 34 Citations 35 Ability to do the following to ACJIS/NCIC data fields: 36 Add 37 Modify Arizona State University Police Department Interface Functional Requirements 2 of 14

3 38 Remove 39 Ability to update the RMS with agency defined information returned from a ACJIS/NCIC inquiry. Ability to support agency defined automatic ACJIS/NCIC queries 40 based on the transaction performed (e.g., run plates up entry of a traffic stop). Ability for the department to disable automatic ACJIS/NCIC queries 41 based on the transaction performed (e.g., run plates up entry of a traffic stop). 42 Criminal Justice Information System (CJIS) 43 Ability to support a two-way interface between the Criminal Justice Information Control (CJIS) and the following applications: 44 CAD 45 Mobile 46 RMS 47 Ability to query CJIS from: 48 CAD 49 Mobile 50 RMS 51 Ability to copy/paste information from CJIS into an active or closed CAD event. 52 Ability to attach CJIS "hits" to the call for service. 53 Ability to send the attach CJIS "hit" to an officer's mobile application. 54 Ability to query ACJIS from the mobile environment and populate the data returns into the following: 55 Reports 56 Forms 57 Citations 58 Ability to update the RMS with agency defined information returned from a ACJIS inquiry. Arizona State University Police Department Interface Functional Requirements 3 of 14

4 59 Ability to transfer warrants stored in ACJIS into the RMS at agency defined intervals. Ability to support agency defined automatic ACJIS queries based on 60 the transaction performed (e.g., query plates upon entry of a traffic stop). Ability for the department to disable automatic ACJIS queries based 61 on the transaction performed (e.g., query plates upon entry of a traffic stop). Ability for user to make simultaneous ACJIS queries (e.g., when a 62 vehicle is run in the ACJIS/NCIC, the registered owner of the vehicle is also queried in the RMS and ACJIS). 63 LE WEB 64 Ability to support a two-way interface between the County mugshot system to the following public safety applications: 65 CAD 66 Mobile 67 RMS 68 Ability to query the County Mugshot system based on the County's booking photo identifiers. 69 Ability for the County Mugshot system query to return the image and any information associated with that individual. 70 Ability for the data stored in the County's mugshot system to be incorporated in the Photo Lineups created in the RMS. Ability for user to make simultaneous County Mugshot system 71 queries (e.g., when a subject is run in the ACJIS/NCIC, he or she should also be queried in the County Mugshot system, CJIS and the RMS). 72 ecite - Make and Model to be Determined 73 Ability to support a two-way interface between the County and the application from the following public safety applications: 74 CAD 75 RMS & Mobile Arizona State University Police Department Interface Functional Requirements 4 of 14

5 76 Ability to transfer call for service data from CAD into the application. 77 Ability to populate accident reports in the application with subject and vehicle information from the master indices. 78 Ability to transfer accident reports written in the application into the RMS at agency defined intervals. 79 Ability to link new subject and vehicle information from the application to the RMS master indices. 80 Ability to link new subject and vehicle information from application to any associated events. 81 Ability to transfer call for service data from CAD into ecite. 82 Ability to provide the option of populating the electronic citation with information from the master indices. 83 Ability to transfer accident reports written in ecite into the RMS at agency defined intervals. 84 Ability to link new subject and vehicle information from ecite to the RMS master indices. 85 Ability to link new subject and vehicle information from ecite to any reports associated with the incident in which the citation was issued. 86 Enterprise Document Management System; Make/Model To Be Determined 87 Ability for users to search files stored in the Document Management System by: 88 incident number 89 Date 90 Officer Name 91 Subject Name 92 Keywords 93 Ability to link files from the Document Management System to: 94 Master records 95 Calls for Service 96 Incident Records Arizona State University Police Department Interface Functional Requirements 5 of 14

6 97 Reports 98 Field Interviews 99 Citations 100 Permits 101 Other data found in the RMS Ability to provide full access (based on personnel security standards) 102 from the RMS to the files in the Document Management System which allows the user to: 103 Add 104 Modify 105 Redact 106 Rename 107 Delete 108 LInX - Northup Grumman (Software) 109 Ability for Records Management or CAD to include a Global Justice XML Data Export Module 110 If not, are there plans to develop an export module and what is your implementation timeline 111 Ability to provide the capability to export all law enforcement data from RMS and/or CAD including: 112 Incident Reports 113 Accident Reports 114 Warrants 115 Arrest and Booking Records 116 Field Interview/Contacts 117 Pawnshop Records 118 Citations 119 Traffic Stops 120 Sexual Assault Registry 121 Mugshots and photos with any associated record type 122 Narratives and supplemental narratives 123 Other: 124 Other: Arizona State University Police Department Interface Functional Requirements 6 of 14

7 125 Other: 126 Ability for the export module allow the agency to control what data can be exported and when 127 Ability to control what data can be exported, include the ability to restrict the export of sensitive records 128 Is there an extra cost to obtain this export module? 129 Would there be an on-going annual maintenance cost for this type of export module? 130 Is there another agency currently using or a participating member with LInX? 131 Is there a point of contact or agency references for LE agencies that are currently using this export capability? 132 Other: 133 Other: Intrado VIPER 136 Ability to provide a one-way interface between the Intrado VIPER E9-1-1 system and the CAD application. 137 Ability for the user to import ANI/ALI data into the CAD application. 138 Ability for user to import TEXT to data into a call for service. 139 Ability to pre-fill the CAD incident mask with ANI/ALI data. 140 Ability for CAD to geo-verify the ALI information. 141 Ability to convert Phase II Wireless call ALI data containing lat/long coordinates in CAD. 142 Ability to plot Phase II Wireless call ALI data containing lat/long coordinates on the CAD map. 143 Ability for updated VIPER information to automatically update data that has already been transferred into the CAD system (e.g., if the Phase 1 information is updated to Phase 2). Arizona State University Police Department Interface Functional Requirements 7 of 14

8 144 Ability to incorporate Next Generation functionality into the interface as technology and standards in the area develop. 145 Motorola Gold Elite Radio System 146 Ability to provide a one-way interface with the CAD system and Motorola Gold Elite Radio. 147 Ability to transfer push-to-talk data from Radio System to CAD. 148 Ability for the controlling dispatcher CAD station to receive and capture the following radio traffic data: 149 Date and time transmission initiated 150 Date and time transmission ended 151 Channel talk group 152 Unit ID 153 Apparatus ID Ability to link radio traffic data with unit history as an incident, if the communication occurs while a unit is assigned to a call for service. Ability to notify all dispatchers upon depression of an emergency key on the radio. Ability to log radio transmission data in the communications audit files. Ability to time stamp all radio transmission data in the communications audit files. 158 Ability for time stamp to reflect the master clock time stamp. 159 Miscellaneous and yet to be determined Interfaces 160 E-Subpoena (Through Maricopa County) 161 Export data 162 Update Metadata 163 Sync to CAD/RMS system 164 Ability to create a link for Axom Video from BWC 165 Add to report Arizona State University Police Department Interface Functional Requirements 8 of 14

9 166 Officer name 167 Time of upload 168 Ability to define meta-data for BWC video uploads to Evidentce.com. 169 Ability to link BWC footage to report, or auto-populate the call number on the selected footage ISS Incident Management System Ability to transfer CAD call for service information to ISS upon receipt 173 of calls meeting agency defined criteria (e.g., proximity to stadium, type). 174 Ability to recognize if an active or closed call has been updated in CAD. 175 Ability to send the updated call information to ISS. 176 NICE LOGGER/Recording System 177 Ability to capture and link all radio transmissions to call for service. 178 Ability to capture and link all telephone calls to a call for service. 179 Ability to time and date stamp when recording was linked. 180 Ability to capture and link all radio transmissions to call for service. 181 Ability to capture and link all telephone calls to a call for service. 182 Ability to time and date stamp when recording was linked. 183 IBM i2 COPLINK 184 Ability to support a one-way interface from the RMS application to COPLINK. 185 Ability to transfer the following information from the RMS to COPLINK: 186 Subject 187 Vehicle Arizona State University Police Department Interface Functional Requirements 9 of 14

10 188 Incident 189 Property 190 Summary narrative 191 Other agency information 192 Ability send information from the RMS to COPLINK daily. 193 LexisNexis/Coplogic Desk Officer Online Reporting System (DORS) 194 Ability to support a one-way interface to transfer reports generated in DORS to the RMS. 195 Ability to transfer reports into the RMS at agency defined intervals. Ability for the department to review the DORS reports before they 196 are accepted into the RMS (similar to report review/approval process for officer generated reports). 197 Ability to provide a visible indication that the report originated from a DORS entry upon transfer to the RMS. Ability for reports originating from a DORS entry to be available for 198 case assignment alongside officer generated reports in the system's case management module. 199 Internal Campus Video System Lenel/Genetec 200 Physical Security Video and access/duress/intrusion 201 Genetec - Security Center OmniCast 202 Ability to interface to live video streams 203 Ability to match the device to a location and a responsible party or to other pertinent information 204 Ability to link recorded video to police reports which can be stored by CAD as a single record 205 Ability to time, date and stamp recordings 206 Ability to include case report numbers to stored record with the video linked 207 Ability to choose a camera and take over PTZ controls 209 Genetec - Security Center AutoVU 209 Ability to provide plate information in a watch list and update in real time to AutoVu Arizona State University Police Department Interface Functional Requirements 10 of 14

11 210 Ability to interface live captured alert detection to CAD screen 211 Ability to link captured alert detection record with data, time and parking lot information to the police report and case reports 212 Ability to rescan AutoVu recording for plate numbers recorded on a given date or over time and produce a report 213 Lenel - OnGuard Pro 214 Ability to interface to live OnGuardPro Alarm Monitoring 215 Ability to match the device to a location and a responsible party or to other pertinent information 216 Ability to link alarms notification events to police reports and case reports 217 Ability to time, date and stamp events used with cases 218 Ability to rerun alarm events on a given date or over time and produce reports 219 ASAP TO PSAP 220 Ability to link all fire and campus security alarms into a call for service. 221 Ability to auto-populate the call for service with pertinent info. 222 Location 223 Responsible Party information and telephone number 224 Premise telephone number 225 Special Instructions 226 Specific alarm location 227 Alarm reference number 228 Time of alarm activation 229 Item # Other Integrations ASU PD is currently using S M A U Comments 230 Parking & Transit - T2 Systems PARC/FLEX 231 Environmental Health and Safety OnSite EHS Assistant 232 Classroom/Event Scheduling - Ad Astra/Event Management Systems 233 Police Adventos Smartforce Arizona State University Police Department Interface Functional Requirements 11 of 14

12 234 Mass Communications 235 LiveSAFE 236 Guitronics Emergency Call box systems 237 Learning Management - Canvas 238 ASU Enterprise LDAP (any) 239 Active Directory 240 ServiceNow 241 MyASU 242 DUO MFA 243 MuleSoft 244 ASU Mobile 245 AWS 246 AZURE 247 SalesForce 248 Sharepoint - SmartForce 249 LEADS - property database 250 Veoci - Emergency Management Software 251 NICE Logger System, or equivalent 252 AFIS - LiveScan fingerprint system 253 Ability to include a PCN number to case report. 254 Ability to create customized reports 255 Climatec - Fireworks Alarm Monitoring 256 WEB EOC - State and County A data management system used in Planned or Active Incidents Ability to document and share information in county and state site used during emergency/active incidents, or events, that may require equipment or manpower. Other Reporting and Business Intelligence Requirements Item # Reporting and Business Intelligence S M A U Comments 258 Ability to have an API developed to assist with reporting for additional business and intelligence reports. 259 *currently using Crystal Reports with current software for business analytics and intelligence. Arizona State University Police Department Interface Functional Requirements 12 of 14

13 260 Quality Assurance & Quality Improvement Software Please List Other Reporting Options Offered/Available Please List Other Integrations Offered/Available S M A U Comments Arizona State University Police Department Interface Functional Requirements 13 of 14

14 Arizona State University Police Department Interface Functional Requirements 14 of 14