C
C
C
I
IIV
V
VI
IIL
L
L
W
W
W
O
O
OR
R
RK
K
KF
F
FL
L
LO
O
OW
W
W
C
C
C
O
O
ON
N
NT
T
TR
R
RO
O
OL
L
L
S
S
S
Y
Y
YS
S
ST
T
TE
E
EM
M
M
CIVIL WORKFLOW CONTROL SYSTEM (CWCS)
?
INTERFACE CONTROL DOCUMENT (ICD)
?
FOR THE
?
FLORIDA DEPARTMENT OF LAW ENFORCEMENT
?
September 28, 2004
?
Version 1.7
?
Interface Control Document
1
Table of Contents
Section / Paragraph
Page
CHANGE PAGE .............................................................................................................................3
?
1. INTRODUCTION .......................................................................................................................5
?
1.1 Purpose...........................................................................................................................5
?
1.2 References......................................................................................................................5
?
2. INTERFACE CONTROL............................................................................................................5
?
2.1 Submission to FDLE......................................................................................................5
?
2.2 Receipt of Responses .....................................................................................................6
?
3. APPLICANT DATA REQUIREMENTS....................................................................................6
?
3.1 Applicant NIST Requirements.......................................................................................6
?
3.2 Data Validation ..............................................................................................................6
?
3.3 Applicant Type of Transactions (TOT) .........................................................................6
?
APPENDICES
APPENDIX A NIST TYPE-1 DEFINITIONS...............................................................................7
?
APPENDIX B NIST TYPE-2 DEFINITIONS.............................................................................20
?
Interface Control Document
2
CHANGE PAGE
?
Version
Date
Page
Description
Ver 1.6
10/7/03
3
Inclusion of Change page.
Ver 1.6
10/7/03
5
Verbiage change to Sec 1 Introduction
Ver 1.6
10/7/03
5
Verbiage change to Sec 1.3 Certification
Ver 1.6
10/7/03
5
Verbiage change to Sec 2.1 Submission to FDLE
Ver 1.6
10/7/03
6
Verbiage change to Sec 2.2 Receipt of Responses
Ver 1.6
10/7/03
6
Verbiage change to Sec 3.1 Applicant NIST Requirements
Ver 1.6
10/7/03
6
Verbiage change to Sec 3.2 Data Validation
Ver 1.6
10/7/03
7
NIST Type 1 Table Added verbiage to TCN and TCR fields
Ver 1.6
10/7/03
13
NIST definition PRY field. Change to default value
Ver 1.6
10/7/03
15
NIST definition ORI field verbiage change
Ver 1.6
10/7/03
16
NIST definition TCN field. change from 5 to 6 digits prefix.
Use of 8 vice 7 as leading TCN digit for scanned inked cards.
Ver 1.6
10/7/03
17
NIST definition TCR field. Additional use for credit card
submissions on initial submission.
Ver 1.6
10/7/03
20
NIST Type 2 Table. Added ATN, SCO, OCA, FBI, SID, MNU,
OCP, TSR fields.
Ver 1.6
10/7/03
25
NIST definition ATN field description added
Ver 1.6
10/7/03
26
NIST definition SCO field description added
Ver 1.6
10/7/03
27
NIST definition OCA field description added
Ver 1.6
10/7/03
28
NIST definition FBI field description added
Ver 1.6
10/7/03
29
NIST definition SID field description added
Ver 1.6
10/7/03
30
NIST definition SOC field verbiage change
Ver 1.6
10/7/03
31
NIST definition MNU field description added
Ver 1.6
10/7/03
49
NIST definition WGT field verbiage change
Ver 1.6
10/7/03
54
NIST definition EAD field verbiage change
Ver 1.6
10/7/03
55
NIST definition OCP field description added
Ver 1.6
10/7/03
56
NIST definition RES field verbiage change
Ver 1.6
10/7/03
57
NIST definition TSR field description added
Ver 1.6
10/7/03
58
NIST definition IMA field description added
Ver 1.6
10/7/03
59
NIST definition CRI field description added
Ver 1.7
09/28/04
21
NIST Type 2 Table Added RAP field
Ver 1.7
09/28/04
59
NIST definition RAP field description added
Interface Control Document
3
This page intentionally left blank
Interface Control Document
4
1.
?
INTRODUCTION
This document defines the protocols, procedures and data formats for interfacing and submission to the
Civil Workflow Control system (CWCS). No other interface changes will be supported unless documented
as a revision to this document. This document will be used as the baseline for product development by
vendors desiring certification of equipment capable of submitting to CWCS. Interpretation of these
requirements rests solely with Florida Department of Law Enforcement (FDLE). This document will be
revised as requirements change.
1.1
?
Purpose
This document provides the interface descriptions required for applicant submissions to FDLE.
1.2
?
References
a.
?
American National Standard for Information Systems – Data Format for the Interchange
of Fingerprint Information, November 22, 1993, ANSI/NIST – CSL 1-1993
b.
?
Criminal Justice Information Service (CJIS) Electronic Fingerprint Transmission
Specification, January 1999, CJIS-RS-0010 (V7)
1.3
?
Certification
Any electronic fingerprint capture device proposed for submitting requests through CWCS must first be on
the list of FBI approved devices as certified in Appendix F of the FBI Image Quality Standard.
Software must be certified by FDLE to ensure correct procedures and format in the collection, submission
and storage of electronic applicant fingerprint records. Products submitted to FDLE must conform to a
standard “look” in the display and capture of information. Products that do not meet the hardware or
software requirements will not be certified or permitted to transmit images to FDLE. Any “upgrades” or
changes to either software or hardware will require re-certification by FDLE prior to product delivery.
Customization of software for individual preference is prohibited. Any changes, software or hardware, to
an installed device will result in de-certification.
2.
?
INTERFACE CONTROL
This section provides the interface control information for transmission to CWCS and receipt of responses
from CWCS.
2.1
?
Submission to FDLE
Submissions to CWCS shall be transmitted as single part MIME encoded SMTP mail messages through
Internet mail services. The NIST packet will be an attachment in the body of the email message. The
NIST packet will be labeled with the Transaction Control Number (TCN) and an extension of “.EFT”. For
example, 70P01000155.eft. Transmission of an applicant request to FDLE shall not be automatic. The
operator will be required to take some overt action to transmit each request. The operator can be provided
5
Interface Control Document
the ability to transmit multiple submissions at one time or transmit each one individually. A daily
transmission log is required indicating the date/time of the transmission, TCN, success, or failure.
Each device electronically submitted to FDLE shall have the capability to print a hardcopy of the
transaction, including images. The hardcopy must be printed on the standard FBI Applicant fingerprint
card (FD-258) if being submitted to FDLE for processing manually vice electronic submission processing.
The hardcopy may be printed on standard paper (8 ½ X 11) for record storage or to be used for a receipt.
In the event of a submission’s rejection by the FBI, the capability to resubmit must be available. The
resubmission must contain the FBI’s control number (IAFS123456789) in the Transaction Control
Reference (TCR) field. (NIST field 1.10) Resubmissions will also be logged in the daily transmission log
indicating the date/time of transmission, TCN, TCR, success/failure.
2.2
Receipt of Responses
CWCS uses a table of authorized customers to determine the destination address for returning the results of
the background check. Notification is sent to the customer’s email indicating results are available. The
operator is given a link to a secure email site. Results are sent to the designated destination address via
secure email.
3.
APPLICANT DATA REQUIREMENTS
This section provides the requirements needed for the NIST data types applicable for an applicant
submission.
3.1
Applicant NIST Requirements
Packets will be formatted according to NIST standards for applicant submissions. Packets will consist of
Type–1, Type-2 and Type-4 data. Appendix A provides a breakdown of fields for Type-1 records.
Appendix B provides a breakdown of fields for Type-2 records. The device will store each transaction as a
NIST packet, using the TCN as the file name, i.e.: 70P020000156.eft. The file must be accessible by the
operator for troubleshooting purposes or to copy to a floppy disk to submit to FDLE for troubleshooting.
The packet must be readable by standard NIST software such as NISTPACK by Aware. Storage of data in
proprietary format is prohibited.
3.2
Data Validation
Devices utilized in the collection of demographic data must perform validation on the data. Data must be
validated according to current EFTS standards, both in content and format AND as modified by this
document. Improper or invalid data should produce an error message to the device operator, outlining the
correct format or content. Submissions containing invalid data will be rejected by CWCS and returned to
the originating livescan. Data entered into each NIST field
MUST
be accurate and reflect the purpose of
that field. The use of optional data fields for local agency information, such as tracking numbers, etc. is
PROHIBITED.
3.3
Applicant Type of Transactions (TOT)
The only accepted TOT’s for applicant submissions, Type-1 field 1.04, are Miscellaneous Applicant Civil
(MAP) and the Non-Federal Applicant User Fee (NFUF).
6
Interface Control Document
APPENDIX A NIST TYPE-1 DEFINITIONS
?
Identifier Condition Field
#
Field name
Char
Type
Field Size
Occurrences
Min Max
Min Max
LEN
M
1.01
Logical Record Length
Numeric
2
3
1
1
VER M
1.02
Version
Number
Numeric
4
4
1
1
CNT M
1.03
File
Content
A/N
9
48
1
1
TOT
M
1.04
Type of Transaction
Alpha
3
5
1
1
NOTE: Only MAP or NFUF permitted.
DAT M
1.05
Date
Numeric
8
8
1
1
PRY O
1.06
Priority
Numeric
1
1
0
1
DAI M
1.07
Destination
Agency
A/N
9
9
1
1
ORI M
1.08
Originating
Agency
A/N
9
9
1
1
TCN
M
1.09
Transaction Control #
A/N
10
22
1
1
FIRST 7 DIGITS WILL BE ASSIGNED PREFIX
TCR
O
1.10
Transaction Control Ref #
A/N
10
40
0
1
REQUIRED FOR RESUBMISSIONS (Note 1)
NSR
M
1.11
Native Scanning Resolution
N/S
5
5
1
1
period only character permitted
NTR M
1.12
Nominal
Transmission
Resolution
N/S
5
5
1
1
period only character permitted
Full description of Field List is found in EFTS Ver 7.
A: Alpha
M: Mandatory
Field
O: Optional
Field
A/N: Alpha
Numeric
characters
A/S:
Alpha and Special Character
N/S:
Numeric and Special Character
MAP Transactions are reserved for Law Enforcement personnel only.
Note 1: This field will also be used for credit card submissions for
INITIAL
submission only
Interface Control Document
7
TYPE-1
FIELD IDENTIFIER:
LEN
FIELD NUMBER:
1.01
FIELD NAME:
Logical Record Length
FIELD CONDITION:
MANDATORY
LENGTH:
2 - 3
A,N,A/N: N
EXAMPLES:
REMARKS:
This mandatory ASCII field shall contain
the total count of the number of bytes in
the 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.
VALID CODES/FIELD
RESTRICTIONS:
Interface Control Document
8
TYPE-1
FIELD IDENTIFIER:
VER
FIELD NUMBER:
1.02
FIELD NAME:
VERSION NUMBER
FIELD CONDITION:
MANDATORY
LENGTH: 4
A,N,A/N: N
EXAMPLES:
REMARKS:
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 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 version 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”.
VALID CODES/FIELD
RESTRICTIONS:
Interface Control Document
9
TYPE-1
FIELD IDENTIFIER:
CNT
FIELD NUMBER:
1.03
FIELD NAME:
FILE CONTENTS
FIELD CONDITION:
MANDATORY
LENGTH:
9 - 48
A,N,A/N: A/N
EXAMPLES:
REMARKS:
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 record. It
shall consist of one or more subfields.
See the FBI’s Electronic Fingerprint
Transmission Specification document dated
August, 1995, for further information
regarding
this
field.
VALID CODES/FIELD
RESTRICTIONS:
Interface Control Document
10
TYPE-1
FIELD IDENTIFIER:
TOT
FIELD NUMBER:
1.04
FIELD NAME:
TYPE OF TRANSACTION
FIELD CONDITION:
MANDATORY
LENGTH:
3 - 5
A,N,A/N: A
EXAMPLES:
MAP, NFUF Only allowable Transaction Types
REMARKS:
This mandatory field shall contain an
identifier, designating the type of
transaction and subsequent processing that
this logical file should be given.
VALID CODES/FIELD
MAP is to be used for Law Enforcement personnel only.
RESTRICTIONS:
Interface Control Document
11
Type-1
FIELD IDENTIFIER:
DAT
FIELD NUMBER:
1.05
FIELD NAME:
DATE
FIELD CONDITION:
MANDATORY
LENGTH: 8
A,N,A/N: N
EXAMPLES: 19951115
REMARKS:
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.
VALID CODES/FIELD
RESTRICTIONS:
Interface Control Document
12
TYPE -1
?
FIELD IDENTIFIER:
PRY
FIELD NUMBER:
1.06
FIELD NAME:
PRIORITY
FIELD CONDITION:
OPTIONAL
LENGTH: 1
A,N,A/N: N
EXAMPLES:
REMARKS:
When this field is used, it shall contain a
single information character to designate
the urgency with which a response is
desired. The values shall range from 1 to
4, with “1” denoting the highest priority.
The default value shall be “2’ if no value
is
indicated.
VALID CODES/FIELD
RESTRICTIONS:
Interface Control Document
13
TYPE-1
?
FIELD IDENTIFIER:
DAI
FIELD NUMBER:
1.07
FIELD NAME:
DESTINATION AGENCY IDENTIFIER
FIELD CONDITION:
MANDATORY
LENGTH: 9
A,N,A/N: A/N
EXAMPLES: FLFDLECVZ
REMARKS:
This mandatory field shall contain the
identifier of the administration or
organization to receive the transmission.
The size and data content of this field
shall be defined by the user and be in
accordance
with
the receiving agency.
VALID CODES/FIELD
Same as ORI listed below.
RESTRICTIONS:
Interface Control Document
14
TYPE-1
?
FIELD IDENTIFIER:
ORI
FIELD NUMBER:
1.08
FIELD NAME:
ORIGINATING AGENCY IDENTIFIER
FIELD CONDITION:
MANDATORY
LENGTH: 9
A,N,A/N: A/N
EXAMPLES: LSD123456
REMARKS:
This ORI# will identify the identity
of the submitting device
VALID CODES/FIELD
RESTRICTIONS:
Each agency will be assigned an Identifier #
by FDLE. This field also known as the
Livescan Identity Number, will be used to
identify the physical device submitting to FDLE.
Interface Control Document
15
TYPE-1
FIELD IDENTIFIER:
TCN
FIELD NUMBER:
1.09
FIELD NAME:
TRANSACTION CONTROL NUMBER
FIELD CONDITION:
MANDATORY
LENGTH:
10 - 22
A,N,A/N: A/N
EXAMPLES:
REMARKS:
This mandatory field shall contain the
Transaction Control Number as assigned by
the
originating
agency. A unique 7 character
prefix 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.
VALID CODES/FIELD
RESTRICTIONS:
TCN will be limited to a total of 22 characters.
(7 assigned + 15 open) TCN prefix will also
denote type of device capturing the prints.
Prints taken electronically will have the TCN
start with “70” (70SX01000000000000001)
Prints being scanned in from inked cards
will have the TCN prefix start with “80”
(80E0100000000000000001)
Interface Control Document
16
FIELD IDENTIFIER:
?
FIELD NUMBER:
?
FIELD NAME:
?
FIELD CONDITION:
?
LENGTH:
?
A,N,A/N:
?
EXAMPLES:
?
REMARKS:
?
VALID CODES/FIELD
RESTRICTIONS:
TYPE-1
TCR
1.10
TRANSACTION CONTROL REFERENCE
OPTIONAL
10 - 40
A/N
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 requires a response. For a
case returned by the FBI for poor quality images,
this field would contain the FBI’s TCN when
resubmitting the case.
(i.e. IFCS00050000130729800)
This field will
also
be used to denote submissions
paid by an applicant’s credit card. Information
needed to indicate transaction paid via credit card
will
ONLY
be used on original submission. Data
required to indicate a credit card submission will be
provided by FDLE in policy/training material to
each
agency.
Interface Control Document
17
TYPE-1
FIELD IDENTIFIER:
NSR
FIELD NUMBER:
1.11
FIELD NAME:
NATIVE SCANNING RESOLUTION
FIELD CONDITION:
MANDATORY
LENGTH: 5
A,N,A/N: N/S
EXAMPLES:
REMARKS:
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 response data at a transmitting
resolution tailored to the NSR (if it is
able to do so) or to the minimum scanning
resolution. See the FBI’s Electronic
Fingerprint Transmission Specifications
dated January 1999, for further information
regarding
this
field.
VALID CODES/FIELD
RESTRICTIONS:
Period is only allowable special character.
Interface Control Document
18
TYPE-1
FIELD IDENTIFIER:
NTR
FIELD NUMBER:
1.12
FIELD NAME:
NOMINAL TRANSMISSION RESOLUTION
FIELD CONDITION:
MANDATORY
LENGTH: 5
A,N,A/N: N/S
EXAMPLES:
REMARKS:
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.
VALID CODES/FIELD
RESTRICTIONS:
Period only allowable special character.
Interface Control Document
19
APPENDIX B NIST TYPE-2 DEFINITIONS
?
Identifier Condition Field
Field name
Char
Field Size
Occurrences
#
Type
Min Max
Min Max
LEN
M
2.001
Logical Record Length
Numeric
2
5
1
1
Integer values only
IDC
M
2.002
Image Designation Char
Numeric
2
2
1
1
Integer values only
RET M
2.005
Retention
Code
Alpha
1
1
1
1
ATN
O
2.006
Attention Indicator
A/N/S
3
30
0
1
No periods
SCO
O
2.007
Send Copy to
A/N/S
9
19
0
9
OCA
O
2.009
Originating Agency Case #
A/N/S
1
20
0
1
No periods
FBI O
2.014
FBI
Number
A/N
1
9
0
1
SID
O
2.015
State Identification Number
A/N/S
3
10
0
1
No hyphen permitted
SOC
O
2.016
Social Security Number
Numeric
9
9
0
4
No hyphens. If no SSN, leave field blank.
MNU
O
2.017
Miscellaneous Id Number
A/N/S
4
15
0
4
Hyphen allowed as special character
NAM
M
2.018
Name
A/S
4
30
1
1
Format must include comma after last name.
NOTE 1
AKA
O
2.019
Aliases
A/S
4
30
0
10
Same formatting as Name field
POB
M
2.020
Place of Birth
Alpha
2
2
1
1
Allowable codes are listed in Part IV of NCIC Manual
CTZ
O
2.021
Country of Citizenship
Alpha
2
2
0
1
Allowable codes are listed in Part IV of NCIC Manual
DOB
M
2.022
Date of Birth
Numeric
8
8
1
5
CCYYMMDD
SEX M
2.024
Sex
Alpha
1
1
1
1
M,
F, X only valid codes accepted
RAC M
2.025
Race
Alpha
1
1
1
1
A,B,I,U,W only valid codes accepted
HGT
M
2.027
Height
Numeric
3
3
1
1
Height range is 4’00” to 7’11”
WGT
M
2.029
Weight
Numeric
3
3
1
1
Max allowable weight is 499 lbs
EYE
M
2.031
Eye Color
Alpha
3
3
1
1
See EFTS Ver 7 for valid eye color codes
HAI
M
2.032
Hair Color
Alpha
3
3
1
1
See EFTS Ver 7 for valid hair color codes
RFP
M
2.037
Reason for Fingerprinting
A/N/S
1
75
1
1
NOTE 2
DPR M
2.038
Date
Printed
Numeric
8
8
1
1
CCYYMMDD
EAD O
2.039
Employer
Name/Address
A/N/S
1
120
0
1
OCP O
2.040
Occupation
A/N/S
1
50
0
1
RES O
2.041
Residence
A/N/S
1
120
0
1
TSR
O
2.043
Type of Search Requested
Alpha
0
1
0
1
Applies to NFUF transactions.
IMA
O
2.067
Image Capture Equipment
A/N/S
1
100
1
1
See EFTS Ver 7 for complete field data
M:
Mandatory
O:
Optional
A: Alpha
A/N:
Alpha Numeric
A/N/S:
Alpha Numeric and Special character
20
Interface Control Document
APPENDIX B NIST TYPE-2 DEFINITIONS
?
Identifier Condition Field
#
Field name
Char
Type
Field Size
Occurrences
Min Max
Min Max
RAP O
2.070
Request
for
Rapsheet
A 1
1
0
1
CRI
M
2.073
Controlling Agency Ident
A/N/S
1
9
1
1
AMP
O/M
2.084
Amputated or Bandaged
A/N
2
2
0
9
See EFTS Ver 7 for complete field data
NOTE: 3
NOTE 1:
Name format is LAST
,
FIRST MIDDLE INITIAL. Comma, Blank, Hyphen are ONLY allowable special characters.
NOTE 2:
Comma, Blanks, Dashes, Hyphens and Slashes are only allowable special characters.
NOTE 3:
Field MUST be complete if image can not be taken.
Full description of Field List is found in EFTS Ver 7.
M:
Mandatory
O:
Optional
A: Alpha
A/N
Alpha Numeric
A/N/S:
Alpha Numeric and Special character
21
Interface Control Document
TYPE-2
FIELD IDENTIFIER:
LEN
FIELD NUMBER:
2.001
FIELD NAME:
LOGICAL RECORD LENGTH
FIELD CONDITION:
MANDATORY
LENGTH:
2 - 5
A,N,A/N: Numeric
EXAMPLES: 90909
REMARKS:
This mandatory ASCII field shall contain
the total count of the number of bytes in
the type 2 logical record. Field 2.001
shall begin with “2.001:”, followed by
the length of the record including every
character of every field contained in the
record and the information separators.
VALID CODES/FIELD
RESTRICTIONS:
Integer values only.
Interface Control Document
22
TYPE-2
FIELD IDENTIFIER:
IDC
FIELD NUMBER:
2.002
FIELD NAME:
IMAGE DESIGNATION CHARACTER
FIELD CONDITION:
MANDATORY
LENGTH:
2
A,N,A/N:
Numeric
EXAMPLES:
01
REMARKS:
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.
VALID CODES/FIELD
RESTRICTIONS:
Integer values only.
Interface Control Document
23
TYPE-2
FIELD IDENTIFIER:
RET
FIELD NUMBER:
2.005
FIELD NAME:
RETENTION CODE
FIELD CONDITION:
MANDATORY
LENGTH:
1
A,N,A/N:
A
EXAMPLES:
Y,
N
REMARKS:
This field indicates whether the
information submitted as part
of a transaction is to be retained
as a permanent part of the State’s
and the FBI’s Criminal Master File.
VALID CODES/FIELD
RESTRICTIONS:
Y - Indicates to retain
N - Indicates not to retain
Interface Control Document
24
TYPE-2
FIELD IDENTIFIER:
ATN
FIELD NUMBER:
2.006
FIELD NAME:
ATTENTION INDICATOR
FIELD CONDITION:
OPTIONAL
LENGTH:
3 - 30
A,N,A/N/S:
A/N/S
EXAMPLES:
ALEXANDER, JOHN PAUL
SMITH,B
REMARKS:
This field will indicate the
individual to whose attention
a response will be directed
VALID CODES/FIELD
RESTRICTIONS:
Can contain any 7 bit ASCII
character EXCEPT the period.
If the agency does not use this
field, it should not be included
as part of the NIST packet.
Interface Control Document
25
TYPE-2
FIELD IDENTIFIER:
SCO
FIELD NUMBER:
2.007
FIELD NAME:
SEND COPY TO
FIELD CONDITION:
OPTIONAL
LENGTH:
9 - 19
A,N,A/N/S:
A/N/S
EXAMPLES:
FL0370100
FL0370100:CWCS
REMARKS:
This field indicates that additional
electronic responses need to be
forwarded to an agency other
than the contributor.
VALID CODES/FIELD
RESTRICTIONS:
The first nine characters shall contain the
NCIC assigned ORI for the agency who is
to receive a copy of the response. At the
option of the transmitting agency, the ORI
may be expanded up to a size of 19 characters,
with 10 A/N/S characters appended to the end to
assist in proper routing. The state is responsible
for forwarding the copy of the electronic
response to each agency listed in this block.
If the agency does not use this field, it should
not be included as part of the NIST packet.
Interface Control Document
26
TYPE-2
FIELD IDENTIFIER:
OCA
FIELD NUMBER:
2.009
FIELD NAME:
ORIGINATING AGENCY CASE NUMBER
FIELD CONDITION:
OPTIONAL
LENGTH:
1
-20
A,N,A/N/S:
A/N/S
EXAMPLES:
PO5320030602
REMARKS:
This field contains the OCA that has been
assigned by the originating agency.
The length of the OCA for an applicant
transaction should be 15 characters. The
OCA field can not start with a blank.
VALID CODES/FIELD
RESTRICTIONS:
Any printable 7 bit ASCII character EXCEPT for
the period. If the agency does not use this field, it should
not be included as part of the NIST packet.
Interface Control Document
27
TYPE-2
FIELD IDENTIFIER:
FBI
FIELD NUMBER:
2.014
FIELD NAME:
FBI NUMBER
FIELD CONDITION:
OPTIONAL
LENGTH:
1 - 9
A,N,A/N/S:
A/N
EXAMPLES:
61753A3
012345678
REMARKS:
This field will contain the unique
number assigned by the FBI for the
individual as a permanent part of the
State’s and the FBI’s Criminal Master File.
VALID CODES/FIELD
RESTRICTIONS:
If the agency does not use this
field, it should not be included
as part of the NIST packet.
Interface Control Document
28
TYPE-2
FIELD IDENTIFIER:
SID
FIELD NUMBER:
2.015
FIELD NAME:
STATE IDENTIFICATION NUMBER
FIELD CONDITION:
OPTIONAL
LENGTH:
3 - 10
A,N,A/N/S:
A/N/S
EXAMPLES:
FL0586795
REMARKS:
This field indicates the unique number
assigned to a individual in the FDLE
Computerized Criminal History (CCH)
system. The number is prefixed with the
two character NCIC code for the state.
VALID CODES/FIELD
RESTRICTIONS:
Embedded blanks are prohibited.
No hyphen permitted. If the agency
does not use this field, it should not be
included as part of the NIST packet.
Interface Control Document
29
TYPE-2
FIELD IDENTIFIER:
SOC
FIELD NUMBER:
2.016
FIELD NAME:
SOCIAL SECURITY NUMBER
FIELD CONDITION:
OPTIONAL
LENGTH: 9
A,N,A/N: N
EXAMPLES: 123456789
001999945
REMARKS:
This field contains the individual’s
reported social security number.
VALID CODES/FIELD
RESTRICTIONS:
No hyphen permitted.
Value cannot be less than 001010001.
The social security number cannot be all
zeroes, eights or nines.
Fourth and fifth digits cannot equal
zeroes at the same time.
SSN starting with 9 is for non citizen
This field is not required and should
not be included in the NIST packet if
the data is not available or provided.
Interface Control Document
30
TYPE-2
FIELD IDENTIFIER:
MNU
FIELD NUMBER:
2.017
FIELD NAME:
MISCELLANEOUS IDENTIFICATION NUMBER
FIELD CONDITION:
OPTIONAL
LENGTH:
4 - 15
A,N,A/N/S:
A/N/S
EXAMPLES:
AF-123456789
REMARKS:
This field indicates any miscellaneous
identification
numbers associated with
the individual. Format for data shall be
a two letter identifying code, followed by
a hyphen (-), followed by the number itself.
VALID CODES/FIELD
RESTRICTIONS:
If “AF” or “AS” is entered, all characters
following the hyphen must be numeric.
Interspaced 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.
If the agency does not use this field,
it should not be included as part of
the NIST packet.
This field requires unique values and is not to be
used with any local agency numbering scheme.
Interface Control Document
31
TYPE-2
?
FIELD IDENTIFIER:
MNU (Continued)
Identifying Agency
Code
Air Force Serial Number
AF
Alien Registration Number
AR
Air National Guard Serial Number
AS
Army Serial Number
National Guard Serial Number
Bureau Fugitive Index Number
BF
Canadian Social Insurance Number
CI
U.S. Coast Guard Serial Number
CG
Identification Order Number
IO
Marine Corps Serial Number
MC
Mariner’s Document or Identification Number
MD
RCMP Identification or
MP
Fingerprint Section Number
National Agency Case Number
NA
Navy Serial Number
NS
Passport Number (U.S. ONLY)
PP
Port Security Card Number
PS
Selective Service Number
SS
Veterans Administrative Claim Number
VA
Interface Control Document
32
TYPE-2
FIELD IDENTIFIER:
NAM
FIELD NUMBER:
2.018
FIELD NAME:
NAME OF PERSON
FIELD CONDITION:
MANDATORY
LENGTH:
4 - 30
A,N,A/N: A/Special
EXAMPLES:
ALEXANDER, JOHN PAUL
SMITH,
B
KIPLING, JOYCE ALICE FAY
JONES-SMITH, JOHN KING JR
REMARKS:
This field should reflect the name
the individual used at the time of
processing.
VALID CODES/FIELD
RESTRICTIONS:
If an individual's name is being
reported, the following restrictions
will
apply:
Surname, followed by a comma and
space, first name or initial, space,
middle name or initial, space,
followed by additional names or
titles.
Only one comma may be used, and it
must follow the surname
.
No periods following initials or
titles or no numerals allowed.
Comma and space are included in
character count.
Valid characters are A-Z, hyphen,
space, and comma.
Interface Control Document
33
TYPE-2
FIELD IDENTIFIER:
AKA
FIELD NUMBER:
2.019
FIELD NAME:
ALIASES
FIELD CONDITION:
OPTIONAL
LENGTH:
4 - 30
A,N,A/N:
A/Special
EXAMPLES:
ALEXANDER, JOHN PAUL
SMITH,
B
REMARKS:
This field should reflect an alias
of the individual used either
in the past or currently.
VALID CODES/FIELD
RESTRICTIONS:
If an individual's name is being
reported, the following restrictions
will
apply:
Surname, followed by a comma and
space, first name or initial, space,
middle name or initial, space,
followed by additional names or
titles.
Only one comma may be used, and it
must follow the surname.
No periods following initials or
titles.
Comma and space are included in
character
count.
Valid characters are A-Z, hyphen,
space, and comma.
Name must be a complete name, not
street names, such as “Killer”.
Interface Control Document
34
TYPE-2
?
FIELD NAME:
ALISAS (Continued)
This field is not required and
can be omitted form the NIST record.
Interface Control Document
35
TYPE-2
FIELD IDENTIFIER:
POB
FIELD NUMBER:
2.020
FIELD NAME:
PLACE OF BIRTH
FIELD CONDITION:
MANDATORY
LENGTH: 2
A,N,A/N: A
EXAMPLES: GA
PR
REMARKS:
This field will be used to identify
the individual’s place of birth.
VALID CODES/FIELD
RESTRICTIONS:
The codes on the following pages
are EXAMPLES of codes used to
identify the state or country of birth.
Consult NCIC manual for complete list
.
Interface Control Document
36
TYPE-2
PLACE OF BIRTH
PLACE OF BIRTH (POB): THESE CODES ARE USED DURING ENTRY TO RECORD THE STATE
OR COUNTRY OF BIRTH OF THE SUBJECT. THESE ABBREVIATIONS ARE ALSO USED FOR
ENTRY OF A SUBJECT'S STATE OR COUNTRY OF RESIDENCE. THE LIST IS BROKEN DOWN
INTO (1) UNITED STATES, (2) UNITED STATES TERRITORIAL POSSESSIONS, (3) FOREIGN
COUNTRIES, AND (4) CANADIAN PROVINCES AND MEXICAN STATES.
UNITED STATES
ALABAMA
AL
MISSOURI
MO
ALASKA
AK
MONTANA
MT
ARIZONA
AZ
NEBRASKA
NB
ARKANSAS
AR
NEVADA
NV
CALIFORNIA
CA
NEW HAMPSHIRE
NH
COLORADO
CO
NEW JERSEY
NJ
CONNECTICUT
CT
NEW MEXICO
NM
DELAWARE
DE
NEW YORK
NY
DISTRICT OF COLUMBIA
DC
NORTH CAROLINA
NC
FLORIDA
FL
NORTH DAKOTA
ND
GEORGIA
GA
OHIO
OH
HAWAII
HI
OKLAHOMA
OK
IDAHO
ID
OREGON
OR
ILLINOIS
IL
PENNSYLVANIA
PA
INDIANA
IN
RHODE ISLAND
RI
IOWA
IA
SOUTH CAROLINA
SC
KANSAS
KS
SOUTH DAKOTA
SD
KENTUCKY
KY
TENNESSEE
TN
LOUISIANA
LA
TEXAS
TX
MAINE
ME
UTAH
UT
MARYLAND
MD
VERMONT
VT
MASSACHUSETTS
MA
VIRGINIA
VA
MICHIGAN
MI
WASHINGTON
WA
MINNESOTA
MN
WEST VIRGINIA
WV
MISSISSIPPI
MS
WISCONSIN
WI
WYOMING
WY
IF THE STATE OF BIRTH IS UNKNOWN AND THE SUBJECT IS A NATIVE AMERICAN, THE
CODE FOR THE UNITED STATES (US) MAY BE ENTERED.
Interface Control Document
37
TYPE-2
U.S. TERRITORIAL POSSESSIONS
AMERICAN SAMOA
AM
MARSHALL ISLANDS
MH
CANAL ZONE
CZ
MIDWAY ISLANDS
MW
CAROLINE ISLANDS
CG
PUERTO RICO
PR
GUAM
GM
U.S. VIRGIN ISLANDS
VI
MARIANA ISLANDS
MK
WAKE ISLAND
WK
FOREIGN COUNTRIES/DEPENDENCIES/TERRITORIES
?
AFGHANISTAN
AFRICA
ALBANIA
ALGERIA
ANDORRA
ANGOLA
ANTARCTICA
ANTIGUA
ARGENTINA
ARUBA
AUSTRALIA
AUSTRIA
BAHAMAS
BAHRAIN/BAHREIN IS
BARBADOS
BARBUDA
BELGIUM
BENIN
BERMUDA
BHUTAN
BOLIVIA
BONAIRE
BOTSWANA
BRAZIL
BRAZZAVILLE
BRITISH VIRGIN IS
BRUNEI
BULGARIA
BURKINA FASO
(UPPER VOLTA)
AF
CYPRUS
CS
AC
CZECHOSLOVAKIA
CK
AA
DAHOMEY (BENIN)
DH
AN
DENMARK
DK
AD
DOMINICA
DM
AO
DOMINICAN REPUBLIC
DR
AY
EAST GERMANY
GE
AI
ECUADOR
EU
AT
EGYPT (UNITED ARAB REP)
EY
NX
EL SALVADOR
EL
AS
ENGLAND
EN
AU
EQUATORIAL GUINEA
EK
BD
ESTONIA
ES
BE
ETHIOPIA
EO
BB
FIJI
FJ
AI
FINLAND
FD
BG
FRANCE
FN
DH
GABON
GB
BM
GAMBIA
GK
BN
GERMANY (GERMAN DEM REP)
GE
BV
GHANA
GG
NX
GIBRALTAR
RG
BT
GREAT BRITAIN
BZ
**(SEE EN, SS, WL, NI)
RB
GREECE
GC
VB
GREENLAND
GN
BX
GRENADA
GJ
BU
GUADELOUPE
GP
GUATEMALA
GT
UV
GUINEA
GI
Interface Control Document
38
TYPE-2
?
FOREIGN COUNTRIES/DEPENDENCIES/TERRITORIES
(Continued)
?
BURMA
BURUNDI
CAMBODIA
CAMEROON
CANADA****
CANARY ISLANDS
CAPE VERDE ISLANDS
CAYMEN ISLANDS
CENTRAL AFRICA REP
CEYLON (SRI LANKA)
CHAD
CHILE
CHINA
**PEOPLES REP OF CHINA
**TAIWAN
COLUMBIA
CONGO KINSHASA (ZAIRE)
CONGO, REPUBLIC OF
COSTA RICA
CUBA
KOREA
**NORTH KOREA
**SOUTH KOREA
KUWAIT
LAOS
LATVIA
LEBANON
LESOTHO
LIBERIA
LIBYA
LIECHTENSTEIN
LITHUANIA
LUXEMBOURG
MACAO/MACAU
MADAGASCAR/MALAGASY
REP
MALAWI
MALAYSIA
BR
BI
CJ
CM
CD
ZI
CV
CP
CW
CY
CF
CQ
CN
RC
TW
CB
ZR
RB
CR
CC
KN
KO
KU
LS
LT
LN
LE
LB
LY
LI
LH
LX
OC
MP
MF
MZ
GUINEA-BISSAU
PG
GUIANA/GUYANA
GY
HAITI
HT
HOLLAND
NE
HONDURAS
HD
HONG KONG
HK
HUNGARY
HU
ICELAND
IC
INDIA (SIKKIM)
II
INDONESIA
IO
IRAN
IR
IRAQ
IQ
IRELAND (NOT N IRELAND)
IE
ISRAEL
IS
ITALY (SICILY/SARDINIA)
IT
IVORY COAST
IY
JAMAICA
JM
JAPAN
JA
JORDAN
JO
KENYA
KE
POLAND
PO
PORTUGAL
PT
PORTUGUESE GUINEA
PG
PORTUGUESE TIMOR
IO
QATAR
QA
REPUBLIC OF CHINA
RC
REPUBLIC OF CONGO
RB
REUNION
RE
RHODESIA (ZIMBABWE)
RH
RUMANIA/ROMANIA
RU
RUSSIA (USSR)
SX
RWANDA
RW
ST PIERRE AND MIQUELON
PS
ST VINCENT AND GRENADINES
VV
SAN MARINO
SH
SAO TOME AND PRINCIPE
TP
SARDINIA
IT
Interface Control Document
39
TYPE-2
?
FOREIGN COUNTRIES/DEPENDENCIES/TERRITORIES
(Continued)
?
MALDIVES
MALI
MALTA
MAURITANIA
MAURITIUS
MEXICO****
MONACO
MONGOLIA
MOROCCO
MOZAMBIQUE
NAMIBIA
NAURU
NEPAL
NETHERLANDS
NETHERLANDS ANTILLES
NEW CALEDONIA
NEW GUINEA
NEW ZEALAND
NICARAGUA
NIGER
NIGERIA
NORTH KOREA
NORTH VIETNAM
NORTHERN IRELAND
NORWAY
OMAN
PAKISTAN
PANAMA
PAPUA NEW GUINEA
PARAGUAY
PEOPLES REP OF CHINA
PERU
PHILIPPINES
PITCAIRN ISLAND
TUNISIA
TURKEY
TURKS AND CAICOS IS
(BRITISH COLONY)
MV
ML
MY
MU
UM
MM
MJ
MG
MQ
ZO
SJ
NR
NP
NE
NX
NQ
NO
NZ
NU
NN
NG
KN
RV
NI
NW
OM
PK
PM
NO
PV
RC
PU
PI
PC
TU
TY
TR
SAUDI ARABIA
SB
SCOTLAND
SS
SENEGAL
SG
SEYCHELLES
SE
SICILY
IT
SIERRA LEONE/SIERRE LEONE
SA
SIKKIM (INDIA)
II
SINGAPORE
SR
SOMALIA
SM
SOUTH AFRICA
SF
SOUTH KOREA
KO
SOUTH VIETNAM
RV
SOUTHERN YEMEN
RY
OUTH-WEST AFRICA
SJ
SOVIET UNION (USSR)
SX
SPAIN
SP
SPANISH SAHARA
RS
SRI LANKA
CY
SUDAN
SU
SURINAM
ZC
SVALBARD
SV
SWAZILAND
SW
SWEDEN
SQ
SWITZERLAND
SZ
SYRIA
SY
TAIWAN
TW
TANZANIA (UNITED REP OF)
TZ
THAILAND
TH
TIMOR PORTUGUESE
IO
TOGO
TO
TONGA
TG
TRINIDAD/TOBAGO
TT
TRUCIAL STATES
(UNITED ARAB EMIRATES)
TC
VIETNAM, SOCIALIST REP OF
**NORTH VIETNAM
RV
**SOUTH VIETNAM
VIRGIN ISLANDS, BRITISH
VB
Interface Control Document
40
TYPE-2
?
FOREIGN COUNTRIES/DEPENDENCIES/TERRITORIES
(Continued)
?
UGANDA
UG
WALES
WL
UNITED ARAB EMIRATES
TC
WEST GERMANY
GE
UNITED ARAB REPUBLIC
EY
WEST INDIES
WN
UNITED KINGDOM
WESTERN SAHARA
RS
**(SEE EN, SS, WL, NI)
WESTERN SAMOA
WS
UPPER VOLTA
UV
YEMEN, REP OF
RY
URUGUAY
UY
YUGOSLAVIA
YG
USSR (SOVIET UNION)
SX
ZAIRE (CONGO KINSHASA)
ZR
VENEZUELA
VZ
ZAMBIA
ZM
ZIMBABWE (RHODESIA)
RH
****SEE SEPARATE LIST OF CANADIAN PROVINCES AND MEXICAN STATES. USE CODE CD
OR MM ONLY WHEN PROVINCE OR STATE IS NOT KNOWN.
CANADIAN PROVINCES AND MEXICAN STATES
CANADIAN PROVINCES
ALBERTA
AB
ONTARIO ON BRITISH COLUMBIA
BC
PRINCE EDWARD ISLAND
PE
MANITOBA
MB
QUEBEC
PQ
NEW BRUNSWICK
NK
SASKATSCHEWAN
SN
NEWFOUNDLAND (LABRADOR)
NF
YUKON TERRITORY
YT
NOVA SCOTIA
NS
NORTHWEST TERRITORY
NT
MEXICAN STATES
(BORDER STATES)
BAJA, CA (NTE.)
COAHUILA
CU
(TERRITORY NORTH)
BA
NUEVO LEON
NL
BAJA, CA (SUR.)
SONORA
SO
(TERRITORY SOUTH)
BJ
TAMAULIPAS
TA
CHIHUAHUA
CH
Interface Control Document
41
DURANGO
SAN LUIS POTOSI
SINALOA
AGUASCALIENTES
CAMPECHE
CHIAPAS
COLIMA
DISTRITO FEDERAL
(MEXICO, D.F.)
GUANAJUATO
GUERRERO
HIDALGO
JALISCO
TYPE-2
MEXICAN STATES
(NEXT LAYER OF STATES)
DO
SL
SI
VERACRUZ
ZACATECAS
VC
ZA
MEXICAN STATES
(OTHER STATES)
AG
MEXICO (STATE)
MX
CE
MICHOACAN
MC
CI
MORELOS
MR
CL
OAXACA
OA
PUEBLA
PB
DF
QUERETARO
QU
GU
QUINTANA ROO
QR
GR
TABASCO
TB
HL
TLAXCALA
TL
JL
YUCATAN
YU
Interface Control Document
42
TYPE-2
FIELD IDENTIFIER:
CTZ
FIELD NUMBER:
2.021
FIELD NAME:
COUNTRY OF CITIZENSHIP
FIELD CONDITION:
OPTIONAL
LENGTH: 2
A,N,A/N: A
EXAMPLES: AF
REMARKS:
This field will be used to identify
the individual’s country of citizenship.
VALID CODES/FIELD
RESTRICTIONS:
The codes on the preceding pages
are EXAMPLES used to identify the country
of citizenship. Consult NCIC manual for
complete
list.
Interface Control Document
43
TYPE-2
FIELD IDENTIFIER:
DOB
FIELD NUMBER:
2.022
FIELD NAME:
BIRTH DATE OF PERSON
FIELD CONDITION:
MANDATORY
LENGTH: 8
A,N,A/N:
N
EXAMPLES:
19570607
20000607
REMARKS:
This field contains the individual’s
reported date of birth.
VALID CODES/FIELD
RESTRICTIONS:
Must be eight numeric characters
consisting of four two digit
subfields which correspond to the
century, year, month, and day.
Must be in century, year, month and
day (CCYYMMDD) format.
The value of the century subfield
must be 19 or when it becomes
appropriate
20.
The value of the year subfield must
be 00 to 99.
The value of the month subfield must
be 01 to 12.
The value of the day subfield must
be 01 to 28, 29, 30, 31, inclusive
depending on the month and year
indicated.
Interface Control Document
44
TYPE-2
?
FIELD NAME:
BIRTH DATE OF PERSON (Continued)
If the exact date of birth is
unknown, the month and day subfields
should contain zeroes and the value
of the year subfield
should
contain
the year of birth.
The month subfield cannot contain
zeroes unless the day subfield also
contains
zeroes.
Interface Control Document
45
TYPE-2
FIELD IDENTIFIER:
SEX
FIELD NUMBER:
2.024
FIELD NAME:
SEX OF INDIVIDUAL
FIELD CONDITION:
MANDATORY
LENGTH: 1
A,N,A/N: A
EXAMPLES: M
F
X
REMARKS:
This field should reflect the sex of
the
individual.
VALID CODES/FIELD
RESTRICTIONS:
M - Male
F – Female
X – Unknown
Interface Control Document
46
TYPE-2
?
FIELD IDENTIFIER:
RAC
FIELD NUMBER:
2.025
FIELD NAME:
RACE OF INDIVIDUAL
FIELD CONDITION:
MANDATORY
LENGTH: 1
A,N,A/N: A
EXAMPLES: W
B
REMARKS:
This field should reflect the race
of the individual.
VALID CODES/FIELD
RESTRICTIONS:
W - White (includes Mexicans)
B - Black
A - Oriental/Asian
I - American Indian/Alaskan Native
U - Unknown
NOTE: HISPANIC IS NOT A RACE, BUT AN ETHNICITY. HISPANIC INDIVIDUALS SHOULD
BE INDICATED AS EITHER WHITE OR BLACK, WHICHEVER IS APPROPRIATE.
Interface Control Document
47
TYPE-2
FIELD IDENTIFIER:
HGT
FIELD NUMBER:
2.027
FIELD NAME:
HEIGHT
FIELD CONDITION:
MANDATORY
LENGTH:
3
A,N,A/N:
N
EXAMPLES:
411
402
REMARKS:
This field should reflect the height
of the individual in feet and inches.
VALID CODES/FIELD
RESTRICTIONS:
The first number will be feet.
The second and third numbers will be
inches. If the number is less than
ten it will be preceded by zero.
Examples: If a person is 4 feet
nine inches it will be recorded as
409. If a person is 5 feet 11
inches it will be recorded as 511.
A height of less than 4 feet or
greater than 7 feet 11 inches cannot
be entered in this field. If the
reported height is less than the
minimum, enter the minimum. If
greater than the maximum, enter the
maximum. Fractions of an inch
should be rounded to the nearest
inch.
Interface Control Document
48
TYPE-2
FIELD IDENTIFIER:
WGT
FIELD NUMBER:
2.029
FIELD NAME:
WEIGHT
FIELD CONDITION:
MANDATORY
LENGTH:
3
A,N,A/N:
N
EXAMPLES:
070
175
REMARKS:
This field should reflect the weight
of the individual.
VALID CODES/FIELD
RESTRICTIONS:
A weight less than 50 pounds cannot
be entered. If the weight is less
than 50 pounds, enter the minimum.
Weight less than 100 pounds will start with
a zero (0). 99 pounds will be entered as 099.
A weight greater than 499 pounds
cannot be entered. If the weight is
greater than 499 pounds, enter the
maximum.
Interface Control Document
49
TYPE-2
FIELD IDENTIFIER:
EYE
FIELD NUMBER:
2.031
FIELD NAME:
EYE COLOR
FIELD CONDITION:
MANDATORY
LENGTH:
3
A,N,A/N:
A
EXAMPLES:
BLK
HAZ
REMARKS:
This field should reflect the eye
color of the individual.
VALID CODES/FIELD
RESTRICTIONS:
BLK Black
HAZ
Hazel
BLU Blue
MAR Maroon
BRO Brown
PNK
Pink
GRN
Green
GRY Gray or partly gray
MUL Multicolored
XXX
Unknown
Interface Control Document
50
TYPE-2
FIELD IDENTIFIER:
HAI
FIELD NUMBER:
2.032
FIELD NAME:
HAIR COLOR
FIELD CONDITION:
MANDATORY
LENGTH:
3
A,N,A/N:
A
EXAMPLES:
BLK
RED
REMARKS:
This field should reflect the hair
color of the individual.
VALID CODES/FIELD
RESTRICTIONS:
BAL Bald
RED Red
BLK Black
SDY
Sandy
BLN Blonde or strawberry
WHI White
BRO Brown
GRY
Gray
XXX
Unknown
BLU Blue
GRN Green
ONG Orange
PNK Pink
PLE
Purple
Interface Control Document
51
TYPE-2
FIELD IDENTIFIER:
RFP
FIELD NUMBER:
2.037
FIELD NAME:
REASON FINGERPRINTED
FIELD CONDITION:
MANDATORY
LENGTH:
1 - 75
A,N,A/N:
A/N & Special Characters
EXAMPLES: APPLICANT
BACKGROUND
CHECK
REMARKS:
This field should reflect the reason
the fingerprinting occurred and, as
appropriate, should be formatted as
required by FBI for specific types of
background
check
requests.
VALID CODES/FIELD
RESTRICTIONS:
Commas, blanks, dashes, slashes, and
hyphens only allowable special characters.
Interface Control Document
52
TYPE-2
FIELD IDENTIFIER:
DPR
FIELD NUMBER:
2.038
FIELD NAME:
DATE FINGERPRINTED
FIELD CONDITION:
MANDATORY
LENGTH:
8
A,N,A/N:
N
EXAMPLES:
19950607
19940924
REMARKS:
This field should reflect the date
the fingerprinting occurred.
VALID CODES/FIELD
RESTRICTIONS:
Must be eight numeric characters
consisting of four two digit
subfields which correspond to the
century, year, month, and day.
Must be in century, year, month, and
day (CCYYMMDD) format.
The value of the century subfield
must be 19 or when it becomes
appropriate
20.
The value of the year subfield must
be 00 to 99.
The value of the month subfield must
be 01 to 12.
The value of the day subfield must
be 01 to 28, 29, 30, 31, inclusive
depending on the month and year
indicated.
Interface Control Document
53
TYPE-2
FIELD IDENTIFIER:
EAD
FIELD NUMBER:
2.039
FIELD NAME:
EMPLOYER AND ADDRESS
FIELD CONDITION:
OPTIONAL
LENGTH:
1 - 120
A,N,A/N:
A/N & Special Characters
EXAMPLES:
ALEXANDER, JOHN PAUL
SMITH’S
JEWELRY
BOB’S
PLUMBING AND ELECTRIC,
235 Hummingbird Ln, Waco, Tx
REMARKS:
An individual's name or business name
may be recorded in this field.
This field should reflect the name of
the individual’s employer.
.
VALID CODES/FIELD
RESTRICTIONS:
If an individual's name is being
reported, the following restrictions
will
apply:
Surname, followed by a comma and
space, first name or initial, space,
middle name or initial, space,
followed by additional names or
titles.
Only one comma may be used, and it
must follow the surname. No periods
following initials or titles.
Valid characters are any 7-bit ASCII character.
If the agency does not use this field,
it should not be included as part of
the NIST packet.
Interface Control Document
54
TYPE-2
FIELD IDENTIFIER:
OCP
FIELD NUMBER:
2.040
FIELD NAME:
OCCUPATION
FIELD CONDITION:
OPTIONAL
LENGTH:
1 - 50
A,N,A/N/S:
A/N/S
EXAMPLES:
Sanitation
Engineer
Teacher
REMARKS:
This field contains the individual’s
occupation.
VALID CODES/FIELD
RESTRICTIONS:
If the agency does not use this field,
it should not be included as part of
the NIST packet.
Any printable 7 bit ASCII character permitted.
Interface Control Document
55
TYPE-2
FIELD IDENTIFIER:
RES
FIELD NUMBER:
2.041
FIELD NAME:
RESIDENCE OF PERSON FINGERPRINTED
FIELD CONDITION:
OPTIONAL
LENGTH:
1 - 120
A,N,A/N:
A/N/S
EXAMPLES:
Route 4 Box 500, Ft. Myers, Fl.
506 South North St, Tallahassee, Fl.
REMARKS:
This field should reflect the
current address of the individual.
VALID CODES/FIELD
RESTRICTIONS:
Any printable 7-bit ASCII character
is
allowed.
This field is not required and can be
omitted from the NIST packet.
Interface Control Document
56
TYPE-2
FIELD IDENTIFIER:
TSR
FIELD NUMBER:
2.043
FIELD NAME:
TYPE OF SEARCH REQUESTED
FIELD CONDITION:
OPTIONAL
LENGTH:
1
A,N,A/N:
A
EXAMPLES:
V
REMARKS:
This
field
is
only
used with NFUF
transactions and pertains to
civil submissions in support of the
National Child Protection Act of 1993.
VALID CODES/FIELD
RESTRICTIONS:
V – Indicates volunteer.
If field not used, do not include in
NIST packet.
Interface Control Document
57
TYPE-2
FIELD IDENTIFIER:
IMA
FIELD NUMBER:
2.067
FIELD NAME:
IMAGE PROCESSING FIELD
FIELD CONDITION:
OPTIONAL * (see restrictions)
LENGTH:
1 - 100
A,N,A/N:
A/N/S
EXAMPLES:
FREE
TEXT
REMARKS:
This is an FBI field.
This free text field is used to log
the make, model, and serial number
of the equipment used to acquire
images.
VALID CODES/FIELD
RESTRICTIONS:
The make, model and serial number of
the acquisition device shall be
separated by the US separator
character.
This
field
is
MANDATORY
for submissions to FDLE.
The submission must correctly identify the device used
to capture the fingerprints, either electronic or via
scanned images from inked cards. (See NIST field 1.09
TCN for additional information on submission
identification.)
Interface Control Document
58
TYPE-2
FIELD IDENTIFIER:
?
RAP
FIELD NUMBER:
?
2.070
FIELD NAME:
?
REQUEST FOR ELECTRONIC RAPSHEET
FIELD CONDITION:
?
OPTIONAL
LENGTH:
?
1
A,N,A/N:
?
A
EXAMPLES:
?
2.070:Y
Electronic rapsheet requested
2.070:N
or
2.070:
?
Electronic rapsheet NOT desired
?
REMARKS:
?
This is an optional field .The recipient will get either
an IDRR if an Ident was made or an NIDR is results
are
Non-Ident.
A “Y” indicates a rapsheet is desired and an omitted
field or an “N” indicates that no electronic rapsheet
should be returned with the response.
.
VALID CODES/FIELD
RESTRICTIONS:
.
Interface Control Document
59
TYPE-2
FIELD IDENTIFIER:
CRI
FIELD NUMBER:
2.073
FIELD NAME:
CONTROLLING AGENCY IDENTIFIER
FIELD CONDITION:
MANDATORY
LENGTH:
1 - 9
A,N,A/N:
A/N/S
EXAMPLES:
FREE
TEXT
(RESERVED)
REMARKS:
This free text field is used to identify
the requesting agency. Will contain the
requesting agency’s ORI.
VALID CODES/FIELD
RESTRICTIONS:
Interface Control Document
60
TYPE-2
FIELD IDENTIFIER:
AMP
FIELD NUMBER:
2.084
FIELD NAME:
AMPUTATED OR BANDAGED
FIELD CONDITION:
OPTIONAL/MANDATORY
LENGTH:
2
A,N,A/N:
A/N
EXAMPLES:
REMARKS:
2.084:03\uXX\r09\uUP\g
Finger three amputated and finger 9 bandaged
where \u = unit separator (ASCII code 31)
\r = record separator (ASCII code 30)
\g = group separator (ASCII code 29)
This is mandatory ONLY when there are less than
ten (10) fingerprint images taken. The field is
comprised of two subfields, the Finger Number (FGP)
and Amputated or Bandaged Code (AMPCD).
The two character finger position is followed by
the unit separator and the amputated or bandaged code.
Multiple missing digits shall be separated by the
record
separator.
VALID CODES/FIELD
RESTRICTIONS:
This field is not required and
should contain spaces if the data is
not
available.
FINGER
POSITION FGN
Right
Thumb
Right
Index
Right
Middle
Right
Ring
Right
Little
Left
Thumb
Left
Index
Left
Middle
Left
Ring
Left
Little
01
02
03
04
05
06
07
08
09
10
DESCRIPTOR
Amputation
Unable to Print
(i.e.
bandaged)
AMPCD
XX
UP
Interface Control Document
61
TYPE-2
?
FIELD IDENTIFIER:
AMP (CONTINUED)
VALID CODES/FIELD
RESTRICTIONS:
IF IMAGE IS TAKEN, DO NOT
INCLUDE AMP CODE. AMP CODE
IS ONLY TO BE USED IF IMAGE CAN
NOT BE TAKEN FOR ANY REASON.
Interface Control Document
62