MNI Rebuild Process
MNI Rebuild Process
Table of Contents
Table of Contents PAGEREF _Toc75761590 \h 1
OVERVIEW PAGEREF _Toc75761591 \h 2
ADDITIONAL NOTES PAGEREF _Toc75761592 \h 2
OVERVIEW
To achieve the agency’s desired level of aggregation and fidelity, there are 3 major steps taken to condense name data from both JMS and RMS as much as possible without erroneously combining names:
Using a name key, the initial name consolidation will occur, this is configurable and typically constructed as: last name, first name, (business name if applicable), sex, race, date of birth. If there is a lot of junk data, say a name of “unknown”, or is empty, the row is discarded from the rest of the MNI rebuild.
Then, an attempt is made to match names based on unique identification numbers and are done in the following order. Note that there is an initial attempt to remove all bad ID’s from this process (i.e., a social security number of “N/A”). This comparison is done in the following order (this is configurable per agency request).
Inmate ID number (JMS) / Local ID (RMS if there is an agency practice to support this)
FBI number
SSN
SID
DL
Once these names in both systems have been associated, the most recently occurring name in each collection is inserted into the MNI to represent the name collection.
ADDITIONAL NOTES
Most of these steps and formulas are completely configurable to satisfy each Client’s unique needs.
Each MNI rebuild takes between 0.5 and 4 hours depending on SQL server performance and data volume.
Change Log
Date
Version
Change
6/12/2020
1.0
Initial document
Confidential – ©2025 Executive Information Services. All rights reserved.
This document contains confidential and proprietary information of Executive Information Services. Do not copy, share, or distribute without permission.
Source: MNI Rebuild Process Description.docx