RFP 1900000001266 - QA Attachment - Michigan EBTS 1 of 3.pdf

Michigan Electronic Biometrics Transmission Specifications

November 2017-Revision 2 Table of Contents

INTRODUCTION

DEFINITION OF FIELDS FOR MICHIGAN TYPE 1 RECORD

DEFINITION OF FIELDS FOR MICHIGAN TYPE 2 RECORD

BEST PRACTICE GUIDELINES FOR THE CAPTURE OF MUG SHOT PHOTOS 30

SPECIFICATIONS FOR TRANSMITTING PALM PRINTS

LIVE SCAN TABLES: VALIDATION PROCESS

DESCRIPTION OF FILES

MICHIGAN STATE POLICE: RI-7 ARREST FINGERPRINT CARD

MICHIGAN STATE POLICE: BID-024 ARREST PALM PRINT CARD

INTRODUCTION

This document contains the specifications to successfully transmit biometric data within the State of Michigan. Transactions submitted using these specifications will allow the submission of fingerprints, palm prints, and mug shots to both state and federal databases. This is considered a living document and may be revised as procedures and laws change within the State of Michigan or as directed by the Federal Government. The specifications found in this document are meant to provide a minimum standard to operate in Michigan as a Live Scan vendor. Each NIST record type is broken up within this document into two sections. First, a text document explaining specifications found in the spreadsheets in detail. Second, spreadsheets will provide a snapshot of the field format and requirements within the record and will include information such as field number, identifier, name, conditions, character type, length, number of occurrences, and maximum number of bytes. There are two formats contained within this document. One is a spreadsheet and is ordered in numerical order of the field number, where the text document is ordered alphabetically by mnemonic identifier.

EBTS defines the composition of records within a transaction that is submitted to the Michigan AFIS. All records in a transaction shall pertain to a single subject; data used to identify another individual requires a separate transaction. Data imported from any other system (i.e. a booking system) to a Live Scan must be validated against the tables (pulled from AFIS) and edited to ensure they meet the requirements.

SUGGESTED FEATURES:

This section is based on feedback collected from agencies in order to provide vendors some features or items that seem to be beneficial. These items are not requirements, but may benefit the users of your system in many ways.

• Help shall be provided for each field, whether it is a hover over or displayed on focus.

This would allow the user to know what to type in the field and can prevent them from entering data multiple times. For example: Show format for date of birth (mm/dd/yyyy).

Display race criteria and what is encompassed in each displayed selection.

• When a transaction is rejected, place the transaction in red or have some type of distinction telling the agency their transaction was not accepted.

• Make mandatory fields distinguished. This allows users to see the fields they must complete. Please use the EBTS to ensure the mandatory fields are correctly noted.

• Allow some form of search or sort option on the “main” screen so users can search for a name, TCN, or other criteria in order to locate transactions.

• Allow the fingerprint being captured to be shown on the screen at the time of capture so the user can determine whether they need to re-take the image at that time.

• Particular ORI’s can be defaulted on the device per the agencies request, but all ORI’s should be available for use.

• Make palm prints mandatory for the CAR-Arrest Build type of transaction or all CAR- TOT’s.

• Ensure palm prints are allowed for MAP type of transactions as they are applicable to the sex offender registration MAP prints.

DEFINITION OF FIELDS FOR MICHIGAN TYPE 1 RECORD

The following paragraphs describe the data contained in fields for the Type-1 logical record.

Each field shall begin with the number of the record type, followed by a period, followed by the appropriate field number, followed by a colon. Multiple information items within a field or subfield shall be separated by the US separator, multiple subfields shall be separated by the RS separator, and information fields shall be separated by the GS separator. Immediately following the last information field in the Type-1 logical record, an FS separator character shall be used to separate it from the next logical record.

1.03 CNT - File Content

This mandatory field shall list each of the logical records in the logical file by record type. It also specifies the order in which the remaining logical records shall appear in the logical file. It shall consist of one or more subfields. Each subfield shall contain two information items describing a single logical record found in the current logical file. The subfields shall be entered in the same order in which the logical records shall be transmitted. When more than one subfield is used, the RS separator character shall be entered between the subfields.

The first subfield shall relate to this Type-1 transaction record. The first information item within this subfield shall be the single character indicating that this is a Type-1 record consisting of header information (the numeral "1" is used).

The second information item of this subfield shall be the sum of the Type-2 plus Type-4 plus Type 10 records contained in this logical file. This number is also equal to the count of the remaining subfields of the CNT Field. The US separator character shall be entered between the first and second information items.

The remaining subfields of the CNT Field pertaining to the Type-2, Type-4, and Type-10 records contained in the file shall each be comprised of two information items. The first information item shall be a single character chosen from table 1, which states the record type. The second information item shall be the IDC associated with the logical record pertaining to that subfield.

The IDC shall be a positive integer equal to or greater than zero. The US character shall be used to separate the two information items.

1.07 DAI - Destination Agency Identifier

This mandatory field shall contain the identifier of the administration or organization designated to receive the transmission. This will be the ORI number for the Michigan State Police AFIS Server.

1.05 DAT - Date

This mandatory field shall contain the date that the transaction was initiated. The date shall appear as eight digits in the format CCYYMMDD. The CCYY characters shall represent the year of the transaction; the MM characters shall be the tens and units values of the month; and the DD characters shall be the day in the month. For example, 19920601 represents June 1, 1992.

The complete date shall not exceed the current date.

1.01 LEN - Logical Record Length

This mandatory ASCII field shall contain the total count of the number of bytes in this Type-1 logical record. Field 1.01 shall begin with “1.01”, followed by the length of the record including every character of every field contained in the record and the information separators.

1.11 NSR - Native Scanning Resolution

This mandatory field shall specify the nominal scanning resolution of the AFIS or other image capture device supported by the originator of the transmission. This field permits the recipient of this transaction to send respond data at a transmitting resolution tailored to the NSR (if it is able to do so) or to the minimum scanning resolution. This field shall contain five bytes specifying the native scanning resolution in pixels per millimeter. The resolution shall be expressed as two numeric characters followed by a decimal point and two more numeric characters (e.g., 20.00) This field is needed because the interchange of fingerprint information between systems of the same manufacturer may, in some instances, be more efficiently done at a transmitting resolution equal to the native scanning resolution of the system rather than at the minimum scanning resolution specified in this standard.

1.12 NTR - Nominal Transmitting Resolution

This mandatory field shall specify the nominal transmitting resolution for the image or images being transmitted. This field shall contain five bytes specifying the transmitting resolution in pixels per millimeter. The resolution shall be expressed as two numeric characters followed by a decimal point and two more numeric characters (e.g., 20.00). The transmitting resolution shall be within the range specified by the transmitting resolution requirement.

1.08 ORI - Originating Agency Identifier

This mandatory field shall contain the identifier of the administration or organization originating the transaction. This will be the ORI# of the Live Scan device initiating the transaction.

1.09 TCN - Transaction Control Number

This mandatory field shall contain the Transaction Control Number as assigned by the Live Scan agency or MSP. A unique control number shall be assigned to each transaction. For any transaction that requires a response, the respondent shall refer to this number in communicating with the originating agency. This shall be an eleven-byte, alpha-numeric field.

The TCN format is llyyssssssc.

ll: livescan ID (assigned by MSP) yy: year ssssss: sequential number c: check character

The check formula is the same as the formula used for MSP SID. Alphabetic characters in the TCN are given the following values:

Each position of the TCN is given a weight value.

Position 1 2 3 4 5 6 7 8 9 10 Weight Value 5 4 3 2 7 6 5 4 3 2

A=1 F=6 K=2 P=7 U=4 B=2 G=7 L=3 Q=8 V=5 C=3 H=8 M=4 R=9 W=6 D=4 I=9 N=5 S=2 X=7 E=5 J=1 O=6 T=3 Y=8 Z=9

Multiply each alphabetic or numeric value by the positional weight value. Calculate the sum of these products. Divide the sum by 11 and use the remainder to form the check character.

Assign the check character from the following values:

1.10 TCR - Transaction Control Reference

This field shall be used in responses to refer to the Transaction Control Number of a previous transaction involving an inquiry or other action that required a response. This is a 10 to 40 alpha numeric field. Not visible to the end user.

1.04 TOT - Type of Transaction

This mandatory field shall contain an identifier, designating the type of transaction and subsequent processing that this logical file should be given. There are several types of ten-print electronic submissions that will be accepted by the Federal Bureau of Investigation (FBI). The particular type of transmission is identified in the Type of Transaction (TOT) Field in the Type 1 record that is used with each transaction. The following are the TOTs for ten-print submissions for the State of Michigan and the FBI:

Court Build YES

*Court Builds are only allowed upon MSP approval (only Michigan Department of Corrections (MDOC) is currently eligible)

CAR - Criminal Ten-print Submission (Answer Required) This transaction is a criminal arrest fingerprint submission for which a response will be returned to the Live Scan agency. It contains ten rolled fingers, four plain impressions, and palm impressions if scanner allows, as well as information relative to an arrest or to custody status.

The biographical data and fingerprint images are used to determine potential candidates with criminal records at the State and the FBI. This TOT is also used for inquiry on criminal suspect or informant, in which case arrest, custody, or supervisory data may or may not be present.

Under this TOT, if the record is to be recorded in the Criminal History Records (CHR), the Retention Code (RET) in the Type-2 record must be set to yes (Y). If the record is for identification only, not record building, the Retention Code must be set to no (N). The fingerprint images of the candidates will be compared either by computer or manually with those submitted and an identification or non-identification decision is determined. If the retention code is set to yes (Y), then the criminal history is updated and a response is returned.

MAP - Miscellaneous Applicant Civil These submissions are for applicant prints. These prints will be retained and transmitted to Michigan, as well as the FBI. The record is updated and a response is returned to a designated recipient. Retention is set to yes and should be locked.

1.02 VER - Version Number

This mandatory four-byte ASCII field shall be used to specify the version number of the standard implemented by the software or system creating the file. The format of this field shall

TOT TRANSACTION RETENTION

CAR Criminal Arrest Build YES CAR Identification (ID) Only NO MAP Miscellaneous Applicant Civil YES CAR Court Build YES

0=A 3=J 6=M 9=W 1=E 4=K 7=P 10=X 2=H 5=L 8=T consist of four numeric characters. The first two characters shall specify the major version number. The last two characters shall be used to specify the minor revision number. The initial revision number for a version shall be "00". The entry in this field for this 1993 approved standard shall be "0200". The original 1986 standard would be considered the first version or "0100".

DEFINITION OF FIELDS FOR MICHIGAN TYPE 2 RECORD

2.216 ADC - Arrest Disposition Code

This is a data field within the Michigan Arrest Segment (MAS). For this field, the three letter code from the following table is used to describe the arrest disposition as known at time of transmission to the State. Vendors must label these codes on the Live Scans exactly as they are below:

DESCRIPTION CODE

Charged For Prosecution CHG Juvenile Petition Issued JUV

Notice to Appear NTA Requesting Petition REP Requesting Warrant REW

2.019 AKA - Aliases

This field contains alias names of the subject. The format is the same as described in the NAM field and the same 30-character limit applies to the field length. Up to ten aliases may be provided, separated from one another by the (R

S) character. Duplicates are not allowed. (See Name Section for details).

2.084 AMP - Amputation

This field is used if the subject being fingerprinted is missing a finger or if a finger is bandaged.

If either condition is met, then the field becomes mandatory.

2.226 AON - RQID Type Flag

Data in this field is a valid code which identifies the source of the requester number (RQID) in an applicant record submission. This table must be maintained, but not displayed to the end user on the Live Scan. It should auto populate based on the reason code selected. Vendors must populate this field with the exact terminology listed below. The user shall not be able to alter this field.

Agency ID number assigned by MSP A

LEIN Assigned ORI O No Submission- Print Card only N

2.216 ARO - Arresting/Warrant Holding Agency ORI Number

This is a data field within the Michigan arrest segment (MAS). Data in this field is comprised of a valid nine character Michigan agency identifier (ORI). It must identify the law enforcement agency holding or seeking an arrest warrant or juvenile petition, or ordinance violation.

The Michigan Attorney General is using ORIs that end in ‘A’. These are valid ORIs with arrest powers and are listed in the Utility Server table ‘orispecialyyyymmdd’

2.216 ATF - Arrest Type Flag

This is a data field within the Michigan Arrest Segment (MAS). For this field, the alpha code from the following table is used to describe the reported arrest to be a felony, misdemeanor, ordinance, or civil violation.

FELONY F

MISDEMEANOR M

ORDINANCE O

CIVIL C

2.006 ATN - Attention Indicator

This field shall contain a designation of the individual to whose attention a response is to be directed. When including the recipient’s rank/or using initials for first and/or middle name, periods shall not be used (e.g., Det. J. Q. Public shall be entered as DET J Q PUBLIC).

2.221 CCN - Court Count Number

This data field is a subfield of the Michigan Court Segment (MCS). The data is numeric with a maximum length of 3 characters. The number corresponds to the times a defendant is adjudicated with the same crime code.

2.221 CDC - Court Disposition Code

This data field is included in the court segment of the record (MCS). Data in this field is a three character alpha code from the following table to report the court conviction disposition for the case. The disposition is taken from the commitment to jail court form in the convicted by column.

ADJUDICATION ADJ

PLED NOLO CONTD NOC

FOUND GUILTY MENTALL ILL GMI

PLED GUILTY MENTALLY ILL PMI

DEFERRED-HYTA DPY

DEFERRED-7411 DPD

DEFERRED-DOMESTIC ASSAULT DPS

DEFERRED-PARENT. KIDNAPPING DPK

FOUND GUILTY GTY

PLEAD GUILTY PLG

2.221 CDD - Court Disposition Date

This data field is included in the court segment of the record (MCS). This field contains the date a court count was disposed of by the court. The CDD shall appear as an eight-digit number in format of CCYYMMDD. The CCYY characters shall represent the year of the transaction; the MM characters shall be the tens and units values of the month; and the DD characters shall be the day in the month. For example, 19920601 represents June 1, 1992. The complete date shall not exceed the current date. The year must not be prior to the year in the CTN (Criminal Tracking Number).

2.221 CFN - Court File Number

This data field is within the Michigan Court Segment (MCS). The data in this field is the number assigned to a file/case/subject during the adjudication process. This is not the same as the originating case agency number/report/incident number, but it is specifically assigned by the court.

2.216 CGO - Prosecuting Agency ORI

This is a data field within the Michigan Arrest Segment (MAS). Data in this field is comprised of a valid nine character Michigan agency identifier (ORI) usually ending with an “A”. It must identify the prosecuting agency for the reported case. This field is mandatory when using the Arrest Disposition Codes (ADC) of REW, REP, CHG, and JUV. The field is optional when the Arrest Disposition Code is equal to NTA.

2.221 CIT - PACC Charge Code

This data field is included in the Michigan Court Segment (MCS) of the record. The data in this field is taken from the commitment to jail court form identified as the charge code. The code is from the PACC code table and is provided in lieu of the charge description. Local edits are recommended, but are not mandatory.

2.216 CNT - Charge Counts

This is a data field within the Michigan Arrest Segment (MAS). The data is numeric with a maximum length of 3 characters. The number corresponds with the number of times a defendant is charged with the same crime defined by data provided in the CTC, MIC, GOC, and ATF fields for a case.

2.242 CON - Contact Information

This data field is alphanumeric/ special and designed to capture name, phone number and e-mail of a person. Field may be up to 95 characters in length. This information will be mandatory based on the fingerprint reason code(s) listed in NIST spreadsheet.

CNM - Contact Name This data field is alphanumeric/ special with the name to be entered in the format of last name followed by a comma and then first name. This field will allow both characters and numbers along with spaces to accommodate suffixes such as Jr., III, etc. Any of these suffixes should be included after the last name and before the comma. The limit for length on this field will be 40 characters. Any spaces, commas or periods will go towards the limit in length.

CPH - Contact Phone Number This data field is numeric 10 digit field that will capture a common ten digit phone number.

Vendors may use a mask but should transmit only numbers when sending to AFIS.

CEM - Contact Email Address This data field is alphanumeric/ special and must be formatted as a valid e-mail address.

This field will be limited to 45 characters.

2.225 CTL – COURT LITERAL

This data field is alphanumeric with a maximum length of 24 characters. This field is the literal name that corresponds with the 2.216 JUDORI Court Jurisdiction/Arraignment ORI# field.

2.221 CSR - Court Sentence Remarks

This data field is included in the court segment of the record (MCS). The data is free text information up to 90 characters in length which describes the court sentence. This information will be taken from the commitment to jail court form and will identify the length of the jail term in days, months, or years.

2.216 CTC - Charge Type Code

This is a data field within the Michigan Arrest Segment (MAS). Data in this field is a valid single character numeric code that identifies which table of codes is used to describe the arrest charge in the MIC field of this arrest segment.

MAC 1

PACC 2

AFC 3

Note: It is mandatory that these tables, amongst other tables, are downloaded and/or updated on a regular basis by the vendor in order to keep the accuracy of all submissions on Live Scans adequate.

2.216/2.221 CTN - Criminal Tracking Number This is a data field in the Michigan Arrest Segment (MAS) and the Michigan Court Segment (MCS). Data in this field identifies the prosecutor assigned criminal tracking number for the reported case. This field is mandatory for the Michigan Arrest Segment when the Arrest Disposition Code is charge (CHG) or juvenile (JUV) and the Arrest Type Flag (ATF) is F or M.

At the time of booking, this number will be available off the authorized warrant. This field is not required for a CHG or JUV Arrest Disposition Code if the Arrest Type Flag is O. It is also not required for the Arrest Disposition Codes (ADC) of REW, REP, or NTA. This field is not mandatory for the Michigan Court Segment (MCS) when reporting ordinance violations from the court. This field is mandatory for the Michigan Court Segment when there is a criminal tracking number recorded on the Commitment to Jail court form. The number is comprised of 12 numeric characters. The first two digits are the county code, digits three and four are the year, the next six digits is a sequential number, and the last two digits is the defendant’s number. If no warrant is issued prior to the booking, this field is not required.

2.213 DLN - Driver’s License Number

The driver’s license number cannot be longer than 20 characters and must contain at least one number (all alpha is not allowed). Any character such as a hyphen may be used to break up the number on the GUI, but these characters will not be included in the NIST file. When a Michigan license is entered, it must consist of one alpha character followed by 10 or 12 numbers. If the driver’s license state is entered then the driver’s license number or PID is mandatory. If a DLN or PID is not available, the DLS should not be entered.

2.214 DLS - Driver’s License State

This field is a two-character code for the state where the driver’s license was obtained. Data within this field is a two-character alpha code that identifies the state that issued the license.

The code is obtained from the NCIC table of valid state codes. (See State & Country Codes Section). If the driver’s license number is entered, the driver’s license state is mandatory.

2.045 DOA - Date of Arrest

This field contains the date of arrest. The date shall appear as an eight-digit number in the following format CCYYMMDD. The date of arrest is mandatory when submitting a CAR transaction regardless of retention value or the existence of MAS versus MCS. Default to current date when transaction is created but do not lock.

2.022 DOB - Date of Birth

This field contains the date of birth. It is entered as an eight-digit number in the following format CCYYMMDD. Up to five multiple occurrences of this field may be listed to indicate different dates of birth, with each entry being separated by the (R S) separator character. Date of Birth is required; zeros are not valid in Michigan. For CAR transactions and MAP transactions, most reason codes the age range is 7 to 99. For the Vulnerable or Impaired Persons (VIP) MAP reason code, the age range is 2-99.

2.216 DOO - Date of Offense

Each OCA should have a corresponding date (DOO), if available. The DOO shall appear as an eight-digit number in the same format as the DOB. The DOO shall be separated from the ATF by the (U

S) separator character. A DOO is prohibited without a corresponding OCA. If a DOO is not present, a blank followed by a (U

S) character separator shall be used.

2.038 DPR - Date Printed

This field contains the date that the subject was fingerprinted. The format shall be the same as that specified for the DOB field. This field should be auto populated by the device with the current date.

2.031 EYE - Color of Eyes

For this field, the three-letter code from the following table is used to indicate the subject’s color of eyes.

2.014 FBI - FBI Number

This field contains the subject’s FBI number, if known. A valid FBI number shall be no more than nine alphanumeric characters. This is also known as the Universal Control Number (UCN).

2.228 FPR - Fingerprint Reason

This data is a valid code (see Fingerprint Reason Code Table) which identifies the type of employment or licensing clearance for which the applicant fingerprints are submitted. Not all codes on the Fingerprint Reason Code Table are valid for electronic submission.

*These codes should be configurable to accommodate changes in laws and processing

EYE COLOR CODE

BLACK BLK

BLUE BLU

BROWN BRO

GREEN GRN

HAZEL HAZ

MAROON MAR

PINK PNK

UNKNOWN XXX

criteria instead of embedded in compiled code or internal database structures. i.e. When a change is mandated by a controlling authority to make a FPR transmittable via live scan (vs. print only), this should be easily done in configurable file (.ini xml etc.)

2.216/2.221 GOC - GENERAL OFFENSE CODE

This is a data field within the Michigan Arrest Segment (MAS) or the Michigan Court Segment (MCS). In this field, a one character code from the following table is used to describe a specific charge in an arrest or court segment. A valid code must be reported in the CIT field in association with this field.

For MAS, GOC is only available if the arrest disposition code is CHG or JUV.

ATTEMPT A

CONSPIRACY C

SOLICIT S

2.032 HAI - HAIR COLOR

In this field, the three-letter code from the following table is used to indicate the subject’s color of hair.

2.027 HGT - HEIGHT

This field contains the subject’s height as a three-character value. Reported in feet and inches, the first (leftmost) digit is used to show feet while the two rightmost digits are used to show the inches between 00 and 11. The height can range from 2’00” to 7’11”. If the height is unknown, HAIR COLOR CODE

BALD BAL

BLACK BLK

BLOND or STRAWBERRY BLN

BLUE BLU

BROWN BRO

GRAY or PARTIALLY GRAY GRY

GREEN GRN

ORANGE ONG

PINK PNK

PURPLE PLE

RED or AUBURN RED

SANDY SDY

UNKNOWN XXX

WHITE WHI

an estimate must be entered. Zeros are not valid in Michigan.

2.056 ICO - IDENTIFICATION COMMENT

Data in this field is free text data up to 50 characters. Additional miscellaneous identification remarks may be entered in the field. The first character may not be a blank.

2.002 IDC - IMAGE DESIGNATION CHARACTER

The image designation character shall be a sequentially assigned positive integer starting from zero and increasing by one for each finger position, image, or type-2 record present. Each IDC value matches a value in the content (CNT) field of the type-1 message header.

2.067 IMA - IMAGE CAPTURE EQUIPMENT

This field is used to log the make, model, and serial number of the equipment used to acquire images. It is a grouped field, comprised of three subfields: the Make (MAK), Model (MODL), and Serial Number (SERNO) of the acquisition device, separated by the separator character.

2.210 ITB - IMPRESSION TAKEN BY

This field contains the name of the person taking the fingerprints. Up to 30 characters are allowed in the same format as described for the NAM field. This is to be populated by the logon information of the user. The field does not need to be on the GUI. The live scan software will automatically fill in the content with the information related to the current logged-on user.

Having an automatic log out after a certain time period will help to prevent people using the device under another user’s login.

2.216/2.221 JUDORI - COURT JURISDICTION/ARRAIGNMENT ORI NUMBER

This is a subfield within the Michigan Arrest Segment (MAS) or Michigan Court Segment (MCS).

Data in this field is comprised of a valid nine character Michigan agency identifier (ORI). Within the Michigan Arrest Segment, this field is always mandatory; it must identify the court of jurisdiction for the case. When the ADC is JUV or REP, the ORI must be a juvenile/family court ORI. Within the Michigan Court Segment, this field is always mandatory. It must identify the court that appears on the judgment of sentence form as the sentencing court.

2.001 LEN - LOGICAL RECORD LENGTH

This field contains the length of the logical record specifying the total number of bytes, including every character of every field contained in the record. The length of the LEN is included in the total length of the record.

2.211 LSI - LIVE SCAN ID# (OPERATOR)

This field contains the assigned operator identification code used to log on to the Live Scan terminal. This code must be a unique value and cannot be re-issued for seven years. This is used in CCH and must be identifiable to a person. This field must be a minimum of 1 character long and a maximum of 12 characters long. Employee numbers or badge numbers are acceptable. Alpha characters are allowed. Spaces and zeros may be used to fill characters if needed. This field is similar to the ITB (2.210) in that it is automatically captured from the login data. This field need not be on the GUI. The live scan software will populate the database on the current user. Having an automatic log out after a certain time period (as indicated in the CJIS policy) will help to prevent people using the device under another user’s login.

2.216 MAS - MICHIGAN ARREST SEGMENT

This field is a set of data that reports an arrest. Up to 15 occurrences of the entire MAS are allowed. Each occurrence shall be separated by the (R S) separator. This allows for reporting of

15 different cases with 15 different warrant holding agencies, or 15 different arrest charges for the same agency. Each set must contain all data fields but the optional data may be blank. The data set is comprised of the date of offense (DOO), warrant holding agency (ARO), agency case number (OCA), charge counts (CNT), general offense code (GOC), charge code (MIC), charge code type (CTC), arrest type flag (ATF), arrest disposition code (ADC), criminal tracking number (CTN), prosecutor ORI (CGO), and ORI of court of jurisdiction (JUDORI). This segment is mandatory, unless the court segment is provided or the retention code (RET) is set as No.

2.221 MCS - MICHIGAN COURT SEGMENT

Michigan Court Segments/Builds should only be viewable on Michigan Department of Corrections’ Live Scans. Up to 15 occurrences of the entire MCS are allowed. Each occurrence shall be separated by the (R S) separator. This allows for reporting of up to 15 convicted charges from the same court case or 15 different court cases. Each set must contain all data fields but the optional data may be blank. The data set is comprised of criminal tracking number (CTN), disposition date (CDD), court jurisdiction/arraignment ORI (JUDORI), court file number (CFN), count number (CCN), convicted charge code (CIT), general offense character (GOC), ordinance flag (ORF), coded disposition (CDC), and sentence or remarks (CSR). The court segment is mandatory only when there is no data for the arrest segment and the Retention Code (RET) is set as Y.

2.216 Michigan Arrest Codes - MAC/PACC/AFC

The data in this field is a code, that when translated, identifies the reported arrest charge. There are three types of codes valid for use in the field. Data in this field also requires an entry in the Charge Type Code (CTC) data field to identify the code type used. Following is a description of the codes allowed to be used in this field.

MAC – Michigan Arrest Code. This is the code that is created and maintained on CCH. It is not a MICR code. In the case where CTC = “1” and the booking system sends Live Scan software a value that is not in the table provided by the unit in charge of Live Scan, the Live Scan software will do one of the following:

1. Do Not import the incorrect value, leave it blank forcing the Live Scan operator to input a correct value; or

2. Import the incorrect value and implement validation edits to get a valid code in this field. Leaving a blank is not valid and should be found in the validation edits.

PACC – Prosecuting Attorneys’ Coordinating Council. This code is created and maintained by the Prosecuting Attorneys’ Association of Michigan. This code is mandatory when entering charge (CHG) or juvenile (JUV) arrest disposition code (ADC) when ATF = F or M. This code is optional when entering charge (CHG) or juvenile (JUV) arrest disposition code (ADC) and the

ATF = O.

AFC – Arrest File Class. This is a general code used to report arrest data.

2.017 MNU - MISC. IDENTIFICATION NUMBER

If there are any miscellaneous identification numbers, they shall be entered in this field. The format of the data shall be a two-letter identifying code, followed by a hyphen (-), followed by the number itself. The following table lists the acceptable two letter identifying codes. Interspersed blanks are invalid. Types of numbers not listed in the following table (such as driver’s license) shall not be entered. Only U.S. Passport numbers shall be entered; foreign numbers shall be ignored. The size of the MNU is limited to 15 characters. As many as four miscellaneous numbers may be included in this field. Each MNU shall be separated from the next by the (R S) separated character. No duplicates are allowed.

IDENTIFYING AGENCY CODE

AIR FORCE SERIAL NUMBER AF

ALIEN REGISTRATION NUMBER AR

AIR NATIONAL GUARD SERIAL NUMBER, ARMY SERIAL

NUMBER, NATIONAL GUARD SERIAL NUMBER

AS

CANADIAN SOCIAL INSURANCE NUMBER CI

U. S. COAST GUARD SERIAL NUMBER CG

MARINE CORPS SERIAL NUMBER MC

MARINE’S DOCUMENT OR IDENTIFICATION NUMBER MD

RCMP IDENTIFICATION OR FINGERPRINT SECTION NUMBER MP

NAVY SERIAL NUMBER NS

ORIGINATING AGENCY IDENTIFIERS OA

PASSPORT NUMBER ( U.S. ONLY) PP

PORT SECURITY CARD NUMBER PS

SELECTIVE SERVICE NUMBER SS

VETERANS ADMINISTRATION CLAIM NUMBER VA

SPECIAL CASES

• IF “AF” OR “AS” IS ENTERED, ALL CHARACTERS FOLLOWING MUST BE

NUMERIC.

2.222 MSM - MICHIGAN SCARS, MARKS, TATTOOS

This field is used for scars, marks, and tattoos which are located on the subject of the record.

This field must contain a valid 3-character code used in LEIN. A maximum of nine occurrences is allowed and must be separated by a (R

S) separator. Duplicates are not allowed. See Scars, Marks & Tattoos Section for a complete list of valid codes.

2.018 NAM - NAME

This field contains the name(s) of the subject. The format shall be the surname followed by a comma (,) followed by the given name(s), which are separated by a space. A hyphen is only allowed in the surname.

The NAM field of the Type-2 Record, and any aliases, must be entered in the following order:

mandatory surname; mandatory comma; space (optional); mandatory first name or initial; space (include only if middle name or initial will follow); middle name(s) or initial(s) if any; mandatory space after each middle name or initial except last one; and suffix denoting seniority (Jr., II, etc.)

if any. For example:

Smith, John Henry Smith, John Henry Jr Smith, John H Smith, J H Sr

A comma is necessary to separate the surname and the first name or initial, and the space following the comma is optional. A space following the first name or initial, middle name or initial is mandatory if the name or initial is not ending the NAM field.

Complete names are to be used if available. No unit of a name or alias should be abbreviated unless the complete name exceeds the 30-character maximum NAM field length. Should a name exceed the maximum field length, the initial of the middle name should be used rather that the full middle name. When entering records for person with only one name, use the only name as the surname and an alphabetic X as the first name.

Abbreviations such as ‘FNU’, “IO”, “LNU”, “MNU”, “NMI”, and “NMN” should not be used in place of the X.

Titles or degrees of individuals, including foreign titles and degrees, and their abbreviations; for example, Mr., Miss, Mrs., Ms., Prof., Ph.D., Capt., Lt., D.D.S., Dr., Rev., etc., are not used in the NAM Field.

Names with apostrophes (O’Neal, O’Boyle) should be condensed, eliminating the apostrophe.

O’Neal, Joseph ONEAL, JOSEPH

COMPOUND SURNAMES

For compound surnames (paternal and maternal), the full name including both surnames, if known, should be entered in the NAM Field. For example:

Subject’s Name: Jose Rodriguez-Gonzalez (hyphenated) Entered Name: RODRIGUEZ-GONZALEZ, JOSE

Subject’s Name: Jose Rodriguez Gonzalez (non-hyphenated) Entered Name: RODRIGUEZGONZALEZ, JOSE Subject’s Name: Jane Smith-Jones (hyphenated) Entered Name: SMITH-JONES, JANE

*Subject’s Name: Jane Smith Jones (not hyphenated) Entered Name: SMITH JONES, JANE

*Subject’s Name: Jose Rodriguez y Gonzalez (Spanish letter Y used as a separator) ** Entered Name: RODRIGUEZ Y GONZALEZ, JOSE

*Each surname component of the full name must be entered individually as a separate alias in a supplemental record entry to ensure the possibility of a hit should either surname be inquired upon.

**When each surname component is entered individually as an alias, the letter Y should not be entered. Using the example, the following two aliases would be appended to the base record:

AKA/RODRIGUEZ, JOSE

AKA/GONZALEZ, JOSE

When entering a hyphenated name in Michigan, the criminal history update program will automatically enter each surname component individually as an alias. Using the above hyphenated name as an example (Rodriguez-Gonzalez), the following two aliases would be appended to the base record:

RODRIGUEZ, JOSE

GONZALEZ, JOSE

ASIAN NAMES

The last unit of an Asian name should be entered as the master last name. Each of the other units should be entered as a surname in the AKA Field, with the other units shown as first and middle name. For example:

NAM/NAI, DONALD LEE

AKA/LEE, DONALD NAI

AKA/DONALD, LEE NAI

2.009/2.216 OCA - ORIGINATING AGENCY CASE NUMBER

This field contains the 1-12 character originating agency case identifier (OCA) that has been assigned by this agency. The case number must not equal ZERO or all ZEROES, “NONE”, ”UNKNOWN”, “UNK”, “UNKN”, “N/A”, “NA”, “MSP”, “ “, “X”, “Y”, “Z”.

2.221 ORF - ORDINANCE FLAG

This field must be filled with either a blank to indicate that the charge code is a state statute violation, or a "Y" to indicate the charge code substantially corresponds to state statute as an ordinance violation. The ORF use provides the criminal history record with a notation that the violation was ordinance-related and also provides the statute code to which it corresponds substantially.

2.224 PAL – PROSECUTING ATTORNEY LITERAL

This data field is alphanumeric with a maximum length of 24 characters. This field is the literal name that corresponds with the 2.216 CGO Prosecuting Agency ORI# field.

2.036 PHT - "PHOTO AVAILABLE" INDICATOR

The photo available indicator is used to identify if there are photos attached in the NIST record.

This field should contain a "Y"; otherwise, the field shall be omitted. The content of this field will be determined by the existence or lack-of the type 10. This field need not be on the GUI. When it is on the GUI, the live scan software will override any user input based on the true content of the file that is sent to the state. If this field does not match the record content, the transaction will be rejected.

2.020 POB - PLACE OF BIRTH

The subject’s place of birth shall be entered in this field. Indicate in the POB field the state, territorial possession, province (Canadian), or country of birth. The appropriate two-letter abbreviation shall be used as listed in part IV of the NCIC code manual (See State & County Code Section). The criteria listed below shall also be considered when assigning POB:

IF THE FOLLOWING CONDITIONS EXISTS CODE

POB stated as state and country and applicable code not contained in code table; or city can be ascertained as not being located in the United States; or foreign POB and applicable code not contained in code table

YY

POB stated as only city and city can be ascertained as being located in the United States

US

POB is Mexico or any Mexican state or province not in code table MM POB is “Mexico, Mexico” MX POB is unknown XX

2.035 PPA - PALM PRINTS AVAILABLE INDICATOR

If palm prints are available, this field shall contain a “Y”; otherwise, the field is omitted. The content of this field will be determined by the existence or lack-of the type 15. This field need not be on the GUI. When it is on the GUI, the live scan software will override any user input based on the true content of the file that is sent to the state.

2.215 PRN - PRISON NUMBER

Data must be numeric. A minimum of one digit and a maximum of seven digits are allowed.

The value of the number cannot be less than 4. This number is the client number assigned to persons entering the Michigan Department of Corrections prison system.

2.025 RAC - RACE

This field is used to indicate the race of the subject. The criteria for each race code must be displayed, so the user knows what options are available for what code. Use the predominate race code from the following table:

IF SUBJECT IS ENTER CODE

Chinese, Japanese, Filipino, Korean, Polynesian, Indian, Indonesian, Asian Indian, Samoan, or any other Pacific Islander (Displayed as “Asian”)

A

A person having origins in any of the black racial groups of Africa (Displayed as “Black”)

B

American Indian, Eskimo, or Alaskan native, or a person having origins in any of the 48 contiguous states of the United States or Alaska who maintains cultural identification through tribal affiliation or community recognition (Displayed as “Native American”)

I

Of indeterminable race (Display as “Unknown”) U Caucasian, Mexican, Puerto Rican, Cuban, Central or South American, or other Spanish culture or origin, regardless of race (Displayed as “White/Latino”)

W

2.041 RES - RESIDENCE OF PERSON FINGERPRINTED

The subject’s residential address may be entered in this field as alphanumeric data. It is mandatory that a comma be entered after the street address, city, and state. The address data must be complete. Incomplete address information being sent in with the NIST will be rejected.

Vendors are required to break this field into sub-fields on the graphic interface (GUI). Then combine the sub-fields into the NIST standard field RES (2.041) with the commas included between sub-fields. Blank sub-fields are not valid. User entered commas in sub-fields are not allowed. Maximum length of this field including commas is 120 characters. Vendors are required to trim multiple spaces from the sub-fields when concatenating. Single spaces are not acceptable.

Example of RES field after concatenating:

Acceptable: 7150 Harris Drive,Lansing,MI,48913 Unacceptable: 7150 Harris Drive , Lansing , MI, 48913

The length of the sub-fields will be up to:

-street address 55 characters -comma 1 -City 50 characters -comma 1 -State 2 characters -comma 1 -Zip Code 10 characters Total 120 characters

2.005 RET - RETENTION CODE

This is an alpha field indicating whether the arrest or applicant information submitted is to be retained in the Michigan AFIS and Criminal History Record System. A “Y” is used to indicate yes for a reportable record; an “N” to indicate no for identification only. This field is dependent upon what TOT selection is made. The user shall not be able to alter this field and this field shall not be displayed on screen. See TOT field for proper retention code selections.

2.219 RQID - Requestor ID

When submitting applicant prints, the agency receiving the response for the service must be identifiable in the transaction. Arrangements are made with the Michigan State Police Criminal Justice Information Center (CJIC) and an agency ID number is assigned for use, or an ORI is authorized.

Requestor ID Check Digit algorithm

The following is the check digit algorithm for calculating the check digit for generated requestor (agency) IDs.

1. The requestor ID is zero-filled to the left.

2. The characters in positions 1 (starting counting from the left) through 8 are multiplied by the following numbers and the products totaled.

Character in position number Multiplied by 1 and 7 5 2 and 8 4 3 3 4 2 5 7 6 6

3. The total product is divided by 9 and the remainder determines the check digit value as follows:

Remainder Check Digit 0 A 1 E 2 H 3 J 4 K 5 L 6 M 7 P 8 T Examples:

1340 gets a check digit of “A” 1479 gets a check digit of “J” 3556 gets a check digit of “E”

2.007 SCO - SEND COPY TO - ORIGINATING AGENCY IDENTIFICATION NUMBER

The purpose of this field is to indicate requirements for production of additional response(s) for a receiving agency other than the contributor. It shall contain the NCIC-assigned originating agency identifiers (ORI’s) for agencies that are to receive a copy of the response. Each ORI consists of 9 bytes of alphanumeric data. At the option of the transmitting agency, the ORI may be expanded to a size of 19 characters, with 10 characters appended to the end to assist in proper routing of the responses. Each entry shall be separated from the next by a (R

S) separator character.

2.024 SEX - GENDER

This field is used to report the gender of the subject. The entry is a single character selected from the following table:

IF FOLLOWING CONDITION EXISTS ENTER CODE

Subject’s gender reported as female F Subject’s gender reported as male M

Unknown U

2.015 SID - STATE IDENTIFICATION NUMBER

This field contains the Michigan state identification number. Embedded blanks are not permitted.

2.016 SOC - SOCIAL SECURITY NUMBER

This field contains the subject’s social security number, if known. This number shall be entered as nine characters with no embedded punctuation. Up to four social security numbers may be entered. Each shall be separated from the next by the (R

S) separator character. No foreign social security numbers shall be used. The number must contain 9 digits. The number cannot begin with a 9. The fourth and fifth digits cannot both be zero. The number cannot be less than 001010001. The social security number cannot be duplicated in the transmitted record.

2.212 TIM - TIME PRINTED

The time printed is a 4 digit number in hours and minutes when the prints were taken on the Live Scan device. The time is represented in military time.

2.029 WGT - WEIGHT

In this field the subject’s weight in pounds is entered. The weight entered can range from 20 pounds to 499 pounds. If the weight is unknown, an estimate is required for reportable records.

Zeros are not valid for unknown in Michigan.

DEFINITION OF FIELDS FOR MICHIGAN TYPE 10 RECORD

Type-10 records shall contain facial and/or SMT image data and related ASCII information pertaining to the specific image contained in this record. The type-10 record shall be used to exchange both gray-scale and color image data in a compressed form. A maximum number of 19 images may be attached to each transmission.

CGA 10.011 – COMPRESSION ALGORITHM

This mandatory ASCII field shall specify the algorithm used to compress the color or grayscale image. The standard method for the compression of facial and SMT images is specified by the baseline mode of the JPEG algorithm. The data shall be formatted in accordance with the JPEG File Interchange Format, Version 1.02 (JFIF)7. An entry of "JPEGB" indicates that the scanned or captured image was compressed using baseline

JPEG

COL 10.043 – COLORS

This optional field shall contain one subfield corresponding to each subfield contained in the SMD (SMT Descriptors) field. Each subfield shall contain one or more information items that list the color(s) of the tattoo or part of the tattoo. For each subfield, the first information item in the subfield shall be the predominant color, entered according to the color codes in the table below. Additional colors for the subfield shall be entered as information items in the subfield separated by the US separator character.

COLOR CODES

Color description Color code

Black BLACK Brown BROWN Gray GRAY Blue BLUE

Green GREEN Orange ORANGE Purple PURPLE Red RED

Yellow YELLOW White WHITE

Multi-colored MULTI Outlined OUTLINE

CSP 10.012 - COLORSPACE

This mandatory ASCII field shall contain the colorspace used to exchange the image. The preferred colorspace using baseline JPEG and JFIF is YCbCr8 to be coded as "YCC".

DAT 10.999 - IMAGE DATA

This field shall contain all of the grayscale or color data from a face, scar, mark, tattoo, or other image. It shall always be assigned field number 999 and must be the last physical field in the record. For example, .10.999:. is followed by image data in a binary representation.

HLL 10.006 - HORIZONTAL LINE LENGTH

This mandatory ASCII field shall contain the number of pixels contained on a single horizontal line of the transmitted image.

HPS 10.009 - HORIZONTAL PIXEL SCALE

This mandatory ASCII field shall specify the integer pixel density used in the horizontal direction providing the SLC contains a "1" or a "2". Otherwise, it indicates the horizontal component of the pixel aspect ratio.

IDC 10.002 - IMAGE DESIGNATION CHARACTER

This mandatory ASCII field shall be used to identify the facial or SMT image data contained in the record. This IDC shall match the IDC found in the file content (CNT) field of the Type-1 record.

IMT 10.003 - IMAGE TYPE

This mandatory ASCII field is used to indicate the type of image contained in this record. It shall contain "FACE", "SCAR", "MARK", or "TATTOO" to indicate the appropriate image type.

LEN 10.001 - LOGICAL RECORD LENGTH

This mandatory ASCII field shall contain the total count of the number of bytes in the Type- 10 logical record. This field shall specify the length of the record including every character of every field contained in the record and the information separators.

PHD 10.005 - PHOTO DATE

This mandatory ASCII field shall contain the date that the facial or SMT image contained in the record was captured. The date shall appear as eight digits in the format CCYYMMDD.