WIN-4.1.0-Reference-Guide.pdf

WIN EBTS 4.1.0

Western Identification Network

Reference Guide

This Document Produced for WIN by

Aware, Inc.

76 Blanchard Road

Burlington, MA 01803

NECAM Support Center

844-632-2247 necam@servicenowservices.com

Copyright © 2024 Aware, Inc.

All Rights Reserved

Published in the U.S.A.

mailto:necam@servicenowservices.com

Western Identification Network (WIN) Technical Support

WIN members who have questions or believe they have identified an issue or error in the WIN EBTS Specification (AWARE Reference Guide or Verification File) and wish to report them are to utilize the NECAM National Support Center (NSC).

NECAM Support Center (NSC) Contact Information 844-632-2247 necam@servicenowservices.com

Inquiries may also be submitted to the following :

Chad Butler Chad@winid.org Gary Goad gary@winid.org

Masahiro Suzuki masahiro.suzuki@necam.com Anil Alavilli Anil.Alavilli@necam.com Nagabaji Kakumanu nagabaji.kakumanu@necam.com

Manual generated November 11, 2024.

mailto:necam@servicenowservices.com mailto:Chad@winid.org mailto:gary@winid.org mailto:masahiro.suzuki@necam.com mailto:Anil.Alavilli@necam.com mailto:nagabaji.kakumanu@necam.com

CONTENTS v

Contents

1 Preface 1

2 Introduction 3

2.1 Background

2.2 File Format

2.3 Change Control

2.4 Error Handling

2.5 Identifying Previous Transactions

2.6 Data Storage in WIN/FBI/CJIS Database

2.7 Guidance on ORI and CRI Usage

3 Scope 7

3.1 Identification Service

3.2 Verification Service

3.3 Information Service

3.4 Investigation Service

3.5 Notification Service

3.6 Data Management Service

4 Services and Transaction Types 9

4.1 Identification Service

4.2 Verification Service

4.3 Information Service

4.4 Investigation Service

4.5 Notification Service

4.6 Data Management Service

4.7 Error Message Format

4.8 Other Special Requirements For Communicating With FBI/CJIS

5 WIN and FBI Transaction Response Times 49

5.1 Average Transaction Response Times

5.2 NGI Type of Transaction by Service

6 Type-2 Field Allocations For FBI/WIN 53

7 Fields Not Validated 55

8 Transaction Services 57

8.1 Tenprint Fingerprint Identification SubmissionS

8.2 Rapid Fingerprint Identification Search Submission

8.3 Disposition Fingerprint Submission

8.4 Iris Identification Search Submission

8.5 Verification Submission

8.6 Biometric Image Retrieval Submission

8.7 Criminal Subject Photo Images Submission

8.8 Biometric Audit Trail Retrieval Submission

8.9 Rap Back Information Retrieval Submission

8.10 Tenprint Fingerprint Investigation Submissions

8.11 Latent Friction Ridge Investigation Submissions

8.12 Photo Investigation Submissions

8.13 Data Management Service Submission

8.14 Identification Service Responses

8.15 Information Service Responses

8.16 Investigative Service Responses

8.17 Notification Service Responses

WIN EBTS Version 4.1.0 Reference Guide vi CONTENTS

8.18 Data Management Service Responses

8.19 Washington State Patrol Transactions

8.20 WIN Internal Transactions

9 Transaction Record Requirements 61

10 Transaction Field Requirements 63

10.1 CAR - Criminal Tenprint Submission - Answer Required

10.2 CNA - Criminal Tenprint Submission - No Answer Required

10.3 FANC - Federal Applicant - No Charge

10.4 FAUF - Federal Applicant - User Fee

10.5 NFUF - Non-Federal Applicant User Fee

10.6 MAP - Miscellaneous Applicant - Civil

10.7 DEK - Known Deceased

10.8 DEU - Unknown Deceased

10.9 MPR - Missing Person

10.10AMN - Amnesia Victim 10.11RPIS - Rapid Fingerprint Identification Search 10.12FDSP - Electronic Fingerprint Disposition Submission 10.13IIDS - Iris Identification Search Submission 10.14FVR - Fingerprint Verification Request 10.15IRQ - Biometric Image/Feature Retrieval Request 10.16CPR - Subject Photo Request 10.17BATQ - Biometric Audit Trail Query 10.18RBRPT - Rap Back Subscription List Request 10.19RBIHS - Rap Back Identity History Summary Request 10.20TPIS - Tenprint Fingerprint Image Search 10.21LFIS - Latent Friction Ridge Image Search 10.22LFFS - Latent Friction Ridge Features Search 10.23FRS - Facial Recognition Search Request 10.24TXTSRCH - Text Based Photo/SMT Search Request 10.25ULD - Unsolved Latent Record Delete Request 10.26FIS - Biometric Image Submission 10.27BDEL - Biometric Delete Request 10.28CPD - Subject Photo Delete Request 10.29CDEL - Civil Event Deletion Request 10.30BDEC - Biometric Decision Submission 10.31DSPE - Disposition File Maintenance Submission 10.32RBSCRM - Rap Back Subsequent Subscription Request - Criminal 10.33RBSCVL - Rap Back Subsequent Subscription Request - Civil 10.34RBMNT - Rap Back Maintenance Request 10.35RPISR - Rapid Fingerprint Identification Search Response 10.36SRE - Submission Results - Electronic 10.37ERRT - Tenprint Transaction Error 10.38ERRB - Biometric Search Error 10.39BATR - Biometric Audit Trail Response 10.40IRR - Image Request Response 10.41ERRI - Information Transaction Error 10.42PRR - Photo Request Response 10.43RBIHSR - Rap Back Identity History Summary Response 10.44RBRPTR - Rap Back Subscription List Response 10.45SRT - Search Results - Tenprint 10.46SRL - Search Result - Latent 10.47SRB - Search Results - Biometric 10.48ULM - Unsolved Latent Match Notification 10.49UUBD - Unsolicited Unsolved Biometric Delete 10.50UULD - Unsolicited Unsolved Latent Delete 10.51RBN - Rap Back Activity Notification

CONTENTS vii

10.52RBRN - Rap Back Renewal Notification 10.53PDR - Subject Photo Delete Response 10.54BDECR - Biometric Decision Response 10.55ULDR - Unsolved Latent Record Delete Response 10.56BDELR - Biometric Delete Response 10.57FISR - Biometric Image Submission Response 10.58DSPR - Disposition File Maintenance Response 10.59CDELR - Civil Event Deletion Response 10.60RBSR - Rap Back Subscription Response 10.61RBMNTR - Rap Back Maintenance Response 10.62XMNTR - External System Link Maintenance Response 10.63DOC - Department of Corrections 10.64SOR - Sex/Kidnapping Offender registration 10.65WFIS - WIN Internal Fingerprint Image Submission 10.66WFISR - WIN Internal Fingerprint Image Submission Response

11 Field Rules for Type 2 Records 117

2.001 T2 LEN - Logical Record Length

2.002 T2 IDC - Information Designation Character

2.005 T2 RET - Retention Code

2.005 T2 RET - Retention Code (2)

2.006 T2 ATN - Attention Indicator

2.007 T2 SCO - Send Copy To

2.009 T2 OCA - Originating Agency Case Number

2.010 T2 CIN - Contributor Case Identifier Number

2.010 T2 CIN PRE - Contributor Case Prefix

2.010 T2 CIN ID - Contributor Case Identifier

2.010 T2 CIN - Contributor Case Identifier Number (2)

2.010 T2 CIN PRE - Contributor Case Prefix (2)

2.010 T2 CIN ID - Contributor Case Identifier (2)

2.011 T2 CIX - Contributor Case Identifier Extension

2.011 T2 CIX - Contributor Case Identifier Extension (2)

2.014 T2 FBI - FBI Number/UCN

2.014 T2 FBI - FBI Number/UCN (2)

2.014 T2 FBI - FBI Number/UCN (3)

2.014 T2 FBI - FBI Number/UCN (4)

2.014 T2 FBI - FBI Number/UCN (5)

2.015 T2 SID - State Identification Number

2.016 T2 SOC - Social Security Account Number

2.017 T2 MNU - Miscellaneous Identification Number

2.018 T2 NAM - Name

2.018 T2 NAM - Name (2)

2.019 T2 AKA - Aliases

2.020 T2 POB - Place of Birth

2.021 T2 CTZ - Country of Citizenship

2.021 T2 CTZ - Country of Citizenship (2)

2.022 T2 DOB - Date of Birth

2.022 T2 DOB - Date of Birth (2)

2.023 T2 AGR - Age Range

2.024 T2 SEX - Sex

2.025 T2 RAC - Race

2.026 T2 SMT - Scars, Marks, and Tattoos

2.026 T2 SMT - Scars, Marks, and Tattoos (2)

2.027 T2 HGT - Height

2.028 T2 HTR - Height Range

2.029 T2 WGT - Weight

2.030 T2 WTR - Weight Range

2.031 T2 EYE - Color Eyes

viii CONTENTS

2.032 T2 HAI - Hair Color

2.033 T2 FPC - NCIC Fingerprint Classification

2.034 T2 PAT - Pattern Level Classifications

2.034 T2 PAT FGP - Finger Position

2.034 T2 PAT PATCL - Pattern Classification Code

2.035 T2 PPA - Palm Prints Available Indicator

2.036 T2 PHT - Photo Available Indicator

2.037 T2 RFP - Reason Fingerprinted

2.038 T2 DPR - Date Printed

2.039 T2 EAD - Employer and Address

2.040 T2 OCP - Occupation

2.041 T2 RES - Residence of Person Fingerprinted

2.042 T2 MIL - Military Code

2.043 T2 TSR - Type of Search Requested

2.043 T2 TSR - Type of Search Requested (2)

2.044 T2 GEO - Geographical Area of Search

2.045 T2 DOA - Date of Arrest

2.046 T2 DOS - Date of Arrest - Suffix

2.047 T2 ASL - Arrest Segment Literal

2.047 T2 ASL DOO - Date of Offense

2.047 T2 ASL AOL - Arrest Offense Literal

2.051 T2 CSL - Court Segment Literal

2.051 T2 CSL CDD - Court Disposition Date

2.051 T2 CSL COL - Court Offense Literal

2.051 T2 CSL CPL - Other Court Sentence Provision Literal

2.051 T2 CSL CDN - Court Disposition

2.051 T2 CSL CCT - Court Count Number

2.053 T2 OFC - Offense Category

2.054 T2 SSD - Custody or Supervisory Status - Start Date

2.055 T2 SLE - Custody or Supervisory Status Literal

2.056 T2 ICO - Identification Comments

2.057 T2 FNR - Finger Number(s) Requested

2.059 T2 SRF - Search Results Findings

2.059 T2 SRF - Search Results Findings (2)

2.059 T2 SRF - Search Results Findings (3)

2.060 T2 MSG - Status/Error Message

2.060 T2 MSG ERD - Date/Time Stamp

2.060 T2 MSG ERC - Error Code

2.060 T2 MSG ECF - Error Condition Field

2.060 T2 MSG MD1 - Error Description Segment 1

2.060 T2 MSG EI1 - Element Insert 1

2.060 T2 MSG MD2 - Error Description Segment 2

2.060 T2 MSG EI2 - Element Insert 2

2.060 T2 MSG MD3 - Error Description Segment 3

2.060 T2 MSG EI3 - Element Insert 3

2.060 T2 MSG MD4 - Error Description Segment 4

2.060 T2 MSG EIC - Element Insert Count

2.060 T2 MSG - Status/Error Message (2)

2.060 T2 MSG - Status/Error Message (3)

2.060 T2 MSG - Status/Error Message (4)

2.060 T2 MSG - Status/Error Message (5)

2.061 T2 CST - Case Title

2.062 T2 IMT - Image Type

2.062 T2 IMT - Image Type (2)

2.064 T2 CAN - Candidate List

2.064 T2 CAN UCN - Universal Control Number

2.064 T2 CAN NAM - Name

CONTENTS ix

2.064 T2 CAN - Candidate List (2)

2.064 T2 CAN UCN - State Identification Number (2)

2.064 T2 CAN NAM - Name (2)

2.067 T2 IMA - Image Capture Equipment

2.067 T2 IMA MAK - Equipment Originating Fingerprint Reading System Make

2.067 T2 IMA MODL - Originating Fingerprint Reading System Model

2.067 T2 IMA SERNO - Originating Fingerprint Reading System Serial Number

2.070 T2 RAP - Request for Electronic Rap Sheet

2.071 T2 ACN - Action to be Taken

2.072 T2 FIU - Fingerprint Image(s) Updated

2.073 T2 CRI - Controlling Agency Identifier

2.074 T2 FGP - Friction Ridge Generalized Position

2.074 T2 FGP - Friction Ridge Generalized Position (2)

2.074 T2 FGP - Friction Ridge Generalized Position (3)

2.075 T2 ERS - Electronic Rap Sheet

2.079 T2 NCR - Number of Candidates Returned

2.080 T2 EXP - Response Explanation

2.082 T2 REC - Response Code

2.083 T2 ULF - Unsolved Biometric File

2.084 T2 AMP - Amputated or Bandaged

2.084 T2 AMP FGP - Finger Position

2.084 T2 AMP AMPCD - Amputated or Bandaged Code

2.086 T2 SCNA - Subject Control Number

2.087 T2 TAA - Treat as Adult

2.088 T2 NOT - Note Field

2.089 T2 MSC - Match Score

2.091 T2 RCD1 - Ridge Core Delta One for Subpattern Classification

2.091 T2 RCD1 FGP - Finger Position

2.091 T2 RCD1 RCN1 - Ridge Count Number 1

2.092 T2 RCD2 - Ridge Core Delta Two for Subpattern Classification

2.092 T2 RCD2 FGP - Finger Position

2.092 T2 RCD2 RCN2 - Ridge Count Number 2

2.095 T2 RFR - Request Features Record

2.096 T2 RPR - Request Photo Record

2.098 T2 NDR - Name of Designated Repository

2.098 T2 NDR - Name of Designated Repository (2)

2.124 T2 IPA CA - Image Pattern Annotation

2.124 T2 IPA CA FGN - Finger Number

2.124 T2 IPA CA IAC1 - Image Annotation Code 1

2.124 T2 IPA CA IAC2 - Image Annotation Code 2

2.475 T2 SSO W - WIN-Send Search To Other AFIS

2.476 T2 SRA W - WIN-Search Results Agency

2.477 T2 FRC W - WIN-FBI Retention Code

2.478 T2 QUA W - WIN-Quality Codes

2.478 T2 QUA W FGN - Finger Number

2.478 T2 QUA W NECQ - AFIS Quality Code

2.478 T2 QUA W MNC - AFIS Finger Minutia Count

2.478 T2 QUA W PPC - AFIS Primary Pattern

2.591 T2 IRQ W - Compressed Type 1 and 2

2.591 T2 IRQ W AORI - Agency ORI

2.591 T2 IRQ W GMT - GMT

2.591 T2 IRQ W TCN - TCN

2.591 T2 IRQ W B64 - Base64 Type 1 and 2 Records

2.593 T2 CFI W - WIN - Conversion Flag Indicator

2.594 T2 SID W - WIN - Originating JMS SID Resulting In No-Hit

2.595 T2 RSB W - WIN - FBI Resubmit TCN

2.602 T2 PALMCA - Palm Image Pattern Annotation

x CONTENTS

2.602 T2 PALMCA PLP - Finger Number

2.602 T2 PALMCA PANC - Image Annotation Code

2.603 T2 QUA2 W - NFIQ Quality

2.603 T2 QUA2 W FGN - Finger Number

2.603 T2 QUA2 W NQC - NFIQ Quality

2.604 T2 BPS W - Send directly to FBI Flag

2.752 T2 AOS WA - Arrest Offense Set (WA)

2.752 T2 AOS WA SEQ - Charge Sequence Number

2.752 T2 AOS WA DOO - Date Of Offense

2.752 T2 AOS WA OFC - Offense Code

2.752 T2 AOS WA OFL - Offense Literal

2.752 T2 AOS WA COM - Offense Comments

2.752 T2 AOS WA ATT - Attempt

2.752 T2 AOS WA SOL - Solicit

2.752 T2 AOS WA CSP - Conspire

2.752 T2 AOS WA CMP - Complicity

2.752 T2 AOS WA PRZ - Protected Zone

2.752 T2 AOS WA SXM - Sexual Motivation

2.752 T2 AOS WA FRM - Firearm

2.752 T2 AOS WA WPN - Weapon

2.752 T2 AOS WA DMV - Domestic Violence

2.752 T2 AOS WA DRG - Drug Related

2.752 T2 AOS WA DUI - DUI Related

2.752 T2 AOS WA ORA - Originating Agency

2.752 T2 AOS WA OIN - Other Identifying Number

2.752 T2 AOS WA DRA - Dispo Responsible Agency

2.752 T2 AOS WA WAR - Warrant Number

2.752 T2 AOS WA TAA - Treat As Adult

2.752 T2 AOS WA RCC - Report Court Case

2.752 T2 AOS WA DRP - Dispo Reporting Agency

2.752 T2 AOS WA DOD - Date Of Disposition

2.752 T2 AOS WA DST - Disposition Status

2.752 T2 AOS WA FTA - Failure To Appear

2.755 T2 APTP WA - Applicant Type (WA)

2.2007 T2 SDOB - Submitted Date of Birth

2.2008 T2 SNAM - Submitted Name

2.2010 T2 NIR - Number of Images Requested

2.2015 T2 RBXD - Rap Back Expiration Date

2.2018 T2 DNAC - DNA In CODIS Flag

2.2020 T2 RBR - Rap Back Recipient

2.2021 T2 IFS - Identification Firearms Sales

2.2023 T2 SII - Supplementary Identity Information

2.2028 T2 BID - Biometric Image Description

2.2028 T2 BID SI - Subject Identifier

2.2028 T2 BID IMT - Image Type

2.2028 T2 BID BSI - Biometric Set Identifier

2.2028 T2 BID FNR - Finger Number Requested

2.2028 T2 BID PPD - Print Position Descriptor

2.2028 T2 BID POS - Subject Pose

2.2028 T2 BID SMT - NCIC SMT Code

2.2029 T2 BSI - Biometric Set Identifier

2.2030 T2 PPD - Print Position Descriptor

2.2030 T2 PPD FGP - Friction Ridge Generalized Position

2.2030 T2 PPD FIC - Finger Image Code

2.2031 T2 BIA - Biometric Image Available

2.2032 T2 ATR - Audit Trail Record

2.2032 T2 ATR ORI - Originating Agency Identifier

CONTENTS xi

2.2032 T2 ATR DAT - Date of Dissemination

2.2032 T2 ATR TOT - TOT of Dissemination

2.2032 T2 ATR BSI - Biometric Set Identifier Disseminated

2.2032 T2 ATR IMT - Image Type Disseminated

2.2032 T2 ATR FNR - Finger Number Requested

2.2032 T2 ATR PPD - Print Position Description

2.2032 T2 ATR POS - Subject Pose

2.2032 T2 ATR SMT - NCIC SMT Code

2.2033 T2 CNL - Candidate Investigative List

2.2033 T2 CNL SI - Subject Identifier

2.2033 T2 CNL NAM - Master Name

2.2033 T2 CNL BSI - Biometric Set Identifier

2.2033 T2 CNL IMT - Image Type

2.2033 T2 CNL FGP - Friction Ridge Generalized Position

2.2033 T2 CNL PPD - Print Position Descriptor

2.2033 T2 CNL MSC - Match Score

2.2033 T2 CNL BIA - Biometric Image Available

2.2033 T2 CNL NDR - Name of Designated Repository

2.2033 T2 CNL IDC - Information Designation Character

2.2033 T2 CNL NOT - Note Field

2.2033 T2 CNL POS - Subject Pose

2.2033 T2 CNL SMT - NCIC SMT Code

2.2033 T2 CNL - Candidate Investigative List (2)

2.2033 T2 CNL SI - Subject Identifier (2)

2.2033 T2 CNL NAM - Master Name (2)

2.2033 T2 CNL BSI - Biometric Set Identifier (2)

2.2033 T2 CNL IMT - Image Type (2)

2.2033 T2 CNL FGP - Friction Ridge Generalized Position (2)

2.2033 T2 CNL PPD - Print Position Descriptor (2)

2.2033 T2 CNL MSC - Match Score (2)

2.2033 T2 CNL BIA - Biometric Image Available (2)

2.2033 T2 CNL NDR - Name of Designated Repository (2)

2.2033 T2 CNL IDC - Information Designation Character (2)

2.2033 T2 CNL NOT - Note Field (2)

2.2033 T2 CNL POS - Subject Pose (2)

2.2033 T2 CNL SMT - NCIC SMT Code (2)

2.2034 T2 ULR - Unsolved Latent Retained

2.2035 T2 EVI - Event Identifier

2.2036 T2 POS - Subject Pose

2.2037 T2 ESI - External Subject Identifier

2.2039 T2 RBMI - Rap Back Maintenance Indicator

2.2040 T2 RBT - Rap Back Trigger

2.2041 T2 RBNI - Rap Back Activity Notification Identifier

2.2041 T2 RBNI - Rap Back Activity Notification Identifier (2)

2.2047 T2 RAR - Return All Records Indicator

2.2048 T2 RBSI - Rap Back Subscription Identifier

2.2049 T2 RBTD - Rap Back Term Date

2.2050 T2 RBSL - Rap Back Subscription List

2.2052 T2 MAI - Maintenance Action Indicator

2.2052 T2 MAI - Maintenance Action Indicator (2)

2.2054 T2 RBSD - Rap Back Subscription Date

2.2055 T2 SMS - SMT Size

2.2055 T2 SMS HGT - Height

2.2055 T2 SMS WID - Width

2.2058 T2 SMD - SMT Descriptors

2.2058 T2 SMD SMI - SMT Code Indicator

2.2058 T2 SMD TAC - Tattoo Class

xii CONTENTS

2.2058 T2 SMD TSC - Tattoo Subclass

2.2058 T2 SMD TDS - Tattoo Description

2.2059 T2 TCL - Tattoo Color

2.2059 T2 TCL TC1 - Tattoo Color Code 1

2.2059 T2 TCL TC2 - Tattoo Color Code 2

2.2059 T2 TCL TC3 - Tattoo Color Code 3

2.2059 T2 TCL TC4 - Tattoo Color Code 4

2.2059 T2 TCL TC5 - Tattoo Color Code 5

2.2059 T2 TCL TC6 - Tattoo Color Code 6

2.2061 T2 BIE - Biometric Image Enrollment

2.2061 T2 BIE BSI - Biometric Set Identifier

2.2061 T2 BIE IMT - Image Type

2.2061 T2 BIE POS - Subject Pose

2.2061 T2 BIE SMT - Scars, Marks, and Tattoos

2.2061 T2 BIE - Biometric Image Enrollment (2)

2.2061 T2 BIE BSI - Biometric Set Identifier (2)

2.2061 T2 BIE IMT - Image Type (2)

2.2061 T2 BIE POS - Subject Pose (2)

2.2061 T2 BIE SMT - Scars, Marks, and Tattoos (2)

2.2062 T2 RBNF - Rap Back Activity Notification Format

2.2063 T2 RBOO - Rap Back Opt Out In-State Indicator

2.2064 T2 RBUD - Rap Back User Defined

2.2064 T2 RBUD RBFN - Rap Back Field Name

2.2064 T2 RBUD RBFT - Rap Back Field Text

2.2065 T2 RBC - Rap Back Category

2.2067 T2 RBDI - Rap Back Disclosure Indicator

2.2068 T2 DTR - Date Range

2.2069 T2 RBTED - Rap Back Triggered Event Details

2.2069 T2 RBTED DORBE - Date of Rap Back Event

2.2069 T2 RBTED RBT - Rap Back Trigger

2.2069 T2 RBTED RBEI - Rap Back Event Information

2.2070 T2 RBATN - Rap Back Attention Indicator

2.2071 T2 RBST - Rap Back Subscription Term

2.2073 T2 BIL - Biometric Image List

2.2073 T2 BIL SI - Subject Identifier

2.2073 T2 BIL BSI - Biometric Set Identifier

2.2073 T2 BIL BCD - Biometric Capture Date

2.2073 T2 BIL IMT - Image Type

12 Additional Rule Definitions 365

A OFC-WA.txt Codes 367

B OFL-WA.txt Codes 383

C CharacterEncodingSet 399

D CharacterEncodingSetName 401

E POB Table 403

F CTZ Table 421

G SMT Table 427

H CSL CDN Table 441

I FNR Table 443

CONTENTS xiii

J IMT Table 445

K FGP Table 447

L BIA Table 449

M SMD Table 451

N COL Table 453

O T4ImpressionType 455

P FrictionRidgePositionCodes 457

Q FSP codes 459

R PatternClassificationSubCodes 461

S EfsDeltaCodes 463

T TPD Codes 465

U EfsMethodsOfFeatureDetectionCodes 467

V Value Assessments 469

W Fraud Assessments 471

X Latent Substrates 473

Y Latent Matrices 475

Z Quality Issue Types 477

Comparison Determinations 479

FacePositionValues 481

SMTNCICcodes 483

Tattoos 497

Tattoo Colors 499

T13ImpressionType 501

FingerPositionCode 503

FingerPosition-1-10-16-17 505

JointSegmentTipCodeFIC 507

FVC Codes 509

FRMP Table 511

T14ImpressionType 513

T14 FGP Table 515

FingerPositionCode-T14-FGP 517

PPD DFP Table 519 xiv CONTENTS

PPD FIC Table 521

T15ImpressionType 523

FingerPositionCode-T15-FGP 525

FingerPosition-AMP-FRAP 527

T15 PQM FRMP Codes 529

Additional Rule Definitions 531

WIN Verification File Change History 533 .1 New To This Release

Chapter 1

Preface

This document defines requirements to which agencies must adhere when electronically communicating with WIN.

It defines all of the Types of Transactions (TOTs) allowed by WIN. The WIN TOTs are a subset of the FBI EBTS TOTs, but also include two Washington State Patrol specific TOTs (SOR and DOC) and WIN Internal Fingerprint Image Submission (WFIS) not defined in the FBI EBTS. Member state agencies making use of this standard, can elevate WIN optional fields to mandatory if this better meets their particular needs. Tracking these differences is the responsibility of the the state agencies.

The WIN EBTS Version 4.1.0 Reference Guide along with the WIN EBTS 4.1.0 Supplemental Guide completely covers record type descriptions for Type-4, Type-7, Type-8, Type-9, Type-10, Type-13, Type-14, Type-15, and Type-17 records. It is WIN’s intent that these definitions be consistent with the record definitions contained in the FBI EBTS Version 11.2 and ANSI/NIST ITL 1-2011 specifications.

WIN EBTS also complies with FBI EBTS Type-1 and Type-2 field requirements, however there are additional fields the WIN member agencies have opted to capture that contain WIN, state, and local level information. These additions use fields allocated to WIN by the FBI within the North American domain. This is illustrated in Chapter 6 Type-2 Field Allocations For FBI/WIN.

There are minor adjustments to some of the FBI EBTS defined fields that are needed as the submission is sent on to the FBI. These field modifications, when interfacing with another AFIS, are noted in the Field Rules Chapters, under the Notes section for each field. The FBI EAG administers these translations for the WIN member agency, which are defined in the WIN EBTS and the WIN CDRL.

The definitions for the WIN supported transaction types (TOTs) are defined in Section 4.6.2 WIN Fingerprint Image Submissions. Each WIN member state will need to further clarify from the WIN EBTS supported TOTs those transaction types that are supported by the member agencies CCH interface.

Document Overview

Document chapters that a new user may find useful.

⇒ Chapter 2 : Introduction This chapter explains why this document was created, gives a brief description of the specification, and the elements that are commonly used

⇒ Chapter 3 : Scope This chapter explains the scope of this document and its purpose.

⇒ Chapter 4 : Services and Transaction Types This chapter describes the User Services being offered by the Next Generation Identification (NGI).

⇒ Chapter 5 : WIN and FBI Transaction Response Times This chapter briefly presents priorities for each transaction type and response times for the transaction described in this document.

⇒ Chapter 6 : Type-2 Field Allocations For FBI/WIN This chapter outlines the Type-2 record field allocations for WIN and WIN members.

⇒ Chapter 10 : Transaction Field Requirements This chapter contains a summary of records and fields for each Type of Transaction (TOT).

⇒ Chapter 11 : Field Rules for Type 2 Records This chapter contains descriptions for all fields and includes example data, in the Type 2 record. The Type 2 record contains Transaction, Descriptive, Demographic, and Biographic information.

⇒ Chapter : WIN Verification File Change History This chapter lists all changes made to the WIN verification file and WIN reference guide.

2 CHAPTER 1. PREFACE

References for Record Type Layouts

For more detailed descriptions of the record types, refer to ANSI/NIST-ITL 1-2011 or EBTS Version 11.2 as indicated below.

⇒ CJIS Image Quality Specifications refer to the FBI EBTS Version 11.2 (September 20, 2023) Appendix F.

This contains information for fingerprint scanners, both for traditional rolled prints and Identification Flats, and printers, and gives Fast Track Certification procedures.

⇒ Error Messages refer to the FBI EBTS Version 11.2 (September 20, 2023) Appendix M.

⇒ Type 4 Record refer to the ANSI/NIST-ITL 1-2011 (September 2011) Section 8.4 Record Type-4: Grayscale fingerprint image.

⇒ Type 7 Record refer to the FBI EBTS Version 11.2 (September 20, 2023) Appendix H.

⇒ Type 8 Record refer to the ANSI/NIST-ITL 1-2011 (September 2011) Section 8.8 Record Type-8: Signature image record.

⇒ Type 9 Record refer to the FBI EBTS Version 11.2 (September 20, 2023) Appendix J.

⇒ Type 10 Record refer to the FBI EBTS Version 11.2 (September 20, 2023) Appendix K.

⇒ Type 13 Record refer to the ANSI/NIST-ITL 1-2011 (September 2011) Section 8.13 Record Type-13:

Friction-ridge latent image record.

⇒ Type 14 Record refer to the FBI EBTS Version 11.2 (September 20, 2023) Appendix N.

⇒ Type 15 Record refer to the ANSI/NIST-ITL 1-2011 (September 2011) Section 8.15 Record Type-15: Palm print image record.

Chapter 2

Introduction

2.1 Background

In support of the development of the FBI’s Next Generation IAFIS (NGI) and in accordance with the recommen-dations of the National Crime Information Center (NCIC) Advisory Policy Board (APB) ) (currently known as the CJIS APB) Identification Services Subcommittee, WIN has maintained compliance with the updates to FBI EBTS up through and including FBI EBTS 11.2.

The original version of WIN EFTS 3.1 (January 1999-WIN EFTS V3r3) has been grandfathered into the latest WIN upgrade and into this publication. This publication will be referred to as WIN EBTS Version 4.1.0. WIN EBTS has incorporated the following national standards documents, and is included as reference here in as defined to enhance the utility of the NIST/WIN-EBTS tenprint submissions:

1. WIN EBTS conforms with the American National Standards Institute (ANSI) standard entitled Data Format for the Interchange of Fingerprint, Facial, & Other Biometric Information (ANSI/NIST-ITL 1-2011).

2. WIN duplicates a subset of the FBI EBTS electronic transaction types, TOTS, based on EBTS Version 11.2 242-HQ-A6687913-SYSDOCU September 20, 2023.

3. The WIN EFTS V3.1 originated in 1998 and was based on the now defunct Joint Task Force Criminal History Interstate Transmission specification published Version 1.01 December 8, 1998. WIN EFTS has included the JTF field descriptions to provide the Criminal History Systems and Jail Management Systems the option to use these fields for data interchange. WIN EFTS version 3.1 adjusted some JTF fields to meet the 6/98 and 12/98 version specifications since the original was based on a draft version. WIN EFTS Version 3.2 made minor data corrections and added 5 new field elements.

4. The Washington State Patrol (WSP) EFTS V5pt2 dated March 28, 2006 was merged into WIN existing field descriptions and required that field numbers 2.750-2.782 be appended to the WIN EBTS. The WSP TOTs, SOR (Sex Registrant) and DOC (Department of Corrections), were added to the WIN specification. Notes included in the field description denote where field descriptions differ from the baseline WIN specification.

5. The WIN Internal Fingerprint Image Submission is based on the WIN EBTS FIS transaction. The WFIS TOT was added to the WIN specification in September of 2011. This was added to allow updating of WIN ABIS records.

2.2 File Format

An EBTS transaction is comprised of records. EBTS defines the composition of records within a transaction that is transmitted between the FBI’s Next Generation Identification System (NGI) and another site or agency. All records in a transaction shall pertain to a single subject; data used to identify another individual requires a separate transaction.

All of the records belonging to a single transaction shall be transmitted together. There may be multiple records in a transaction of each Record Type other than Type-1. Record Type-1 and Type-2 are used to describe the transaction and the subject respectively, and are required. These may be accompanied by one or more data records containing biometric data. The maximum number of records in a transaction is restricted to 1000.

In order to ensure that the transaction description information can be read by all systems, all fields within a Type-1 Record shall always be encoded using 7-bit American National Standard Code for Information Interchange (ASCII), with the 8th (leftmost) bit of each byte containing a zero. This is consistent with the specification of UTF-8 for XML encodings, since ASCII is a subset of UTF-8.

For other Record Types, the default character encoding for Traditional encoding is 7-bit ASCII. Users are encouraged to use UTF-8 for “U” and “user-defined” character types that do not require special control characters in Traditional Encoding. It is not possible to switch encodings within an XML transaction. For more information on ASCII characters, see Appendix C.

The first field in a traditional record (2.001 LEN) shall contain the length in bytes of the record. The second field shall contain the version number in the Type-1 record, while in other records this field contains the information designation character (2.002 IDC). In Traditional Record Types conveying binary data (Type-10 through Type-99) the data field will always be the last field in the record. The remaining traditionally encoded ASCII fields may occur in any order.

4 CHAPTER 2. INTRODUCTION

For Type-4 and Type-7 binary image records, the content and order of the recorded fields are specified by this standard. All fields and data in these Record Types shall be recorded as binary information in Traditional encoding.

The domain (1.013 DOM) field shall be mandatory for transactions to/from FBI/CJIS in support of proper file validation and field usage, as well as file interoperability among disparate systems.

2.3 Change Control

The WIN-EBTS defines the interface between WIN, IAFIS, and the States’ systems. Any changes to the data fields or formats within the EBTS must honor previously published protocols to ensure that the States’ systems are not adversely affected. Since WIN, IAFIS, and the States’ systems are being developed independently, a process has been established which provides for coordinated enhancements within the various systems while maintaining reliable interoperability. This convention is based on the tagged field structure defined in the ANSI/NIST-ITL standard and the understanding that field definitions cannot change over time or from system to system.

To facilitate system evolution, each system is assigned an autonomous range of field numbers that it is allowed to define to meet operational needs. These new fields cannot be made mandatory for established functionality, but enhance functionality for those systems wishing to incorporate the new definition. With this process in place, every system on the network has the opportunity to enhance its own system on its own schedule, yet no system is ever forced to make a change in order to maintain current functionality.

2.4 Error Handling

Error handling takes on two primary forms within WIN or CJIS. These are front-end error detection and internal process error detection and correction. The front-end process examines every incoming transaction from a security and mandatory data perspective. Potential security violations are rejected and transferred immediately to a system administrator. Transactions lacking mandatory data, or that are incomplete in referenced content, are rejected back to the contributor. All mandatory data and all optional data fields are checked for length and type of data included.

Optional data failing this validation check are ignored. Mandatory data that fail this validation check are passed to a Quality Check (QC) Service Provider for resolution. If the Service Provider can correct the data, the transaction will be forwarded for further processing. If the Service Provider cannot resolve the issue, the transaction can either be rejected or sent forward for attempted resolution later in the process.

Internal process error detections and corrections are performed any time a WIN or IAFIS attempts to utilize incoming data to perform a search or update a database. Any such action will check the field according to length and type as well as content. Some data values are content sensitive. That is, they can only be examined with respect to the databases against which they are to be applied. Errors in submissions detected at that time will generally be forwarded to a Logic Error Resolution Service Provider. At that point, appropriate actions can be taken to correct the discrepancy and an internal resubmission of the transaction can take place. Alternatively, if the Service Provider cannot resolve the issue, the transaction can be rejected.

In the interpretation of the logical record, tags that are not defined for the requested transaction are to be ignored;

their inclusion is not to be considered an “error” and certainly not a “fatal error”. This rule makes it possible to use a single transmission format, for example, to control both intrastate and interstate transmissions. When the submitting agency is not a member of a WIN agency based on an ORI table lookup, the only mandatory Type 2 fields will be LEN and IDC.

Fields should not be transmitted when there is no value present (e.g.,.. 2.033:<gs>). However, receipt of such an empty field, if the field is not mandatory, should not result in rejection of the record or issuance of an error message.

Rejection will occur, however, when missing or incorrect data would frustrate processing of the transaction. The following list illustrates these types of errors:

1. A mandatory field is missing in a submitted record set (e.g., NAM field 2.018, is missing in the Type-2 record for the TOT of a CAR) and would result in immediate rejection.

2. The format of a mandatory field is incorrect (e.g., an alpha character is discovered in the SOC field) and would result in an attempt to correct the data.

3. The range of data of a mandatory field is incorrect (e.g., a DOB of 18871332 was submitted - century, month, and day are all out of range) and would result in an attempt to correct the data.

4. Incorrect data is discovered that cannot be corrected by a service provider, and without which, the transaction processing cannot proceed will result in the transaction being rejected.

FBI EBTS Version 11.2 Appendix M lists the current set of Error Messages that are pertinent to the EBTS user (i.e., CJIS internal errors are not listed).

2.5. IDENTIFYING PREVIOUS TRANSACTIONS 5

2.5 Identifying Previous Transactions

The fields Transaction Control Number (1.009 TCN) and Transaction Control Reference (1.010 TCR) are used to link requests with their corresponding responses. Every transaction must contain a unique TCN. Transactions that refer to previous submissions also contain a TCR, which is defined as the TCN of the referenced submission.

When FBI/CJIS receives a request transaction and generates the response, it places the TCN of the request into the TCR field of the response as a reference number the submitter can use to mate the response with the original submission. FBI/CJIS places its own identifier for the response transaction in the TCN field.

The TCN in the response can be used by the submitter should the transaction need to be reopened for any purpose.

For example, if FBI/CJIS rejected the first submission of a user-fee transaction due to poor quality fingerprint images, the user would place this number in the TCR field of the resubmitted transaction to enable FBI/CJIS to verify the user’s authorization to resubmit within one year at no charge.

2.6 Data Storage in WIN/FBI/CJIS Database

Transaction data submitted to WIN/FBI/CJIS may or may not be stored in the WIN/FBI/CJIS database. Data not stored is considered to be user-defined. If submitted, user-defined data is returned in the response transaction as an aid to the submitter in interpreting and routing the WIN/FBI/CJIS response. It may differ in format from the originally submitted data. The following user-defined fields, which are not stored at WIN/FBI/CJIS, are always returned as submitted: ATN, SCO, EAD, OCP, RES, and TAA.

2.7 Guidance on ORI and CRI Usage

The following description offers some guidance for the use of theControlling Agency Identifier (CRI) field to provide appropriate authorization to perform file maintenance. This scenario is developed examining how an electronic submission might be formed by a contributor and passed to WIN/FBI/CJIS. This is intended as an example since there are many other requirements that might influence the final design. Ultimately, the contributors manage the use of the CRI field.

Example: Assume a print is obtained by a local agency, passed to a county agency for processing, and subsequently to the WIN/FBI/CJIS Systems Agency (CSA) for transmission to the WIN/FBI/CJIS. In such a case the trans-mission of field 1.008 Originating Agency Identifier (ORI) and field 2.073 Controlling Agency Identifier (CRI) might appear as show in Figure 2.1 Example ORI and CRI Ownership Flow on page 6.

When generated at the local level, no CRI is required since this ORI is the originator. On receipt by the county agency and subsequent transmission to the state CSA, the original ORI is entered as the first instance of the CRI and the county ORI replaces the local ORI in the ORI field. On receipt by the state CSA and for subsequent retransmission to FBI/CJIS, the local ORI is retained as CRI2, the county ORI is entered as CRI1, and the ORI of the state CSA is entered in the ORI field. The transaction is then forwarded to FBI/CJIS via FBI/CJIS WAN. CRI1, the county agency ORI, is then used as the authority for action and thus retains ‘ownership’ of the transaction. In the response, the transaction is sent to the ORI from which it was sent, and it is the responsibility of the state CSA to route it properly to the county agency identified in CRI1. The county agency, in turn, would route the response to the local agency as appropriate.

C H A P T E R

2.

IN

T R O D U C T

IO

N

Figure 2.1: Example ORI and CRI Ownership Flow

W

IN

E B T S V ersion

.1 .0

R eferen ce G u id e

Chapter 3

Scope

This document specifies in detail the file and record content, format, and data codes necessary for the exchange of fingerprint, palmprint, photo, facial, and iris information between state and local users and the WIN including forwarding to FBI. It provides a description of all requests and responses associated with the electronic fingerprint identification service and other services. This specification is organized into User Services which include the following:

1. Identification Service

2. Verification Service

3. Information Service

4. Investigation Service

5. Notification Service

6. Data Management Service

3.1 Identification Service

This service will provide user support of biometric identification. It provides searches that result in the positive identification or non-identification of the individual based on a one-to-many biometric search. In this version of the WIN EBTS, only fingerprints will be used for this purpose, although other biometrics may be submitted in the same transactions (i.e., photo, palmprint, iris, supplemental fingerprint and palmprint). In future versions of the WIN EBTS, multiple biometrics may be used for identification purposes.

The Identification Service will consist of the original Tenprint service that is accessed through the electronic tenprint submission for the purpose of searching the WIN IAFIS and FBI CJIS repository. Electronic submissions may involve processing and evaluation judgments by WIN personnel. Searches are performed by automated equipment without human intervention by WIN personnel. The results of the search may require WIN personnel to evaluate search results and provide their judgment. Tenprint submissions that update current fingerprint images will be handled under the Data Management Services.

The Latent submissions that fall under the Identification Service are comprised of the electronic latent fingerprint identification submission handled by WIN latent examiners along with cascaded searches of the Unsolved Latent Fingerprint (ULF) and the Special Population Cognizant (SPC) File for a positive identification. The remaining Latent Investigative submissions fall under the Investigation Service.

This service provides users with the ability to make electronic tenprint submissions based on legacy Washington State Patrol (WSP) transactions.

3.2 Verification Service

This service will provide user support of biometric verification. It addresses the method that results in the confir-mation of an individual’s identity based on a one-to-one comparison. In this version of the EBTS, only fingerprints will be used for this purpose, although other biometric identifiers (i.e., photo, palm, iris, supplemental fingerprint and palmprint) may be used in the future.

3.3 Information Service

This service will provide user support of requests for specific biographic or biometric information on an individual.

It allows a user to submit a request for information on an individual by specifying a unique identifier. An image request can be used to solicit fingerprints and other types of images stored by WIN. All transactions and messages will be compliant with the ANSI/NIST-ITL standard for exchange of fingerprints, palmprints, facial photos along with scars, marks, and tattoo photos.

3.4 Investigation Service

This service will provide user support of investigative searches. The Investigation Service provides a list of candidates based on a one-to-many biometric and/or biographic search. The result set may include an ordered listing of candidates and corresponding information to facilitate the investigative decision process.

3.5 Notification Service

This service will provide event notification to users about their data contained within any of the FBI IAFIS/NGI repositories [e.g., Criminal and Civil Files, Special Population Cognizant (SPC) Files, Unsolved Latent File (ULF)].

8 CHAPTER 3. SCOPE

With this service, a data owner will receive an unsolicited notification from the system based on event criteria (triggers).

3.6 Data Management Service

This service provides users with the ability to manage data within IAFIS. It allows the user to add, delete, and modify data contained in IAFIS that is under the contributor’s control.

This service provides users with the ability to manage fingerprint images within WIN ABIS. It allows users to update fingerpint images if better quality or the images include different characteristics than the existing ones. WIN will determine whether to update the master fingerprint images.

Chapter 4

Services and Transaction Types

This section describes the User Services offered by WIN and the EBTS Transactions that comprise them. WIN offers the following User Services: Identification Service, Verification Service, Information Service, Investigation Service, Notification Service, and Data Management Service. WIN will process the following types of transactions for the service areas listed below:

� Identification Service

– Tenprint Fingerprint Identification Transactions

– Rapid Fingerprint Identification Search Transactions

– Disposition Fingerprint Transactions

– Iris Identification Search Transactions

– Washington State Patrol Transactions

� Verification Service

– Verification Transactions

� Information Service

– Biometric Image Retrieval Transactions

– Criminal Subject Photo Images Transactions

– Biometric Audit Trail Retrieval Transactions

– Rap Back Information Retrieval Transactions

� Investigation Service

– Tenprint Fingerprint Investigation Transactions

– Latent Friction Ridge Investigation Transactions

– Photo Investigation Transactions

� Notification Service

– Notification Transactions

� Data Management Service

– Data Management Transactions

– WIN Intenal Finerprint Image Transactions

4.1 Identification Service

These transactions will originate from live scan booking terminals, FBI Field Offices, card scanners or mobile devices at either the federal, state, or local level. Refer to Figure 4.1 Electronic Fingerprint Identification Submission on page 10.

Local submissions may be processed by a local ABIS/AFIS and electronically transmitted to a State Identification Bureau (SIB) for processing. If a positive identification is made at the state level, an Ident response will be transmitted back to the local agency. If it is a criterion offense, it will also be forwarded to FBI/CJIS. What constitutes a criterion offense is determined according to the submitting state’s retention policy and legislation.

The processing flow for a civil electronic fingerprint identification submission is similar to the criminal submission flow, except that in the event of state-level Ident response, the submission may still be forwarded to FBI/CJIS for processing under Federal and/or state statutory authority.

If no identification is made at the SIB level, the data will be forwarded via the CJIS WAN to FBI/CJIS for processing. Transmitted data will be automatically parsed, and a search will be conducted of the FBI/CJIS’s friction ridge files. An identification of the submitted fingerprint images may be verified by an FBI/CJIS fingerprint examiner. Electronic responses 1 from FBI/CJIS to the contributor will be routed via the CJIS WAN through the SIB using the ORI. Subsequent routing to the arresting agency is made by the SIB using the CRI. Additional copies are routed by the SIB using the SCO field or other related information (see Appendices B and C for detailed ORI, SCO, and CRI definitions).

1Established procedures for sending unsolicited messages to State Identification Bureaus in response to fingerprint cards from Interstate Identification Index (III) participating states will not be affected.

H A P T E R

4.

S E R V

IC

E S A N D

T R A N S A C T

IO

N T Y P E S

Figure 4.1: Electronic Fingerprint Identification Submission

W

IN

E B T S V ersion

.1 .0

R eferen ce G u

4.1. IDENTIFICATION SERVICE 11

4.1.1 Tenprint Fingerprint Identification Submissions

The Tenprint Fingerprint Identification submissions consists of electronic criminal and civil transactions. The response time goals for these transactions are specified in Chapter 5 WIN and FBI Transaction Response Times.

In addition to the fingerprint images, the submitter may optionally include palm print, joint/tip print, iris, face, and/or SMT images of the subject. If the contributor subsequently wishes to add other biometric images to a tenprint search and retain event, they may reference the Event Identifiers (2.2035 EVI) returned in the tenprint response (SRE) described within the Biometric Enrollment Transactions section. The information within a retained submission will be added to an existing record, if a positive identification is made, or will create a new record if no identification was made. If a nonretain submission is not identified, no information will be retained in the FBI/CJIS databases. If a positive identification is made for a non-retain submission, the information on that submission may be added to the existing record and dissemination rules will govern the dissemination of this information.

Many of the tenprint identification submissions may be used to simultaneously establish a Rap Back subscription.

Inclusion of the Rap Back subscription fields for a TOT in table D-1 signifies that the TOT may establish a Rap Back subscription. Many of the tenprint identification submissions may be used to simultaneously establish a link between an external system identity and an FBI/CJIS identity. The presence of an External Subject Identifier (2.2037 ESI) will establish a link between the provided ESI and the FBI Number/UCN, if the search results in an identification. Coordination between the external system owner and FBI/CJIS must occur before attempting to utilize the external system record linking capability.

Cascaded searches of marked Special Population Cognizant (SPC) files may be launched along with simultaneous searches of other external systems, such as Canada’s Real-Time ID System or DHS IDENT. These will be indicated by the appropriate values for the desired destination in the Name of Designated Repository (2.098 NDR) field in the Type-2 record.

The fingerprint images on these submissions will be used to search against the criminal repository. Besides the fingerprint images, the submitter may optionally include palmprint images along with a set of up to 4 photos of the subject.

The processes of the tenprint search request are further described in the WIN Technical System Design Document

- Figure 4.2 ”WIN Transaction Flow Overview” on page 22.

There are several types of electronic fingerprint identification submissions that will be accepted by WIN and FBI/CJIS. The particular type of submission is identified in the Type of Transaction (TOT) field in the Type- 1 record for each transaction. The following are the TOTs for identification submissions:

Table 4.1: Tenprint Fingerprint Identification Submissions

TOT TRANSACTION

CAR Criminal Tenprint Submission (Answer Required) CNA Criminal Tenprint Submission (No Answer Necessary) CPDR Criminal Fingerprint Direct Route CPNU Criminal Fingerprint Processing Non-Urgent DOCE Departmental Order Channeling Electronic EMUF Electronic In/Manual Out User Fee Submission FANC Federal Applicant (No Charge) FAUF Federal Applicant User Fee FIDR Foreign Information Direct Route NNDR Non-Federal No Charge Direct Route NFUE Non-Federal User Fee Expedite NFUF Non-Federal Applicant User Fee MAP Miscellaneous Applicant Civil DEK Known Deceased DEU Unknown Deceased MPR Missing Person AMN Amnesia Victim

WIN and FBI/CJIS responses to electronic submissions will provide search results or indicate an error via the following TOTs:

Error responses are described in Section 4.7 Error Message Format.

12 CHAPTER 4. SERVICES AND TRANSACTION TYPES

Table 4.2: Tenprint Fingerprint Identification Responses

TOT RESPONSE TRANSACTION

SRE Submission Results - Electronic ERRT Ten-Print Transaction Error

Criminal Tenprint Submission (Answer Required) (CAR)

This transaction is a criminal arrest fingerprint submission for which the requester desires an identification decision response. It contains ten rolled and four plain impressions of all ten fingers, biographic descriptor data, as well as information relative to an arrest and court disposition data. The biographical data and fingerprint images are used to determine potential candidates with criminal records at WIN and/or FBI/CJIS and a positive identification or non-identification decision is determined. A response is returned to the contributor. The response will always contain the positive identification/non-identification decision and may contain the electronic Identity History Summary, if requested.

This TOT is also used for an inquiry on a criminal suspect or informant, in which case arrest, custody, or supervisory data may or may not be present (Retention Code set to “N”).