APPENDIX C

DESCRIPTORS AND FIELD EDIT SPECIFICATIONS

FOR TYPE-2 LOGICAL RECORDS

1.0 User-Defined Data

     Some Type-2 elements have their origins as contributor-supplied data. User-defined data is that subset of contributor-supplied data that will not be stored in any IAFIS files for later search or retrieval purposes. User-defined data will not be validated (with several exceptions), and therefore may in general consist of any printable 7-bit ASCII character: i.e. free text. This includes the ASCII (decimal) codes 07 (BEL) through 13 (CR) and 32 (SP) through 127 (DEL), inclusive. Separator characters are not part of the printable character set.

     The following list gives those Type-2 elements which the FBI treats as being user-defined: ATN, SCO, OCA, SID, OCP, EAD, RES, CRI, IMA, TAA. In this list, SID and CRI may not always be free-text. In criminal transactions, these fields must contain valid formats, as specified further in this appendix. Occasional other restrictions are specified as required in this data dictionary. If the contributor supplies data in any of these fields in a submission or search, that data will be returned in the corresponding response.

     The RAP, RET, REC, TAA, and ULF are flag fields taking values positive = “Y” and negative = “N”. The negative value should not, in general, be submitted unless otherwise described in a specific definition.

1.2 Date Fields

     EFTS transactions will be Y2K compliant. Date fields are in accordance with that requirement. In general, the format for date fields is the following:

A date is shown as an 8-digit numeric field of the format CCYYMMDD, where

CC (Century) must be 19 or 20
YY (Year) must be 00 to 99
MM (Month) must be 01 to 12
DD (Day) must be 01 to the limit defined by the month and year (e.g., DD may be 29 for MM = 02 in Leap Years)

For example 19921201 represents December 1, 1992.

     Since dates find a variety of uses in EFTS transactions, each use may have specific format restrictions or special edits. For specific format restrictions or special edits, see the individual date field entries in this Appendix.

CJIS-RS-0010 (V7)

55

January 29, 1999

2.0 Data Dictionary

ACN 2.071 - ACTION TO BE TAKEN. This field is used to include text answers to submission requests to indicate that a latent case will be established or to indicate recommendations for further actions in either latent or ten-print responses. Commas, hyphens, ampersands, slashes, number signs, and blanks are all allowed as special characters.

AGR 2.023 - AGE RANGE. An estimated age range may be entered using a pair of two-digit numbers. The first two digits shall represent the minimum age, and the second two the maximum. There shall be no separator character used between the ages.

AKA 2.019 - ALIASES. This 3-to-30 alpha-numeric special (ANS) field contains alias names of the subject. Up to ten aliases may be provided, separated from one another by the character. AKA may contain a comma, hyphen, or blank as special characters. The format shall be the surname followed by a comma (,), followed by the given name(s) separated by a space. The following restrictions and exceptions to the general format apply:

1.  Minimum length is three bytes in the following sequence: alpha or ampersand, comma, alpha.

2.  A comma must be followed by the minimum of one alpha character.

3.  Blank before or after comma is invalid.

4.  Hyphen in first and last position of any name segment is invalid.

5.  Two consecutive blanks or hyphens between characters are invalid.

AMP 2.084 - AMPUTATED OR BANDAGED. This grouped field contains information about amputated or bandaged fingerprints in an EFTS submission. It is comprised of two subfields, Finger Number (FGP), and Amputated Or Bandaged Code (AMPCD). The two-character finger position code is followed by the separator and the amputated or bandaged code. Multiple fingers shall be separated by the separator. This field is to be used anytime there are fewer than ten printable fingers in a ten-print submission. A partially scarred finger should be printed. If the forwarding agency is not sure of the reason a finger’s image is missing (for example, when the arresting agency did not specify a reason in its submission to the State Ident Bureau), the “UP” code should be used.

Two characters represent each finger number as follows:

CJIS-RS-0010 (V7)

56

January 29, 1999

The following is a list of allowable indicators for the AMPCD

The following example indicates that the third finger is amputated and that the submitter did not, or was unable to, supply a print of the ninth finger.

2.084:03XX09UP

ASL 2.047- ARREST SEGMENT LITERAL. This field is made up of the Date of Offense (DOO) and the Arrest Offense Literal (AOL). The AOL is free text description of an offense charged on an arrest. The first character of the AOL text must not be blank. Each AOL should have a corresponding date (DOO), if available. The DOO shall appear as an eight-digit number as specified in Section 1.2 of this Appendix. The complete date shall not exceed the current date. Up to 40 occurrences of the ASL are allowed. Each occurrence of the ASL shall be separated by the separator character. The DOO shall be separated from the AOL by the separator character. A DOO is prohibited without a corresponding AOL offense. If a DOO is not present, a character separator shall still be used.

The following is an example of more than one occurrence of the AOL field using DOO:

2.047:19940915DUI19940920POSSESSION OF FIREARMS

ATN 2.006 - "ATTENTION" INDICATOR. This alphanumeric-special field shall contain a designation of the individual to whose attention a response is to be directed. Periods shall not be used (e.g., Det. J. Q. Public shall be entered as DET J Q PUBLIC). The value of ATN returned to the submitter is the value submitted.

CAN 2.064- CANDIDATE LIST. This grouped field shall contain a candidate list. It is comprised of two subfields: FBI number (FNU), and Name (NAM), separated by a separator, will be provided for each candidate in the list. Commas, hyphens and blanks are allowed in the NAM subfield, as specified in the NCIC Code Manual. Each FBI number and name set shall be separated from the next by the separator character.

CFS 2.077 - CANCEL FINGERPRINT SEARCH. This field will contain the information required to cancel a latent FP search previously submitted to IAFIS. This field will contain unique identifier numbers (AFIS/FBI uses the AFIS Segment Process Control Number) for all searches to be canceled. The response to this request will contain the same information for all

CJIS-RS-0010 (V7)

57

January 29, 1999

searches that were canceled. Only searches which are still pending will be canceled (searches completed or in-progress may not be canceled).

CIN 2.010 - CONTRIBUTOR CASE IDENTIFIER NUMBER. This grouped free-text field is a 48-byte (maximum) alphanumeric-special assigned by the contributor to uniquely identify a latent case. It consists of a literal subfield Contributor Case Prefix (CIN_PRE) of up to 24 characters (e.g., “Incident #”, “Laboratory Number:”, “Investigation No.”), followed by the separator and the Contributor Case Identifier subfield (CIN_ID) of up to 24 characters.

CIX 2.011 - CONTRIBUTOR CASE IDENTIFIER EXTENSION. This field is a two-byte to four-byte numeric supplement to the Case Identifier Number that allows multiple searches to be associated with the same case. The CIX shall be used only in conjunction with the CIN.

CRI 2.073 - CONTROLLING AGENCY IDENTIFIER. In Criminal transactions, the first instance of this one-to-nine byte field shall contain the originating agency identifier (ORI) of the organization controlling the transaction when that organization is different than the one submitting the transaction (e.g. state CTA). When the controlling agency has the same ORI as the CTA, both the ORI and CRI fields shall be submitted with the same identifier. In criminal transactions, the CRI will usually refer to the booking station that has submitted the subject’s fingerprint card or photo to be transmitted through the CTA to the FBI. For Civil submissions, this free-text field is user defined. The FBI uses the first instance of CRI in any transaction that would modify criminal records as the authority to do so. If in a Civil transaction there is a criminal IDENT against the subject and the first instance of the submitted CRI is not an authorized ORI, the ORI of the State Ident Bureau that submitted the transaction will be used in its stead. The second and third instances of CRI, when sent, are treated as user defined fields. (See also Appendix B for definitions of ORI and DAI.) CRI returned is otherwise the same as was submitted unless the submitting agency has used a deleted CRI, in which case its replacement will be used.

CRN 2.085 - CIVIL RECORD NUMBER. A unique identifier assigned to each Civil Subject Record.

CSL 2.051 - COURT SEGMENT LITERAL. The CSL field is made up of the Court Disposition Date (CDD), the Court Offense Literal (COL), and the Other Court Sentence Provision Literal (CPL). The CDD is the date a court count was disposed of by the court. The CDD shall appear as an eight-digit number as specified in Section 1.2 of this Appendix. The complete date shall not exceed the current date. The COL contains free text description of an offense charged in a court count. The first character of the COL must not be a ‘blank’. The CPL contains free-text information on sentence provisions. Up to 40 occurrences of the CSL are allowed. Each occurrence of the CSL shall be separated by the separator character. A CDD (if available), followed by a COL, followed by a CPL each separated by a separator character must be present for each occurrence of the CSL field. If the CDD is not available, a separator character alone shall be used immediately after the field tag or preceding separator character. The COL is always mandatory. When a provision (CPL) is included, then the date the provision was made (CDD) may optionally be given.

CJIS-RS-0010 (V7)

58

January 29, 1999

The following is an example of the CSL with multiple occurrences:

2.050:19940930DUI5 DAYS JAIL, PAY COURT COSTS19940930POSSESSION OF FIREARMS10 DAYS JAIL, PAY COURT COSTS, $50

The following is an example of the CSL when the first of two CDDs was not available:

2.050:DUI5 DAYS JAIL, PAY COURT COSTS19940930POSSESSION OF FIREARMS10 DAYS JAIL, PAY COURT COSTS, $50

When submitting a custody Ten-print, use this field for custody information. In the event that there is no arrest information available when submitting a custody Ten-print, the COL and CDD must be copied to the corresponding AOL and DOO fields of the Arrest Segment Literal (ASL), which is mandatory in all criminal Ten-print submissions.

CSR 2.048 - CIVIL SEARCH REQUESTED INDICATOR. This field shall contain a "Y" if a search of the Civil File is desired at the completion of Criminal File search.

CST 2.061 - CASE TITLE. This field identifies the Latent Case. It will include information concerning the case and it must include the offense type.

CTZ 2.021 - COUNTRY OF CITIZENSHIP. This field contains the name of the country of which the subject is a citizen. Entry must be a valid country code from Code Table POB in Part IV of the NCIC Code Manual.

DOA 2.045 - DATE OF ARREST. This field contains the date of arrest. The date shall appear as an eight-digit number in the same format as specified as specified in Section 1.2 of this Appendix. DOA shall not exceed date of submission after Time-Zone adjustment.

DOB 2.022 - DATE OF BIRTH. This field contains the date of birth. It is entered as an eight-digit number in the same format as specified as specified in Section 1.2 of this Appendix. DOB is completely unknown, enter as 00000000. Partial DOBs are not allowed. DOB shall not exceed date of submission after Time-Zone adjustment.

DOS 2.046 - DATE OF ARREST - SUFFIX. This field contains a code representing the sequence of the subject's arrests within a given date. The code also indicates the type of fingerprint card on which the Date of Arrest was contained. This field is for internal use within the FBI only.

DPR 2.038 - DATE PRINTED. This field contains the date that the subject was fingerprinted. The format shall be the same as that specified as specified in Section 1.2 of this Appendix. DPR shall not exceed date of submission after Time-Zone adjustment.

EAD 2.039- EMPLOYER AND ADDRESS. The name and address of the subject’s primary employer may be entered into this free-text field. The EAD returned in a response is the same as the one submitted.

CJIS-RS-0010 (V7)

59

January 29, 1999

ERS 2.075 - ELECTRONIC RAP SHEET. This field shall contain the electronic rap sheet. The electronic rap sheet is an electronic copy of the Identification Record Report (IDRR) or the Non-Identification Response (NIDR) as are done today. The electronic rap sheet shall consist of lines with a maximum of 74 characters per line (text of 72 plus 2 line control characters).

ETC 2.069 - ESTIMATED TIME TO COMPLETE. The estimated time to complete a search or multiple searches for a Latent Search Status and Modification Query may be entered into this field. This one-to-four byte field will contain the estimated search completion time in minutes up to five days.

EXP 2.080 - RESPONSE EXPLANATION. This field is free-form text to elaborate on the RESPONSE CODE field.

EYE 2.031- COLOR EYES. For this field, the three-letter code from the following table is used to indicate the subject's color of eyes.

Eye Color Code

Black BLK Blue BLU Brown BRO Gray GRY Green GRN Hazel HAZ Maroon MAR Multicolored MUL Pink PNK Unknown XXX

FBI - 2.014 FBI NUMBER. This field contains the subject’s FBI number, if known. A valid FBI number shall be no more than nine alphanumeric characters. The FBI number returned in a response is dependent upon the search results (see Section 3.6).

FFN - 2.003 FBI FILE NUMBER. This is a 10-byte numeric representing the FBI

Investigative File Number. This is not the FBI Number specified by the mnemonic “FBI.” Since it is used for FBI LFPS record keeping purposes, it is imperative that the remote user transmit this number if it is known.

CJIS-RS-0010 (V7)

60

January 29, 1999

FGP 2.074 - FINGER POSITION. This field is used for latent submissions and remote searches and contains the fingerprint position code of the latent print(s) submitted. The following table is the finger position and code table:

If more than one finger is submitted, the codes will be separated by the character separator. For remote latent searches, if multiple fingerprint images are included in one search, finger position is mandatory for all images. If finger position is unknown, the search may contain only a single image, and the field FGP will be omitted, or may contain multiple guesses at the correct finger position in the FGP field. In this case the PAT field must contain “00" in its Finger Number subfield to indicate that the actual position is unknown (see also PAT entry).

FIU 2.072 - FINGERPRINT IMAGE(S) UPDATED. This alphanumeric field contains the finger positions that were updated in the FBI’s Fingerprint Image Master File as a result of an electronic request to update fingerprint images. The finger numbers for which image information is requested are selected from Table 5, Finger Position Code, in Section 10 of “ANSI NIST-CSL 1-1993.” Up to 13 individual finger numbers may be listed, separated from one another by the separator. If images of all 14 fingers were updated, the single character “A” is shown instead of individual finger numbers. If no images were updated, an “N” will be returned.

CJIS-RS-0010 (V7)

61

January 29, 1999

FNR 2.057- FINGER NUMBER(S) REQUESTED. This numeric field is used in transactions involving a request for fingerprint image information. The finger numbers for which image information is requested are selected from Table 5, Finger Position Code, in Section 10 of “ANSI NIST-CSL 1-1993.” Up to 13 individual finger image numbers may be listed, separated from one another by the separator. If all 14 ten-print images are desired, 00 is shown instead of individual finger numbers. For transactions which allow only the ten rolled fingerprint images, when all ten images are desired, list each one separately, as 01 02 ... 10.

FPC 2.033 - NCIC FINGERPRINT CLASSIFICATION. If available, the NCIC fingerprint classification will be returned in the FBI’s responses to latent submissions.

The NCIC FPC is comprised of 20 characters. Two characters represent each finger as follows:

The following codes apply:

The NCIC FPC for a set of fingerprints made up of all ulnar loops might read:

2.033:12101116141109111713

A combination of loops and whorls with an amputated right index finger might read:

2.033:12XX11CO14115906Cl13

* Prior to adoption of the above method for coding whorl patterns, this pattern was divided into inner, meeting, and outer subgroups only with codes II, MM, and OO, respectively. Some older records in file may show the codes II, MM, and OO.

** Code XX is used in instances of missing and totally/partly amputated fingers where conditions make it impossible to accurately classify an impression according to the above instructions for NCIC FPC. It is recognized that under the Henry System, if a finger is missing or amputated, it is given a classification identical to the opposite finger; however, this must not be done in the NCIC FPC since the location of finger or fingers missing/amputated is not indicated.

*** Code SR is used in instances in which the fingerprint cannot be accurately classified because of complete scarring or mutilation and a classifiable print cannot be obtained. As in the case of missing and amputated fingers, the procedure for assigning the classification of the opposite finger, as is done under the Henry System, should not be used for the NCIC FPC.

CJIS-RS-0010 (V7)

63

January 29, 1999

**** Codes UC and AC still exist for some legacy records in the Criminal History file.

Refer to the NCIC Code Manual, 4-28, for the FPC Field for Unidentified Persons.

GEO 2.044 - GEOGRAPHIC AREA OF SEARCH. This field indicates the geographic area to be searched. Entry may be any valid code from Code Table POB in Part VI of the NCIC Code Manual. Each GEO shall be separated from the next by the separator character. If inclusion of all 50 states is desired, this field shall remain blank.

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

HGT 2.027 - HEIGHT. This field contains the subject’s height as a three-character value. If 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. If reported in inches, the leftmost character is “N” followed by two digits. If height is unknown, 000 is entered. The allowable range is 400 to 711. Heights outside this range will be clamped at these limits.

HTR 2.028 - HEIGHT RANGE. If a range of height is given, it shall be expressed as two three-character values formatted as described for mnemonic HGT, indicating the shortest and tallest heights of the subject. There shall be no separator character used between the heights. The allowable range is 400 to 711. Heights outside this range will be clamped at these limits.

ICO 2.056 - IDENTIFICATION COMMENTS. Additional miscellaneous identification remarks providing the reason for caution may be entered in this free-text field. The first character may not be a blank.

CJIS-RS-0010 (V7)

64

January 29, 1999

IDC 2.002 - IMAGE DESIGNATION CHARACTER. This mandatory field shall be used to identify the user-defined text information contained in this record. The IDC contained in this field shall be the IDC of the Type-2 logical record as found in the file content field of the Type-1 record.

IMA 2.067 - IMAGE CAPTURE EQUIPMENT. This free text 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.

IMT 2.062 - IMAGE TYPE. This field identifies the type of image (e.g., palm prints, toe prints) included in an electronic submittal. The following is a list of IMT values to be used in an electronic latent submittal to identify the Type-7 record (s) present:

LCN 2.012 - FBI LATENT CASE NUMBER. This field is an 11-byte alphanumeric/special assigned by the FBI LFPS and used for record keeping purposes. Although the field is optional, it is imperative that the remote user transmit this number if it is known.

LCX 2.013 - LATENT CASE NUMBER EXTENSION. Defines extensions assigned by the FBI for each submission related to a Latent Case Number. The LCX shall be a four digit extension starting with "0001" for the first submission and incrementing by one for each subsequent submission. The LCX shall be used only in conjunction with LCN.

LEN 2.001 - 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 number of characters added to the record by the LEN field itself shall be included in calculating the value of LEN.

MIL 2.042 - MILITARY CODE. A one-letter code from the following table shall be entered in this field to indicate which branch of the United States Military submitted the transaction.

CJIS-RS-0010 (V7)

65

January 29, 1999

MNU 2.017 - MISCELLANEOUS 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. If “AF” or “AS” is entered, all characters following the hyphen must be numeric. 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 separator character.

MSC 2.089 - MATCHSCORE. Defines the match score of a fingerprint from AFIS for a candidate list response.

MSG 2.060 - STATUS/ERROR MESSAGE. This free-text field will contain reason, status or error messages that are generated as a result of the processing of a transaction and will be sent back to the submitter. For example, an Unsolicited Unsolved Latent Delete transaction will contain the reason for the deletion of a record. Each message will be separated by the separator character.

NAM 2.018 - NAME. This alpha-special 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. Part IV of the NCIC Code Manual describes in greater detail the manner in which each name is to be entered. Hyphens, commas, and blanks are all allowed as special characters. Numerics are not allowed. Special values of NAM, to be entered in cases where the subject’s name is not known, are:

CJIS-RS-0010 (V7)

66

January 29, 1999

NCR 2.079 - NUMBER OF CANDIDATES’ IMAGES RETURNED. This field contains the maximum number of candidates (images) the submitter desires to receive in response to a latent image or features search. If the field is left blank, only images for the highest scoring candidate will be returned. The maximum value of NCR is currently 20.

NOT 2.088 - NOTE FIELD. This free-text field is used to provide additional information regarding electronic latent submissions.

OCA 2.009 - ORIGINATING AGENCY CASE NUMBER. This field contains the one to twenty character Originating Agency Case Identifier (OCA) that has been assigned by the originating agency. This alphanumeric-special (ANS) field may contain any printable 7-bit ASCII character with the exception of the period (“.”). The length of the OCA field submitted varies by category of transaction: The length of OCA should be 10 characters for CRIMINAL transactions, and 15 for CIVIL. OCA must not begin with a blank.

OCP 2.040 - OCCUPATION. This free text field contains the subject’s occupation. The OCP returned in a response is the same as the one submitted.

OFC 2.053 - OFFENSE CATEGORY. This field shall contain a “1” for a crime categorized as personal, a "2" for one categorized as property, and a "3" for one categorized as both.

PAT 2.034 - Pattern Level Classifications. This grouped field contains information about the finger(s) pattern types. It is comprised of two subfields, Finger Number (FGP), and Pattern Classification Code (PATCL). The two-character finger position code followed by the separator and the primary pattern type code as chosen from the following table. Up to two reference pattern classifications per finger are also allowed, thereby making the total number of pattern classes allowable per finger equal to three. If multiple pattern types are used for reference for the same finger, they shall be separated from each other by the separator. Multiple fingers shall be separated by the separator. If submitting a Latent Fingerprint whose actual finger position is unknown, the PAT and FGP (2.074) fields are used in conjunction as follows to supply guesses for which finger position the Latent print might be: place a “00" in the FGP subfield of PAT to indicate the actual position is unknown; place the actual pattern in the PATCL subfield; place one or more finger number guesses in the FGP field (2.074).

CJIS-RS-0010 (V7)

67

January 29, 1999

Two characters represent each finger as follows:

The following is a list of acceptable IAFIS pattern level fingerprint classifications.

The following is an example of the Pattern Level Classification field with only one pattern per finger:

2.034:01WU02LS03LS04LS05LS06RS07RS08LS09RS10RS

The following is an example of the Pattern Level Classification field with extra pattern references for some of the fingers:

2.034:01RSWUAU02RSAUWU03WU04RS05WU06LS 07WU08AU09AU10WUAU

PEN 2.078 - PENETRATION QUERY RESPONSE. This field provides a response to the penetration query that includes a set of search parameters for a new search. The response will be an estimated size, in percentage, of the repository that will be searched given the input parameters.

PHT 2.036 - "PHOTO AVAILABLE" INDICATOR. If a photograph of the subject is available, this field shall contain a "Y"; otherwise, the field shall be omitted.

CJIS-RS-0010 (V7)

68

January 29, 1999

POB 2.020 - PLACE OF BIRTH. The subject’s place of birth shall be entered in this field. Indicate in this POB field the state (Mexican, United States), 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. The criteria listed below shall also be considered when assigning POB:

PPA 2.035 - "PALM PRINTS AVAILABLE" INDICATOR. If palm prints are available, this field shall contain a "Y"; otherwise, the field shall be omitted.

PRI 2.076 - PRIORITY. This field shall indicate the priority of a latent search (from 1 to 3, with 1 the highest priority). The priority levels will generally correspond to the following crime types in descending order of priority:

• Homicide, rape, and special circumstances
  
• Kidnap, assault, and robbery
  
• Arson, drugs, personal crimes, and property crimes
  

Federal agencies will determine their own priority schemes. No additional validation of priorities will be provided. IAFIS will not interrupt searches in progress upon receipt of higher priority searches.

PTD 2.063 - PERSON TYPE DESIGNATOR. This field is used in the submittal of comparison fingerprints and it indicates that the fingerprints belong to a victim, suspect, individual with legitimate access to the object, or other individuals involved in the latent case. The following codes will be used:

CJIS-RS-0010 (V7)

69

January 29, 1999

QDD 2.004 - QUERY DEPTH OF DETAIL. This field is used to define the scope of the Latent Queue Management Query. The defined levels can be at the State level ("S"), at the ORI level ("O"), or at the Case level ("C").

RAC 2.025 - RACE. This field is used to indicate the race of the subject. Use the predominant race code from the following table:

RAP 2.070 - REQUEST FOR ELECTRONIC RAP SHEET. The purpose of this field is to allow the contributors to optionally request an electronic rap sheet of the suspect. That rap sheet will be an IDRR if an Ident was made, and an NIDR if the submission resulted in a Non-Ident. A "Y" indicates that a rap sheet is desired and an omitted field or an “N” indicates that no electronic rap sheet should be returned with the response.

RCD1 2.091 - Ridge Core Delta One for Subpattern Classification. This grouped field contains information about the finger(s) ridge counts and is used for Remote Native Mode Searches in conjunction with the Pattern Level Classification (PAT - 2.034). It is comprised of two subfields, Finger Number (FGP), and Ridge Count Number 1 (RCN1). The two-character finger position code as specified for the related Pattern Level Classification (PAT) is followed by the separator and at least one RCN1. Each pattern classification PATCL specified in the tagged

CJIS-RS-0010 (V7)

70

January 29, 1999

field 2.034 must be accompanied by two ridge count indicators, one in RCD1 (2.091) and one in RCD2 (2.092) as described in the table provided with RCD2. If multiple RCN1s are used for reference to the same finger, then they shall be separated from each other by the separator. Multiple fingers, if provided, shall be separated by the separator.

RCD2 2.092 - Ridge Core Delta Two for Subpattern Classification. This grouped field contains information about the finger(s) ridge counts and is used for Remote Native Mode Searches in conjunction with the Pattern Level Classification (PAT - 2.034). It is comprised of two subfields, Finger Number (FGP), and Ridge Count Number 2 (RCN2). The two-character finger position code as specified for the related Pattern Level Classification (PAT) is followed by the separator and at least one RCN2. Each pattern classification PATCL specified in the tagged field 2.034 must be accompanied by two ridge count indicators, one in RCD1 and one in RCD2 as described in the following table. If multiple RCN2s are used for reference to the same finger, then they shall be separated from each other by the separator. Multiple fingers, if provided, shall be separated by the separator.

The Ridge Count Number (RCN1 and RCN2) represents the number of ridges between the core and the delta. For right and left slant loops, this count identifies the ridges crossed on a line between the core and the delta. For Whorls, both the RCN1 and the RCN2 values have meaning. Permissible values are 1 to 30 for actual ridge counts and 30 if there are more than 30 ridges. The count of 31 indicates an unknown number of ridges and 0 indicates that the ridge count is not applicable.

The following is a list of acceptable IAFIS pattern level fingerprint classifications and the allowable ridge count ranges for each.

The following example shows the relationship between the Pattern Level Classification (2.034), Ridge Core Delta 1 (2.091) and Ridge Core Delta 2 (2.092) fields, where only the primary classification for each finger is given. In this case, one PATCL, one RCN1 and one RCN2 are associated with each finger. Spaces are shown for clarity only.

2.034:01 WU 02 LS 03 AU 04 XX 10 WU
2.091:01 9 02 4 03 0 04 0 10 14
2.092:01 7 02 0 03 0 04 0 10 21

CJIS-RS-0010 (V7)

71

January 29, 1999

The following example of the Pattern Classification (2.034) field includes two reference classifications for finger 01, only a primary classification for finger 07, and one reference classification for finger 09. Each PATCL in 2.034 requires a corresponding RCN1 and RCN2 in fields 2.091 and 2.092. Spaces are shown for clarity only.

2.034:01 RS WU AU 07 XX 09 AU LS
2.091:01 9   9 0 07 0 09 0 8
2.092:01 0 11 0 07 0 09 0 0

REC 2.082 - RESPONSE CODE. A one-byte alpha field with allowable values of “Y” or “N”. This field is used in the PDR and PRR transactions to indicate the status of the corresponding request. If the request contains any errors, the response code (REC) will be set to “N”.

Otherwise it will be set to “Y”.

RES 2.041 - RESIDENCE OF PERSON FINGERPRINTED. The subject’s residential address may be entered in this field as free text, including printable special characters and formatting characters (CR, LF, TAB). The RES returned in a response is the same as the one submitted.

RET 2.005 - RETENTION CODE. This is an alpha field indicating whether the arrest information submitted as a part of a transaction (either electronic or hard copy) is to be retained as a permanent part of the FBI’s Criminal Master File. Submit a “Y” for yes, an “N” for no. For Civil submissions, RET is used to indicate whether the civil submission is to be retained in the civil files. In the case where a Criminal Ident was made against the Criminal File in a Civil Submission (irrespective of the value of RET), under some conditions the record is retained as a Civil Cycle in that Criminal record.

RFP 2.037 - REASON FINGERPRINTED. This alphanumeric-special field is used to indicate the purpose of a civil or applicant fingerprint card submission. This field will indicate if the card is submitted for licensing, gun permit, or criminal justice employment, non-criminal justice employment, adoption, naturalization, volunteer background checks, gaming certification, and others under State control. Commas, blanks, dashes, hyphens and slashes are all allowed as special characters.

RSR 2.065 - REPOSITORY STATISTICS RESPONSE. This field contains a file generated by the AFIS that provides the detailed statistics that can be used to estimate the level of penetration of the repository given a set of search parameters defined in the search request. This field is in the form of a large ASCII file which can contain up to 32000 bytes of alphanumeric-special (ANS) data. The file has three fields containing: (1) a parameter name, (2) a parameter value; and (3) the fraction of the file having that value of the parameter. The fields are TAB delimited. NEWLINE characters separate records. A period character is used as a decimal point in the Fraction field. As an example, the record EYE<TAB>BLUE<TAB>0.321<NEWLINE> indicates that the parameter EYE having the value BLU occurs in 32.1% of the subjects on file.

CJIS-RS-0010 (V7)

72

January 29, 1999

SCNA 2.086 - AFIS SEGMENT CONTROL NUMBER. This field contains a number used by AFIS/FBI to allow tracking of or reference to specific transactions. It is used, for example, to indicate the index number for individual records in the IAFIS Unsolved Latent File in the response to a Remote Latent Search. It is also used to refer to transactions that contained searches for the purpose of status queries, modifications, or cancellations.

SCO 2.007- SEND COPY TO. The purpose of this 9-to-19 character alphanumeric-special (ANS) field is to indicate that additional electronic responses need to be forwarded to agencies other than the contributor by the state identification bureau. The first nine characters shall be alphanumeric and shall contain the NCIC-assigned Originating Agency Identifier (ORI) for an agency who is to receive a copy of the response. At the option of the transmitting agency, the ORI may be expanded to a size of 19 characters, with 10 characters of alphanumeric-special (ANS) data appended to the end to assist in proper routing of the responses. However, no <US> or <RS> separator may be used between the ORI and routing extension (use any printable ASCII special character (e.g., a slash) as a separator). Upon receiving an electronic response, the state identification bureau will forward a copy of the electronic response to each agency listed in the “SEND COPY TO” block.

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

SID 2.015 - STATE IDENTIFICATION NUMBER. This field contains any known state identification number. The format is the standard two-character abbreviation of the state name, followed by the number. Embedded blanks are not permitted. SIDs from NY, OR, or PA may contain a hyphen in the last position. The SID returned in a response is dependent upon the search results (see Section 3.6).

SLE 2.055 - CUSTODY OR SUPERVISORY STATUS LITERAL. This field contains the free-text description of the subject’s custody or supervision status. The first character must not be blank. Entry of SLE requires that SSD also be entered.

SMT 2.026 - SCARS, MARKS AND TATTOOS. For each scar, mark, or tattoo present on the subject, the appropriate NCIC code shall be used in this information item. Blanks are allowed as special characters.

CJIS-RS-0010 (V7)

73

January 29, 1999

SOC 2.016 - SOCIAL SECURITY ACCOUNT NUMBER. This field contains the subject’s social security number, if known. This number shall be entered as nine consecutive digits with no embedded punctuation characters. No foreign social security numbers shall be used.

SRF 2.059 - SEARCH RESULTS FINDINGS. This field is used in responses to submissions and contains a single character. An “I” shall be used to indicate that an identification has been made, and an "N" shall be used to indicate that no identification has been made.

SSD 2.054 - CUSTODY OR SUPERVISORY STATUS START DATE. This field contains the start date for the subject's indicated custody or supervisory status. The date shall appear as an eight-digit number in the same format as specified for CDD. SSD may not be less than DOA. Complete date may not exceed current date. If custody data are submitted, all custody fields (SSD, OCA and SLE) must be present.

TAA 2.087 - TREAT AS ADULT. A one-byte optional field to indicate whether a juvenile is to be processed as an adult. A “Y” indicates yes, an omitted field indicates no. The TAA returned in a response is the same as the one submitted.

TSR 2.043 - TYPE OF SEARCH REQUESTED. A one-byte code shall be entered in this field from the following table to indicate the type of record being submitted. The field is applicable to the FAUF and NFUF transactions as follows.

ULF 2.083 - UNSOLVED LATENT FILE. This one-character alpha field is used to designate whether a latent image or features record in search should be added to the Unsolved Latent File. Submit a “Y” for yes. For a no, omit the field.

WGT 2.029 - WEIGHT. In this field the subject’s weight in pounds is entered. If weight is unknown, 000 is entered. All weights in excess of 499 pounds will be set to 499 lbs.

WTR 2.030 - WEIGHT RANGE. If a range of weight is given, it shall be expressed as two 3-digit numbers indicating the minimum and maximum weights (in pounds) of the subject. There shall be no separator character used between the weights. WTR must be in the range 050 to 499 lbs (however, there is no minimum range limit for missing persons or unknown persons).

CJIS-RS-0010 (V7)

74

January 29, 1999

TABLE C-1. FIELD EDIT SPECIFICATIONS FOR TYPE-2 ELEMENTS

Under the character type column: A = Alpha; B = Binary; N = Numeric; S = Special Characters

CJIS-RS-0010 (V7)

75

January 29, 1999

TABLE C-1. FIELD EDIT SPECIFICATIONS FOR TYPE-2 ELEMENTS

Under the character type column: A = Alpha; B = Binary; N = Numeric; S = Special Characters

CJIS-RS-0010 (V7)

76

January 29, 1999

TABLE C-1. FIELD EDIT SPECIFICATIONS FOR TYPE-2 ELEMENTS

Under the character type column: A = Alpha; B = Binary; N = Numeric; S = Special Characters

CJIS-RS-0010 (V7)

77

January 29, 1999

TABLE C-1. FIELD EDIT SPECIFICATIONS FOR TYPE-2 ELEMENTS

Under the character type column: A = Alpha; B = Binary; N = Numeric; S = Special Characters

CJIS-RS-0010 (V7)

78

January 29, 1999

TABLE C-1. FIELD EDIT SPECIFICATIONS FOR TYPE-2 ELEMENTS

Under the character type column: A = Alpha; B = Binary; N = Numeric; S = Special Characters

CJIS-RS-0010 (V7)

79

January 29, 1999

TABLE C-1. FIELD EDIT SPECIFICATIONS FOR TYPE-2 ELEMENTS

Under the character type column: A = Alpha; B = Binary; N = Numeric; S = Special Characters

CJIS-RS-0010 (V7)

80

January 29, 1999