Paragon Software International, Inc. September 15, 2003

UOCL Code Additions/Changes Documentation

In our ongoing efforts to utilize and conform to codification schemes developed at the state and national levels, we are going to be implementing some changes to the UOCL tables that are used by our CRIME software. Wisconsin CJIS has recently documented additions it has made to the NCIC Uniform Offense Classification (UOCL) codes it uses. In turn, we will be adding these same codes to the UOCL table used in CRIME. The UOCL table in CRIME is considered by us to be vendor controlled table to enable us to provide programs and reports that are able to run consistently at all sites. The ISC table is normally considered a customer controlled table but in this case all of these new UOCL codes should also be mirrored in the criminal portion of the Internal Service Class (ISC) code table, so we will supply these also.

Most of the new codes issued by the state are simple and straight forward to add to the system. However, some of these new codes overlap existing codes that have been in use for years in our system. To merge the conflicting new codes, the existing codes will need to be relocated to a different code. This will involve historical data as well as the tables. A tool has been built that will locate all records in the CRIME data base currently using a specific ISC and UOCL code and change the data to reflect its newly assigned replacement code. This tool will also be useful for those times an agency would like to re-organize its ISC codes for internal reasons. The overlapping codes also affect several reports that look for these codes. These reports will be replaced with new versions that look for the replacement codes. The new report programs will be installed at the same time the codes are changed in the tables. A program will be shipped to customers that will use this tool to perform all of the necessary table, data base, and program changes in one clean pass. This will enable the customer to prepare for the change over and alter and publish changes to its internal documentation regarding the old and new codes. Below is a table of the new codes that overlap existing codes and what the old code will become.

We will contact each customer when the implementation software has been installed and schedule an implementation date. No down time will be required to implement these changes. However, due to the impact on customer internal documentation and procedures, a clean start in the morning of a new day would be advisable. Each customer will need to review their usage of the above listed ISC/UOCL codes to determine actual impact.

If there are any questions, please contact us.