Quotation - Application Data Systems Inc - Police Dept NIBRS

Home Browse Search

ADSi Reporting Tables Request South Bend Police Department 5/18/2018 Request Summary We are requesting ADSi's assistance with both ongoing and recent reporting challenges experienced at the South Bend Police Department. We are interested in receiving a quote for the services outlined in this document, which would result in two primary deliverables: 1. Reporting tables These tables would provide the current state of crime cases with the data properly linked. We think that this may run as a scheduled job,once. per day (loading last three years through previous day) and publish to SQL table(s) mapped in CyberQuery, although we are. open to discussing other possibilities. The attached file contains the fields that we would like to include in the proposed reporting table. 2; Data documentation We request to have the ADSi data dictionary set up in CyberQuery. For code tables, we would like the code and description stored in the SQL table, as joining tables in CyberQuery has been challenging with the information we currently have. We believe that these deliverables will address a number of ongoing and recent reporting challenges, as outlined below. Motivations and Key issues Since the NIBRS implementation, most of our reporting is not working correctly, which has hindered our ability to provide accurate data on demand. We have identified two primary reasons for the. problems: With UCR, South Bend generally had one offense per case. If there were multiple high-level crimes, multiple cases were created: With lower level crimes, they were rolled up to one higher crime. We were able to pull the correct offense in CyberQuery using the latest supplement, which also accounted for reclassification, This logic no longer works because there can be multiple offenses on one case. During the unofficial NIBRS time period (11/1/17 - 12/3V17) cases were classified under both UCR and NIBRS. Therefore even if we wrote logic to address the first issue, since there is no way to differentiate whether the case was input with UCR or NIBRS for this time period, we would not be able to utilize the logic across the board. Historically, we have also had challenges reporting from the Persons table, as it only retains the link to the original report. Now that there are multiple offenses on a case, entered across multiple supplements, it is even more urgent to find a way to handle this challenge. We have discussed this issue with ADS! over email exchanges and feel that it would be very difficult for our team to replicate the "dig" and other custom logic suggested. Considerations • Should be able to handle reclassifications and facilitate reporting of current status • Could include flag to indicate that reclassification occurred Should link properly to persons, including those not on the original report