Department of Defense Electronic Biometric Transmission … · 2011-05-14 · Electronic Biometric...

Department of Defense

Electronic Biometric Transmission Specification

8 November 2006

Version 1.2 DIN: DOD_BTF_TS_EBTS_ Nov06_01.02.00

Report Documentation Page Form ApprovedOMB No. 0704-0188

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.

1. REPORT DATE 08 NOV 2006 2. REPORT TYPE

3. DATES COVERED 00-00-2006 to 00-00-2006

4. TITLE AND SUBTITLE Department of Defense Electronic Biometric Transmission Specification.Version 1.2

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Department of Defense,Biometric ,347 West Main Street,Clarksburg,WV,26301

8. PERFORMING ORGANIZATIONREPORT NUMBER

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

11. SPONSOR/MONITOR’S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited

13. SUPPLEMENTARY NOTES

14. ABSTRACT

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as

Report (SAR)

18. NUMBEROF PAGES

78

19a. NAME OFRESPONSIBLE PERSON

a. REPORT unclassified

b. ABSTRACT unclassified

c. THIS PAGE unclassified

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

Electronic Biometric Transmission Specification DIN: DOD_BTF_TS_EBTS_ Nov06_01.02.00

i

Revision History Revision Date Document Status Participants/Comments 1.0 19 August 2005 Release Initial release of the EBTS Specification

1.1 23 August 2005 Updated Release Section 1.5 updated to reflect BMO role in the change control of this document

1.1.1 17 July 2006 Interim Revision Updated per Change Request 0001 through 0021 (see Change Requests table below)

1.1.2 08 August 2006 Interim Revision Updated per commenter’s review; includes editorial changes

1.2 08 November 2006 Updated Release Added list of Change Requests, readied for release

Change Requests CR ID Change Request (CR) Description CR-0001 Resolve limited length of the Name Field in EFTS

CR-0002 Consolidate multiple fields for Latitude and Longitude

CR-0003 Incorrect EBTS Domain Name in Section 5.1.1 and incorrect version number in Section 2.4

CR-0004 MIO improperly expanded to Maritime Interdiction Operations in Section 5.2.10 and Appendix A

CR-0005 Add ability to record a missing iris in Type-2 records

CR-0007 Adjust Internment Serial Number

CR-0008 Add short name (mnemonic) to description of each field in Section 5, second paragraph

CR-0010 Add Type-13 for latent prints of 1000 ppi and above

CR-0011 Improve description of image requirements for face, Section 3.2

CR-0012 Section 5.3 says Type-14 is described in EFTS - It is not in EFTS 7.0.

CR-0013 Remove all references to Red, Blue, and Gray forces (Section 2.2)

CR-0016 Remove reference to ANSI/NIST-ITL 1-2000 for Type 16 descriptions

CR-0017 Addition of 15 fields to meet CENTCOM requirements

CR-0018 Proposed Encounter Protection EBTS Elements

CR-0019 Proposed Subsequent Notification EBTS Elements

CR-0020 Proposed Transaction Lookup EBTS Elements

CR-0021 Proposed Watchlist EBTS Elements


ii

TABLE OF CONTENTS 1.0 INTRODUCTION .............................................................................................................. 1

1.1 Background ..................................................................................................................... 1 1.2 Scope and Purpose .......................................................................................................... 1 1.3 Current DoD ABIS Capability and EBTS Support......................................................... 2 1.4 References....................................................................................................................... 2 1.5 Change Control ............................................................................................................... 2 1.6 Contact Information ........................................................................................................ 2

2.0 DoD ABIS OPERATIONS................................................................................................. 3

2.1 Fingerprint Storage ......................................................................................................... 3 2.2 Categories of Submissions.............................................................................................. 3 2.3 User Provisioning Process .............................................................................................. 4 2.4 EBTS Domain Name ...................................................................................................... 4

3.0 EBTS TRANSACTIONS ................................................................................................... 6

3.1 Comparison with EFTS Transactions ............................................................................. 7 3.2 Mug Shot Support ........................................................................................................... 8 3.3 Interim Iris Support......................................................................................................... 9 3.4 Transaction Record Requirements.................................................................................. 9 3.5 Transaction Control Numbers....................................................................................... 10 3.6 Origination Identifiers................................................................................................... 12 3.7 Interpretation of Tags and Error Handling.................................................................... 12 3.8 Image Quality Requirements ........................................................................................ 12

4.0 EBTS TRANSACTION DETAIL .................................................................................... 15

4.1 CAR – Criminal 10-print Submission (Answer Required)........................................... 16 4.2 MAP – Miscellaneous Applicant .................................................................................. 17 4.3 FANC – Federal Applicant No Charge......................................................................... 18 4.4 DEK – Known Deceased & DEU – Unknown Deceased............................................. 19 4.5 TPRS – 10-print Rap Sheet Search............................................................................... 20 4.6 DPRS – DoD Flat Print Rap Sheet Search.................................................................... 21 4.7 LFIS – Latent Fingerprint Image Search & LFFS – Latent Fingerprint Feature Search 22 4.8 VER – Verification Electronic Submission .................................................................. 23 4.9 IRQ – Fingerprint Image Request................................................................................. 24 4.10 CPR – Subject Photo Request....................................................................................... 25

5.0 EBTS RECORDS AND FIELDS ..................................................................................... 26

5.1 Type-1 Records............................................................................................................. 26 5.2 Type-2 Records............................................................................................................. 28 5.3 Type-4 Records............................................................................................................. 58 5.4 Type-7 Records............................................................................................................. 58 5.5 Type-9 Records............................................................................................................. 58 5.6 Type-10 Records........................................................................................................... 58 5.7 Type-13 Records........................................................................................................... 58


iii

5.8 Type-14 Records........................................................................................................... 58 5.9 Type-16 Records........................................................................................................... 59

APPENDIX A: ACRONYM LIST.............................................................................................. 71

APPENDIX B: ACCOMMODATING LONG NAMES ............................................................. 73

LIST OF FIGURES Figure 1: Categories of Fingerprint Data ....................................................................................... 3 Figure 2: Transaction Submission and Response Sequence ........................................................ 11 Figure 3: TCN Field Layout ........................................................................................................ 12

LIST OF TABLES Table 1: EBTS Types of Transactions (TOT) (Submissions and Responses) by Category .......... 6 Table 2: Comparison of EBTS and EFTS TOTs ........................................................................... 7 Table 3: Transaction Record Requirements................................................................................... 9 Table 4: Image Quality Requirements ......................................................................................... 13 Table 5: Transaction List ............................................................................................................. 15 Table 6: CAR Transaction ........................................................................................................... 16 Table 7: MAP Transaction........................................................................................................... 17 Table 8: FANC Transaction......................................................................................................... 18 Table 9: DEK and DEU Transactions.......................................................................................... 19 Table 10: TPRS Transaction........................................................................................................ 20 Table 11: DPRS Transaction ....................................................................................................... 21 Table 12: LFIS and LFFS Transaction ........................................................................................ 22 Table 13: VER Transaction ......................................................................................................... 23 Table 14: IRQ Transaction........................................................................................................... 24 Table 15: CPR Transaction.......................................................................................................... 25


Page 1 of 74

1.0 INTRODUCTION This DoD Electronic Biometric Transmission Specification (EBTS) describes customizations of the Federal Bureau of Investigation (FBI) Electronic Fingerprint Transmission Specification (EFTS) transactions that are necessary to utilize the Department of Defense (DoD) Automated Biometric Identification System (ABIS).

1.1 Background

The DoD ABIS is an electronic database and associated set of software applications that support the storage, retrieval, and searching of fingerprint data collected from persons of national security interest. Over time, the DoD ABIS will support the storage, retrieval, and searching of additional biometric modalities such as face images, iris images, and voice samples. The software architecture of the DoD ABIS has been designed to be compliant with the FBI Criminal Justice Information Services (CJIS) EFTS Version (v) 7. The DoD ABIS implements the transaction types and codes described in the EFTS, thus ensuring operational compatibility with the FBI system. Because of the different nature of DoD encounters and detainment circumstances, the DoD ABIS has additional requirements for transaction types and codes beyond those defined in the EFTS. The DoD-unique transaction types and codes are defined in this, the EBTS.

1.2 Scope and Purpose

The primary audience for this specification consists of software engineers who develop and/or support systems that interface with the DoD ABIS. Readers are expected to have working knowledge of the EFTS and American National Standards Institute/National Institute of Standards and Technology ANSI/NIST-ITL 1-2000 as a prerequisite for understanding this specification. This v1.2 of the EBTS addresses the transactional functionality required for interfacing with the DoD ABIS. Future revisions may address the following additional functionality areas:

• New transactions for iris image submissions and responses • New transactions for face image submissions and responses • New transactions for voice sample submissions and responses • Support for the submittal, storage, and searching of Common Biometric Exchange Formats

Framework (CBEFF) header information along with images or other sample data representing various biometric modalities (e.g., face images, iris images, voice samples)

• Support for ANSI/International Committee for Information Technology Standards (INCITS) standards-based biometric data interchange formats

• Support for XML encoding and/or Web services Many of these issues will be addressed in the ongoing revisions to the ANSI/NIST-ITL 1-2000 standard. DoD ABIS technical specifications, such as this one, shall be updated to be compatible with the revisions to ANSI/NIST-ITL 1-2000 when those revisions become available.


Page 2 of 74

1.3 Current DoD ABIS Capability and EBTS Support

As of time of this publication, some transactions described in this specification are not yet fully supported by the DoD ABIS. For details of currently supported transactions, please contact the DoD BTF Help Desk for more information by e-mail at [email protected].

1.4 References

ANSI/NIST-ITL 1-2000, “Data Format for the Interchange of Fingerprint, Facial, & Scar Mark & Tattoo (SMT) Information” (ANSI/NIST-ITL 1-2000/NIST Special Publication 500 245). It is available for download at ftp://sequoyah.nist.gov/pub/nist_internal_reports/sp500-245-a16.pdf. FBI CJIS EFTS v7 was published in January 1999 (CJIS RS 0010(V7)). This specification is available for download at http://www.fbi.gov/hq/cjisd/iafis/efts_70.pdf.

1.5 Change Control

The BTF maintains change control responsibilities for this document. Requested changes to this document should be submitted to the DoD Biometrics Web site (see contact information in Section 1.6).

1.6 Contact Information

DoD Biometrics Web site: http://www.biometrics.dod.mil. For technical issues, contact the DoD BTF Help Desk at (304) 326-3023, Monday through Friday, 0800-1700 EST or by e-mail at [email protected].


Page 3 of 74

2.0 DoD ABIS OPERATIONS This section provides an overview of DoD ABIS operations and contains information for users who wish to begin using DoD ABIS services and who may have unique requirements.

2.1 Fingerprint Storage

The DoD ABIS accommodates 10-print rolled fingerprint data, flat fingerprint data ranging between one and 10 flat prints, and latent fingerprint images. The categories of supported fingerprint data are shown in Figure 1.

Figure 1: Categories of Fingerprint Data

2.2 Categories of Submissions

DoD ABIS submissions are divided into four categories. Each category represents a separate use case for the DoD ABIS. The four categories are:

• identification of detainees, enemy combatants, enemy prisoners of war (EPW), or persons of interest (known or suspected terrorists).

• biometric screening at a check point or for third country nationals who want to work on a U.S.

military base.

• identification of U.S. military and contractors working for the DoD.

• forensic investigation latent fingerprints. Each category of search is distinguishable based on the type of transaction. The DoD ABIS supports transaction types defined in the EFTS as well as DoD-specific transaction types. The details of transaction types supported by the DoD ABIS are outlined in Section 3, EBTS Transactions.

10-print Rolled Fingerprints

1-10 Flat Fingerprints

Latent Fingerprints


Page 4 of 74

2.3 User Provisioning Process

The BTF is responsible for maintaining the data integrity of the DoD ABIS. Therefore, the BTF has approval authority for all systems interfacing with the DoD ABIS and coordinates the requests of all new users who desire access to DoD ABIS. The term “user” applies to any DoD entity that wishes to make use of the storage, retrieval, and searching capabilities of the DoD ABIS. The overall goal of the DoD ABIS user provisioning process is to ensure that DoD ABIS data are accurate and timely and that DoD ABIS services are available when required. DoD entities may contact the DoD BTF Help Desk (see Section 1.6) concerning the provisioning process. The new user provisioning process will be documented in a BTF Standard Operating Procedure (SOP). The user provisioning process is complete when the DoD entity is granted a formal “permission to operate” with the DoD ABIS. The SOP will identify the significant steps a new user must take before being granted a “permission to operate.” A non-exhaustive list of these steps includes:

• Completion of a DoD ABIS User Agreement • Designing a system using equipment that complies with DoD ABIS interface, data format,

information security, and image quality requirements • Coordinating with the BTF in the assignment of user- and equipment-specific parameters such as

originating agency identifier (ORI), e-mail addresses, and transaction privileges • Submitting the proposed system that will interface with the DoD ABIS to the BTF for a

certification of compliance and supporting the certification process as required • Generating and transmitting test transactions to the DoD ABIS

The goal of the BTF certification process is to assess how well a system conforms to relevant standards and operating requirements. Please contact the BTF Help Desk (see Section 1.6) for further assistance with the certification process.

2.4 EBTS Domain Name

The BTF is the domain registrar for the EBTS implementation domain. ANSI/NIST-ITL 1-2000 defines an implementation domain as “a group of agencies or organizations that have agreed to use specific pre-assigned groups of numbered tag fields for exchanging information unique to their installations.” The EBTS Type-1 domain name field (field 1.013) consists of two information items (subfields). The first, DOM_IMP, uniquely identifies the EBTS implementation with the character string “EBTS.” The second item, DOM_VER, identifies the EBTS version, which is currently 1.2. For example, standard EBTS transactions should have the following domain field values:

DOMAIN IMPLEMENTATION DOMAIN VERIFICATION EBTS 1.2

This coding specifies that the information within the files contains data that are fully compliant with the specifications of EBTS v1.2.


Page 5 of 74

A DoD entity may determine that its unique needs require more information than is defined by the EBTS. In such instances, the DoD entity may request a new domain to customize EBTS fields, types, and/or transactions. To obtain a new domain name, the entity must request a new domain from the BTF domain registrar. Please contact the BTF Help Desk (see Section 1.6) for more information. Once approved, the domain registrar shall assign the entity a unique character string for use in the DOM_IMP field and a version number for the DOM_VER field. The BTF shall maintain the complete documentation for all requests and the unique fields assigned for each domain. For example, a domain implementation may resemble the following:

DOMAIN IMPLEMENTATION DOMAIN VERIFICATION EBTS_NAVY 1.0

This new domain may have domain-specific fields such as the following:

Field #: 2.0001123 T2_PORT_OF_CALL Field #: 2.0001124 T2_TYPE_OF_VESSEL

Note that ANSI/NIST-ITL 1-2000 uses implementation domains to define common sets of Type-2 tags. This document allows an implementation domain to define a common usage of fields, types, and transactions. The DoD BTF recognizes that some applications will collect and utilize information outside of this EBTS specification. The use of a registered domain name will allow these data to be utilized in multiple applications. Instead, this additional information can be included as “user-defined fields” in existing transactions. Additional user-defined Type-2 data fields containing only American Standard Code for Information Interchange (ASCII) data are ignored and not processed by the DoD ABIS.


Page 6 of 74

3.0 EBTS TRANSACTIONS EBTS transactions are a superset of the transactions of the EFTS. The EBTS preserves the structure of the EFTS records so that EBTS submissions can be forwarded to the FBI, but it adds additional transactions and fields to collect DoD-specific data that may be recorded in the DoD ABIS. The full set of EBTS transactions is shown in Table 1.

Table 1: EBTS Types of Transactions (TOT) (Submissions and Responses) by Category

EBTS TOT

EBTS Transaction Name DoD Implementation Notes

Electronic 10-print Submissions

CAR Criminal 10-print Submission (Answer Required)

Submission used for detainee or EPW.

FANC Federal Applicant No Charge Submission used as part of a background check for enlisting U.S. military, DoD civilians, and DoD contractors.

MAP Miscellaneous Applicant Submission used as part of a background check for local nationals and third country nationals who require access to U.S. military installations or other restricted areas.

DEK Known Deceased Submission used for deceased subject whose identity is known.

DEU Unknown Deceased Submission used for deceased subject whose identity is not known.

SRE Submission Results - Electronic Response containing an Ident/Non-Ident decision; will contain an electronic rap sheet if requested.

ERRT 10-print Transaction Error Error response.

Remote 10-print Searches

TPRS 10-print Rap Sheet Search Performs a search only, non-retain, and can return an unconfirmed-identification (“yellow”) identification.

DPRS DoD Flat Print Rap Sheet Search This is only used in special circumstances.

SRT Search Result – 10-print Response including a candidate list comprising names and DoD number of each candidate.

ERRT 10-print Transaction Error Error response.

Remote Latent Print Searches

LFIS Latent Fingerprint Image Search Used for latent image submission and searches.

LFFS Latent Fingerprint Feature Search

Used for latent feature submission and searches.


Page 7 of 74

EBTS TOT

EBTS Transaction Name DoD Implementation Notes

LRE Latent Result Latent Response containing an Ident/Non-Ident decision.

ERRL Latent Transaction Error Error response.

Remote Requests for Fingerprint Images

IRQ Fingerprint Image Request Request for identification information (flat prints, mug shots, demographic/biographic information).

IRR Fingerprint Image Request Response

Response containing requested identification information (flat prints, mug shots, demographic/biographic information).

ISR Image Response Summary Response indicating that the prints were not on file with DoD ABIS.

ERRI Image Transaction Error Error response.

Electronic Criminal Subject Photo Searches

CPR Subject Photo Request Request for mug shot photos on file with DoD ABIS.

PRR Photo Response Response containing requested identification mug shot photos.

Verification

VER Verification Electronic Submission

Used for 1:1 verification based on an identifier.

VRSP Verification Response - Electronic

A verification response that contains Ident/Non-Ident information.

EVER Verification Error Response Error response. Additional transaction types will be added in subsequent versions of this specification to support additional biometric modalities, as noted in Section 1.4, Change Control.

3.1 Comparison with EFTS Transactions

Many of the EFTS transactions are used directly by EBTS, some are not used at all, and some are modified to carry additional DoD-specific fields. EBTS also defines new submission and response transaction types. The EBTS transactions described in detail in this specification are compared to the EFTS transactions in Table 2:

Table 2: Comparison of EBTS and EFTS TOTs

EBTS TOT Description

Related EFTS TOT

EBTS Differences from EFTS


Page 8 of 74

EBTS TOT Description

Related EFTS TOT

EBTS Differences from EFTS

Electronic 10-print Submissions

CAR Criminal 10-print Submission (Answer Required) CAR

Options for two iris images, 1,000-ppi fingerprints, and an additional mug shot

FANC Federal Applicant No Charge FANC Options for two iris images, 1,000-ppi fingerprints, and five mug shots

MAP Miscellaneous Applicant MAP Options for two iris images, 1,000-ppi fingerprints, and five mug shots

DEK Known Deceased DEK Options for two iris images, 1,000-ppi fingerprints, and one additional mug shot

DEU Unknown Deceased DEU Options for two iris images, 1,000-ppi fingerprints, and one additional mug shot

Remote 10-print Searches

TPRS 10-print Rap Sheet Search TPIS 10-print Fingerprint Image Searches - None

DPRS DoD Flat Print Rap Sheet Search TPIS

Additional Type-2 logical record fields are required. Options for two iris images, 1,000-ppi fingerprints, five mug shots, four additional 500-ppi flat prints, and up to 10 fingerprint minutiae. This is used only in special circumstances.

Remote Latent Print Searches

LFIS Latent Fingerprint Image Search LFIS

None

LFFS Latent Fingerprint Feature Search LFFS

None

Remote Requests for Fingerprint Images

IRQ Fingerprint Image Request IRQ None

Electronic Criminal Subject Photo Searches

CPR Subject Photo Request CPR None

Verification Electronic Submissions


None New Transaction

3.2 Mug Shot Support

The CAR, DEK, DEU, MAP, FANC, and DPRS transactions support mug shot submission. Up to five Type-10 records are permitted in these submissions. Facial images should be taken in accordance with the Federal Information Processing Standard (FIPS) 201 Personal Identity Verification (PIV) format (i.e. INCITS 385-2004).


Page 9 of 74

3.3 Interim Iris Support

Interim support for the submission of iris image data is achieved by permitting iris images to be stored in Type-16 records. This interim support will be required until ANSI/NIST-ITL 1-2000 and/or the EFTS provide support for iris images. The CAR, DEK, DEU, MAP, FANC, and DPRS transactions support iris image submission. Up to six Type-16 records are permitted in these submissions.

3.4 Transaction Record Requirements

Each EBTS transaction has requirements for including a certain number of records of each type. Table 3 defines record requirements for the transaction types in EBTS. Notations for the table are as follows:

• A single asterisk (*) indicates that less than 14 images are acceptable for this transaction only in the case of amputation, deformity, or bandage. If less than 14 images are present due to the reasons listed above, this shall be indicated in the Type-2 record as defined in the EFTS. Type-4 data will only contain fingerprint images at 500 ppi with 15:1 Wavelet Scalar Quantization (WSQ) compression as defined in the EFTS.

• Double asterisks (**) indicate that this field shall contain iris images. Currently, DoD

Biometrics will accept iris images in any image format in Type-16 records for CAR, DEK, DEU, MAP, FANC, and DPRS transactions. DoD Biometrics anticipates changes to the underlying ANSI/NIST-ITL 1-2000 standard that will guide the next iteration of this specification to a standardized definition and record location for iris data transmission. Iris images are optional.

• Triple asterisks (***) indicate that this field shall contain 1,000-ppi fingerprint images if

available. Currently, DoD Biometrics will accept 1,000-ppi fingerprint images for CAR, DEK, DEU, MAP, FANC, and DPRS transactions. 1,000-ppi fingerprint images are optional.

Table 3: Transaction Record Requirements

TOT Type-1 Type-2 Type-4 Type-7 Type-9 Type-10 Type-13 Type-14 Type-16

CAR 1 1 0 to 14* - - 0 to 5 - 0-14*** 0-6**

DEK 1 1 0 to 14* - - 0 to 5 - 0-14*** 0-6**

DEU 1 1 0 to 14* - - 0 to 5 - 0-14*** 0-6**

MAP 1 1 0 to 14* - - 0 to 5 - 0-14*** 0-6**

FANC 1 1 0 to 14* - - 0 to 5 - 0-14*** 0-6**

VER 1 1 1 to 14 - - - - - -

LFFS 1 1 to 2 0 to 10 0 to 10 1 to 10† - 0 to 10 0 to 10 -

LFIS 1 1 to 2 0 to 10 0 to 10 - - 0 to 10 0 to 10 -

TPRS 1 1 2 to 10 - 0 to 10 - - - -

DPRS 1 1 0 to 14 - 0 to 14 0 to 5 - 0-14*** 0-6**

SRE 1 1 - - - - - - -


Page 10 of 74

VRSP 1 1 - - - 0 to 1 - - -

EVER 1 1 - - - - - - -

SRT 1 1 0 to 14 - - - - -

ERRT 1 1 - - - - - - -

LRE 1 1 - - - - - - -

ERRL 1 1 1 to n - - - - - -

IRQ 1 1 - - - - - - -

CPR 1 1 - - - - - - -

PRR 1 1 - - - 1 to 5 - - -

IRR 1 1 1 to 4 - - 0 to 1 - - -

ISR 1 1

ERRI 1 1 - - - - - - -

† For each finger submitted as minutiae (Type-9), the corresponding image must be submitted as a Type-4, a Type-7 a Type-13, or a Type-14 record.

3.5 Transaction Control Numbers

A transaction identification number is assigned to a submission and carried through on the response for tracing purposes. A Transaction Control Number (TCN) is a unique identifier generated by the system that submits the transaction. A Transaction Control Reference (TCR) number is part of the DoD ABIS/IAFIS reply and includes the TCN so the originating submission request can be identified. When a transaction is sent to the DoD ABIS, the TCR in the response(s) will contain the TCN used in the submission. A TCN is mandatory for a submission, and a TCR is mandatory for a response. These values are contained in the Type-1 record in an EFTS or EBTS transaction. Information on TCN and TCR is contained in Section 1.6, Identifying Previous Transactions of the EFTS document. Figure 2 illustrates the TCN and TCR in the transaction flow.


Page 11 of 74

��

��

��

�� !� ��"�#�� $%%�&

��

'�(��)��*��

'��(��

'��(��'��+��

��

,-�� !� ��! �.��/ ��%�� #.0�1

��'�

�� !� ��"�#�� $%%�&

Figure 2: Transaction Submission and Response Sequence

The EFTS requires that a TCN must be a 10- to 40-byte string that consists of letters, numbers, and special characters. The EBTS requires a 40-byte identifier that contains:

• the ORI • a Greenwich Mean (a.k.a. Zulu or UTC) date/time stamp • a code for the software used at the point of collection/transmission • an indicator of the software version used at the point of collection/transmission • a random or sequential alphanumeric string

A hyphen separates each of these fields. Figure 3 illustrates the makeup of the TCN.


Page 12 of 74

Figure 3: TCN Field Layout

The BTF will assign a software code to a product as part of the DoD ABIS certification process outlined in Section 2.3, User Provisioning Process of this document. Software developers must contact the BTF Help Desk (see Section 1.6) to obtain a four-letter software code. This code must be used consistently in the software product. Software users must not generate a TCN; rather the software must do this automatically based on a predetermined configuration. A TCN must be unique. A TCN must not be reused. Matching a TCN to a TCR is the method used to match EBTS responses to EBTS submissions.

3.6 Origination Identifiers

The mandatory origination field shall contain the ORI identifying the agency or organization submitting the transaction. For EBTS purposes, this field shall be a nine-byte alphanumeric field. The BTF assigns an ORI code to DoD entities that submit directly to DoD ABIS. Those DoD entities must contact the BTF Help Desk (see Section 1.6) to obtain an ORI.

3.7 Interpretation of Tags and Error Handling

The DoD ABIS will observe the processing rules for tag interpretation and error handling as described in Section 2.4, Tagged Fields, and Section 1.5, Error Handling of the EFTS document. Additional guidance may be added to this EBTS document as necessary to support the operation of the DoD ABIS.

3.8 Image Quality Requirements

In the interest of maintaining an accurate and usable database of biometric data, minimum image quality requirements must be followed for images submitted in EBTS transactions.

3.8.1 Finger Image Quality

Finger image quality requirements are defined in Appendix F of the EFTS. From an image quality perspective only, any system certified for use with IAFIS meets EBTS image quality requirements. Rolled impressions shall be rolled from one side of the fingernail to the other. The collection of rolled finger


Page 13 of 74

samples shall include the following images: o 10 separately rolled fingers o Combined plain impression of the four fingers on the right hand (no thumb) o Combined plain impression of the four fingers on the left hand (no thumb) o Left thumb plain impression o Right thumb plain impression

Collection of flat finger samples shall include the same images, except that the 10 fingers will be captured with each finger laid flat. All images shall be captured at a resolution of either 500 or 1,000 pixels per inch (ppi). Flat fingerprints are allowed only in specific types of transactions. Table 4 outlines which transactions require rolled fingerprints and which transactions are allowed to include flat fingerprints.

Table 4: Image Quality Requirements

TOT Fingerprint Requirements

CAR 10 prints rolled (14 images)

MAP 10 prints rolled or flat (14 images)

DEK 10 prints rolled (14 images)

DEU 10 prints rolled (14 images)

FANC 10 prints rolled (14 images)

TPRS 1-10 prints flat

DPRS 1-10 prints flat

LFIS Any

LFFS Any

VER 1-10 prints flat

Legend:

TOT – Type of Transaction

CAR – Criminal 10-print Submission

MAP – Miscellaneous Applicant

FANC – Federal Applicant No Charge

TPRS – 10-print Rap Sheet Search

DEK – Known Deceased

DEU – Unknown Deceased

DPRS – DoD Flat Print Rap Sheet Search

LFIS – Latent Fingerprint Image Search

LFFS – Latent Fingerprint Feature Search


Page 14 of 74

VER – Verification Electronic Submission

3.8.2 Face Image Quality

All photographs shall be taken using color cameras. The camera lens orientation shall be pointed to the front of the person, aligned approximately in the center of the face, and taken from a distance of approximately five feet. The orientation(s) of the person for facial photos shall be taken from the following options:

o Frontal view (also known as full-frontal pose). o 90 degrees left side. o 45 degrees left side. o 90 degrees right side. o 45 degrees right side.

When photographed, the person shall not be allowed to wear any glasses, sunglasses, headgear, headdress, or other items obscuring the area photographed (the “area photographed” is only the area from the “nose to the ears” and not the entire head -- the person may expose the area from ear to ear and hairline to chin without removing the headdress). There are no constraints on cosmetics. The full frontal pose shall conform to the requirements of ANSI INCITS 385-2004, “Face Recognition Format for Data Interchange”, clauses 8.2, 8.3, and 8.4 (The Full Frontal Image Type).

3.8.3 Iris Image Quality

All iris image capture equipment shall collect separate images of the left and right irises of each person. Note: this does not imply that two images must be collected. The requirement is that, if both the left and right eye are captured, the process must result in two images. Images should be captured in accordance with Annex A, Iris Image Capture Best Practice, of ANSI INCITS 379-2004, the Iris Image Interchange Format.


Page 15 of 74

4.0 EBTS TRANSACTION DETAIL The DoD ABIS will process the transactions listed in Table 5. Those transactions are described in detail in this section.

Table 5: Transaction List

TOT Transaction CAR Criminal 10-print Submission (Answer Required)

MAP Miscellaneous Applicant

FANC Federal Applicant No Charge

DEK Known Deceased

DEU Unknown Deceased

TPRS 10-print Rap Sheet Search

DPRS DoD Flat Print Rap Sheet Search

LFIS Latent Fingerprint Image Search

LFFS Latent Fingerprint Features Search

VER Electronic Verification Submission

IRQ Fingerprint Image Request

CPR Subject Photo Request


Page 16 of 74

4.1 CAR – Criminal 10-print Submission (Answer Required)

The Criminal 10-print Submission Answer Required (CAR) transaction type shall be used for detainees or EPW. DoD Biometrics policy requires 10-print rolled fingerprints for subjects in a detained situation. The demographic data required in the EFTS CAR transaction are also required for submission to the DoD ABIS. This DoD implementation of the CAR transaction contains additional optional DoD-specific data fields. The DoD CAR transaction type is a superset of the EFTS CAR transaction type. The two valid responses to a CAR submission are Submission Results – Electronic (SRE) or 10-print Transaction Error (ERRT). An SRE will be returned with the search results (Identification/Non-identification) if no errors exist in the submission. An ERRT transaction will be returned with details of the specific error should a syntax error and/or image quality problem exist. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). CAR transactions types are listed in Table 6.

Table 6: CAR Transaction

TOT Submission Transaction CAR Criminal 10-print Submission (Answer Required)

TOT Response Transactions

SRE Submission Results – Electronic

ERRT 10-print Transaction Error


Page 17 of 74

4.2 MAP – Miscellaneous Applicant

The MAP transaction type shall be used as part of a background check for local nationals and third country nationals who desire access to U.S. military installations or other restricted areas. DoD Biometrics policy requires 10-print rolled or flat fingerprints (14 images including slaps) for these subjects. Rolled prints are always preferred and should be collected whenever possible. Demographic data required in the EFTS MAP transaction are also required for submission to the DoD ABIS. This DoD implementation of the MAP transaction contains additional optional DoD-specific data fields and biometric information such as mug shots. The DoD EBTS MAP transaction type is a superset of the EFTS MAP transaction type. Valid responses to this submission are Submission Results – Electronic (SRE) or 10-print Transaction Error (ERRT). An SRE will be returned with the search results (Identification/Non-identification) provided that no errors exist in the submission. If a syntax error is present or there is a problem with image quality, an ERRT transaction will be returned with details of the specific error. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). MAP transaction types are listed in Table 7.

Table 7: MAP Transaction

TOT Submission Transaction MAP Miscellaneous Applicant





Page 18 of 74

4.3 FANC – Federal Applicant No Charge

The FANC transaction type may be used as part of a background check for enlisting U.S. military, DoD civilians, and DoD contractors. DoD Biometrics policy requires 10-print rolled or flat fingerprints (14 images including slaps) for these subjects. Rolled prints are always preferred and should be collected whenever possible. Demographic data required in the EFTS FANC transaction are also required for submission to the DoD ABIS. This DoD implementation of the FANC transaction contains additional optional DoD-specific data fields and biometric information such as mug shots. The DoD EBTS FANC transaction type is a superset of the EFTS FANC transaction type. Valid responses to this submission are Submission Results – Electronic (SRE) or 10-print Transaction Error (ERRT). An SRE will be returned with the search results (Identification/Non-identification) provided that no errors exist in the submission. If a syntax error is present or there is a problem with image quality, an ERRT transaction will be returned with details of the specific error. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). FANC transaction types are listed in Table 8.

Table 8: FANC Transaction

TOT Submission Transaction FANC Federal Applicant No Charge





Page 19 of 74

4.4 DEK – Known Deceased & DEU – Unknown Deceased

The DEK transaction type is used for a deceased subject whose identity is known. The DEU transaction type is used for a deceased subject whose identity is not known. DoD Biometrics policy requires 10-print rolled fingerprints for these types of submissions. The DEK and DEU transaction types are defined in the EFTS. Demographic data required in the EFTS DEK and DEU transactions are also required for submission to the DoD ABIS. This DoD implementation of the DEK and DEU transaction types contains additional optional DoD-specific data fields and biometric information such as mug shots. Valid responses to this submission are Submission Results – Electronic (SRE) or 10-print Transaction Error (ERRT). An SRE will be returned with the search results (Identification/Non/identification) provided that no errors exist in the submission. If a syntax error is present or there is a problem with image quality, an ERRT transaction will be returned with details of the specific error. Detailed field requirements of these transaction types can be requested from the BTF Help Desk (see Section 1.6). DEK and DEU transaction types are listed in Table 9.

Table 9: DEK and DEU Transactions

TOT Submission Transaction DEK Known Deceased






Page 20 of 74

4.5 TPRS – 10-print Rap Sheet Search

The TPRS transaction type may be used as part of a quick background check by the U.S military. Uses include highly mobile applications, check points, and situations with a very limited time on target. Demographic information is permitted but not required in this transaction type. This transaction is for flat fingerprints only. One to 10 flat prints are required. This transaction is always search only (non-retain). TPRS is the only transaction type that can return an undetermined identification (“yellow”) to the originator. TPRS requires no demographic or biographic information to be collected from the subject. The TPRS transaction type has the same field requirements as TPIS defined in the EFTS. Remote 10-print responses are the expected result from a remote 10-print search. An SRT will be returned with the search results provided that no errors exist in the submission. If a syntax error is present or there is a problem with image quality, an ERRT transaction will be returned with details of the specific error. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). TPRS transaction types are listed in Table 10.

Table 10: TPRS Transaction

TOT Submission Transaction TPRS Flat-Print Rap Sheet Search


SRT Search Result – 10-print



Page 21 of 74

4.6 DPRS – DoD Flat Print Rap Sheet Search

The DPRS transaction type shall only be used in certain circumstances. These circumstances include legacy data submission and situations where acquiring full rolled fingerprints is not feasible. Highly mobile or limited time on target situations may warrant the use of this transaction type. DPRS data submission requires special coordination with DoD Biometrics. Submissions of this type may require special processing. In all situations, DoD Biometrics policy is to collect as much data as possible. DoD entities must contact the BTF for specific guidance on the use of this transaction type. The DPRS transaction will accept flat or rolled fingerprints. One to 14 fingerprint images are required. Mug shot images may be included in this transaction as a Type-10 record. Iris images may be included in this transaction as a Type-16 record. Type-2 optional and mandatory data types are similar to those of the MAP transaction. The DPRS transaction type is a superset of the TPRS transaction type. Remote 10-print responses are the expected result from a remote 10-print search. An SRT will be returned with the search results provided that no errors exist in the submission. If a syntax error is present or there is a problem with image quality, an ERRT transaction will be returned with details of the specific error. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). DPRS transaction types are listed in Table 11.

Table 11: DPRS Transaction

TOT Submission Transaction DPRS DoD Flat Print Rap Sheet Search





Page 22 of 74

4.7 LFIS – Latent Fingerprint Image Search & LFFS – Latent Fingerprint Feature Search

LFIS and LFFS transaction types shall be used for latent submissions and searches. Information regarding the latent print is required. DoD Biometrics requires the following supporting information to be included with all latent submissions:

• Circumstances for latent collection • Item from which print was lifted • Any unique item descriptor (i.e. serial number, make, model, etc) • Contact info

The previous four information items will be required to be present in the “Notes” field of latent transactions submitted to the DoD ABIS. All feature searches (LFFS) are required to contain fingerprint images as well as feature data. Additionally, DoD Biometrics requires the name of the latent technician (i.e., the lifter or processor) and the name of the submitter (i.e., the AFIS operator). Remote Latent Fingerprint Responses are the expected result from a remote latent print search. An LRE will be returned with the search files provided that no errors exist in the submission. A candidate list is not returned. The response will contain an identification or non-identification. If a syntax error is present or there is a problem with image quality, an ERRL transaction will be returned with details of the specific error. Detailed field requirements of these transaction types can be requested from the BTF Help Desk (see Section 1.6). LFIS and LFFS transaction types are listed in Table 12.

Table 12: LFIS and LFFS Transaction

TOT Submission Transaction LFIS Latent Fingerprint Image Search



LRE Latent Result Electronic

ERRL Latent Transaction Error


Page 23 of 74

4.8 VER – Verification Electronic Submission

The VER transaction type may be used to verify an identity. This submission will not perform a search, but rather perform only a lookup of the biometric. The submission must include a unique identifier that must be on file with the verification system in order to perform the lookup. Valid identifiers may be a Social Security Number, Electronic Data Interchange Personal Identifier (EDIPI), Internment Serial Number (ISN), Biometrics Automated Toolset (BAT) Global Unique Identifier, Defense Biometric Identification System (DBIDS) ID, or DoD Number, depending upon the system. Uses include check points and physical and logical access applications. The DoD ABIS is not intended to support day-to-day verification; this capability is designed to support other local access control applications. For example, this transaction may be used upon initial enrollment of a local access control system to verify a given identity against DoD records. Demographic information is permitted but not required in this transaction type. This transaction is for flat prints only. One to 10 flat prints are required. Electronic verification results are the expected response from an electronic verification submission. A VRSP will be returned with the search results provided that no errors exist in the submission. If a syntax error is present or there is a problem with image quality, an EVER transaction will be returned with details of the specific error. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). VER transaction types are listed in Table 13.

Table 13: VER Transaction

TOT Submission Transaction VER Verification Electronic Submission


VRSP Verification Response – Electronic

EVER Verification Error Response


Page 24 of 74

4.9 IRQ – Fingerprint Image Request

The IRQ transaction enables the retrieval of fingerprint images from the DoD ABIS. These images can be used to load a local biometrics identity verification system (i.e., a base access control system). The requester identifies the DoD Number(s) of the subject(s) whose prints are being requested. Fingerprint image files for up to 1,000 subjects may be requested per transaction. Each DoD Number in a request will be addressed in a separate Image Request Response (IRR) or Image Error Response (ERRI). Errors associated with individual DoD Numbers, such as an image set not being on file, will be reported in the Fingerprint Image Response Summary (ISR). Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). IRQ transaction types are listed in Table 14.

Table 14: IRQ Transaction

TOT Submission Transaction IRQ Fingerprint Image Request



ISR Image Response Summary

ERRI Image Transaction Error


Page 25 of 74

4.10 CPR – Subject Photo Request

The CPR transaction enables the retrieval of a photo set from the DoD ABIS. Each set of photos is comprised of one to five photos of a subject from different views. Each photo set is identified by the DoD Number and date of encounter (represented by the EFTS DOA field). If a date of encounter is not specified in the request, the photo set with the latest date of encounter will be sent. A Photo Response (PRR) will be sent back to the requester. Detailed field requirements of this transaction type can be requested from the BTF Help Desk (see Section 1.6). CPR transaction types are listed in Table 15.

Table 15: CPR Transaction

TOT Submission Transaction CPR Subject Photo Request


PRR Photo Response


Page 26 of 74

5.0 EBTS RECORDS AND FIELDS To support DoD-specific requirements, additional data fields beyond those contained in the EFTS have been added to the EBTS. These new and modified data fields are outlined in the following sections. All other data are defined in the EFTS. For each new EBTS field, the following sections list the field number, short name, and a descriptive name in the section title. For example, a section titled Field 2.311 Name-One (NAM1) is interpreted as follows:

• Field Number: 2.311 • Descriptive Name: Name-One • Short Name: NAM1

Each section also provides:

• A description of the field • A table detailing the construction of the field, including

o Subfield o Item o Acceptable input to the field. Abbreviations used are as follows:

� A—alphabetic � B1—binary � N—numeric � S—special characters

o Length of field • Identification of which special characters are valid (if any) • A list of transactions indicating whether the field is mandatory ([M]), optional ([O]), or

conditional ([C]).

5.1 Type-1 Records

EBTS uses EFTS Type-1 records to carry a transaction record. EBTS identifies one additional field for Type-1 records. This field is defined in ANSI/NIST-ITL 1-2000, but is not used in the EFTS.

5.1.1 Field 1.013 Domain Name (DOMAIN)

This mandatory field identifies the domain name for the user-defined Type-2 logical record implementation. The domain name may appear only once within a transaction. The domain must be registered with the BTF and shall consist of two information items. The first information item will uniquely identify the agency, entity, or implementation used for formatting the tagged fields in the Type-2 record. A second information item will contain the unique version of the particular implementation. The default value for the field shall be the EBTS implementation and shall appear as 1.013:EBTS{US}1.2{GS}. The BTF is the domain registrar for domain names used in EBTS transactions.


Page 27 of 74

Subfields 1 to 1

Item all

Character Type ANS

Characters 2 to 20

Special Characters: Any 7-bit non-control characters

Used in Transactions: CAR[M], DEK[M], DEU[M], FANC[M], MAP[M], VRSP[O], EVER[O], ERRT[O], SRE[O], TPRS[M], DPRS[M], SRT[O], LFIS[O], LFFS[O], SRL[O], ERRL[O], IRQ[M]

5.1.1.1 Subfield 1.013_1 Domain Name Implementation (DOMAIN_NAME)

Subfield all

Item 1

Character Type ANS

Characters 1 to 15



5.1.1.2 Subfield 1.013_2 Domain Name Implementation Version (DOMAIN_VER)

Subfield all

Item 2

Character Type ANS

Characters 1 to 5




Page 28 of 74

5.2 Type-2 Records

EBTS uses EFTS Type-2 records to carry descriptive text. EBTS defines the following new Type-2 fields to meet DoD requirements.

5.2.1 Field 2.300 BAT Global Unique Identifier (GUID)

This optional field shall contain the Biometrics Automated Toolset (BAT) Global Unique Identifier (GUID) as assigned by the BAT.

Subfields 1 to 10

Item 1

Character Type ANS

Characters 36 to 38


Used in Transactions: CAR[O], FANC[O], MAP[O], DPRS[O], VER[O], VRSP[O], SRE[O], SRT[O], SRL[O]

5.2.2 Field 2.301 Location (BLO)

This optional field shall contain the location of biometric collection.

Subfield 1

Item 1

Character Type ANS

Characters 1 to 255


Used in Transactions: CAR[O], FANC[O], MAP[O], SRE[O], DPRS[O], SRT[O], SRL[O]

5.2.3 Field 2.302 Internment Serial Number (ISN)

This field shall contain the ISN as defined by the AR190-8. This field is mandatory for CAR (i.e., EPW, detainee) transactions.

Subfield 1

Item 1


Page 29 of 74

Character Type ANS

Characters 13 to 16


Used in Transactions: CAR[M], DPRS[O], VER[O], VRSP[O], SRE[O], SRT[O], SRL[O]

5.2.4 Field 2.303 DoD Number (DOD_NO)

This optional field contains the subject’s DoD Number. A valid DoD Number shall be no more than nine alphanumeric characters. No special characters allowed.

Subfields 1 to 5

Item 1

Character Type AN

Characters 1 to 9

Used in Transactions: CAR[O], DEK[O], FANC[O], MAP[O], VRSP[O], EVER[O], ERRT[O], SRE[O], DPRS[O], SRT[O], SRL[O]

5.2.5 Field 2.304 Passport Information (PAS)

This optional field contains the subject’s passport information. All five subfields must be completed if this field is used.

Subfields 1 to 5

Item all

Character Type ANS

Characters 20 to 178


Used in Transactions: CAR[O], DEK[O], FANC[O], MAP[O], SRE[O], TPRS[O], DPRS[O]

5.2.5.1 Subfield 2.304_1 Passport Date Issued (PAS_DATEISSUE)

This field contains the date the subject’s passport was issued. The format for this field is YYYYMMDD.


Page 30 of 74

Subfield all

Item 1

Character Type N

Characters 8

Other Tags:

date YYYYMMDD

Used in Transactions: CAR[M], DEK[M], FANC[M], MAP[M], SRE[M], TPRS[M], DPRS[M]

5.2.5.2 Subfield 2.304_2 Passport Date Expires (PAS_DATEEXP)

This field contains the date the subject’s passport expires. The format for this field is YYYYMMDD.

Subfield all

Item 2

Character Type N

Characters 8

Other Tags:

date YYYYMMDD


5.2.5.3 Subfield 2.304_3 Passport Number (PAS_NUMBER)

This field contains the subject’s passport number.

Subfield all

Item 3

Character Type ANS

Characters 1 to 80


Page 31 of 74



5.2.5.4 Subfield 2.304_4 Country of Passport Issuance (PAS_COUNTRY)

This field contains the name of the country from which the subject’s passport was issued. Entry must be a valid country code as noted in the EFTS.

Subfield all

Item 4

Character Type A

Characters 2

Possible Codes (Mandatory):

The country code will consist of a valid two-letter National Crime Information Center (NCIC) country code.


5.2.5.5 Subfield 2.304_5 Location of Passport Issuance (PAS_LOC)

This field contains the name of the location of passport issuance.

Subfield all

Item 5

Character Type ANS

Characters 1 to 80



5.2.6 Field 2.306 Geographic Coordinate Latitude/Longitude (GEO_CORD)

This optional field contains the longitude and latitude at which the submission was collected. The subfields of this field are: Latitude Degree, Latitude Minute, Latitude Second, Longitude Degree,


Page 32 of 74

Longitude Minute, and Longitude Second. Both Latitude Degree and Longitude Degree are mandatory if this field is present. Decimal values are allowed in each subfield. If a decimal value is used in a particular subfield, the more granular subfields shall be empty (e.g., if Longitude Minutes equals 45.67, Longitude Seconds shall be empty. The datum for this field is indicated in Field 2.307 Geographic Coordinate Datum ID.

Subfield 1

Item 1

Character Type NS

Characters 6 to 51

Special Characters: period, plus, hyphen

Used in Transactions: CAR[O], DEK[O], FANC[O], MAP[O], VER[O], TPRS[O], DPRS[O]

5.2.6.1 Subfield 2.306_1 Latitude Degree (GEO_CORD_LAT_DEG)

This field contains the latitude at which the submission was collected. The data is in degrees in the range +90 to -90. The plus sign may be omitted. Decimal values are allowed.

Subfield all

Item 1

Character Type NS

Characters 1 to 9


Used in Transactions: CAR[M], DEK[M], FANC[M], MAP[M], VER[M], TPRS[M], DPRS[M]

5.2.6.2 Subfield 2.306_2 Latitude Minute (GEO_CORD_LAT_MIN)

This field contains the latitude at which the submission was collected. The data is in minutes in the range 0-60. Decimal values are allowed.

Subfield all

Item 2

Character Type NS


Page 33 of 74

Characters 1 to 8

Special Characters: period


5.2.6.3 Subfield 2.306_3 Latitude Second (GEO_CORD_LAT_SEC)

This field contains the latitude at which the submission was collected. The data is in seconds in the range 0-60. Decimal values are allowed.

Subfield all

Item 3

Character Type NS

Characters 1 to 8



5.2.6.4 Subfield 2.306_4 Longitude Degree (GEO_CORD_LONG_DEG)

This field contains the longitude at which the submission was collected. The data is in the range of +180 to -180. The plus sign may be omitted. Decimal values are allowed.

Subfield all

Item 4

Character Type NS

Characters 1 to 10



5.2.6.5 Subfield 2.306_5 Longitude Minute (GEO_CORD_LONG_MIN)

This field contains the longitude at which the submission was collected. The data is in minutes in the range 0-60. Decimal values are allowed.


Page 34 of 74

Subfield all

Item 5

Character Type NS

Characters 1 to 8



5.2.6.6 Subfield 2.306_6 Longitude Second (GEO_CORD_LONG_SEC)

This field contains the longitude at which the submission was collected. The data is in seconds in the range 0-60. Decimal values are allowed.

Subfield all

Item 6

Character Type NS

Characters 1 to 8



5.2.7 Field 2.307 Geographic Coordinate Datum ID (DATUM_ID)

This optional field contains an identifier for the datum used to express the coordinates provided in field 2.306, 2.321, or 2.322. If this field is absent, and one of those other fields are populated, the default datum is WGS-84 / NAD-83.

Subfield 1

Item 1

Character Type AN

Characters 3 to 6



Page 35 of 74

Datum ID Value Definition AIRY Airy AUST Australian National BES Bessel 1841 BESN Bessel 1841 (Nambia) CLK66 Clarke 1866 CLK80 Clarke 1880 EVER Everest FIS60 Fischer 1960 (Mercury) FIS68 Fischer 1968 GRS67 GRS 1967 GRS80 GRS 1980 HELM Helmert 1906 HOUG Hough INT International KRAS Krassovsky AIRYM Modified Airy EVERM Modified Everest FIS60M Modified Fischer 1960 SA69 South American 1969 WGS60 WGS-60 WGS66 WGS-66 WGS72 WGS-72 WGS84 WGS-84 / NAD-83


5.2.8 Field 2.308 Electronic Data Interchange Personal Identifier (EDI)

This optional field shall contain the EDIPI unique identifier for a person in the DMDC Person Data Repository.

Subfield 1

Item 1

Character Type N

Characters 10 to 20

Used in Transactions: CAR[O], DEK[O], FANC[O], MAP[O], VRSP[O], EVER[O], ERRT[O], SRE[O], DPRS[O], SRT[O], SRL[O], IRQ[O], IRR[O]

5.2.9 Field 2.309 Defense Biometric Identification System (DBIDS) ID (DBIDS)

This optional field shall contain the DBIDS ID unique identifier for a DBIDS user.


Page 36 of 74

Subfield 1

Item 1

Character Type ANS

Characters 10 to 50



5.2.10 Field 2.310 Personnel Type (PER_TYPE)

This mandatory field shall contain the classification for the person or personnel.

Subfield 1

Item 1

Character Type AS

Characters 3-50


Code Description

ADGR Active Duty or Guard or Reserve on Active Duty Assignment

RESERVE Reserve

NATIONAL_GUARD National Guard

DOD_CIVIL_SERVICE_OR_NAF DoD Civil Service or NAF

DOD_CONTRACTOR DoD Contractor

FEDERAL_ASSOCIATE Federal Associate (e.g., State Dept)

CIVILIAN_ASSOCIATE Civilian Associate (e.g. Red Cross or USO)

VOLUNTEER_AGENCY Member of Service Volunteer Agency

FOREIGN_MILITARY Foreign Military


Page 37 of 74

Code Description

HOST_NATION_MILITARY_OCONUS Host Nation Military (OCONUS)

HOST_NATION_HIRE_OCONUS Host Nation Hire (OCONUS) (e.g. Local National)

DOD_BENEFICIARY DoD Beneficiary (Retiree, Disabled American Veteran, Transitional Comp)

AD_OR_GUARD_OR_RESERVER_ON_ADFM Ad or Guard/Reserve on Active Duty Family Member

RESERVE_FAMILY_MEMBER Reserve Family Member

NATIONAL_GUARD_FAMILY_MEMBER National Guard Family Member

DOD_OR_USCS_OR_NAF_FAMILY_MEMBER DoD or Uniform Service Civil Service or NAF Family Member

DOD_OR_USC_FAMILY_MEMBER DoD or Uniform Service Contractor Family Member

CONVEYANCE_OPERATOR Conveyance Operator

PERSONAL_SERVICES_OR_DOMESTIC Personal Services or Domestic

FACILITIES_SERVICE_PERSON Person (Delivery, Pickup, Repair)

NON_GOVERNMENT_CIVILIAN Non-Government Civilian

DISTINGUISHED_CIVILIAN Distinguished Civilian

OTHER Other

IDENTI_KID Identi-Kid

EPW Enemy Prisoner Of War or Enemy Combatant

FOREIGN_NATION_HIRE_OCONUS Third Country National

FOREIGN_NATION_HIRE_CONTRACTOR_OCONUS Contractor for Third Country National

OEN Operational or Combat Encounter

PEN Patrol or Checkpoint Encounter

MIO Maritime Interception Operation Encounter

UNK Unknown


Page 38 of 74

Used in Transactions: CAR[M], DEK[M], DEU[M], FANC[M], MAP[M], TPRS[M], DPRS[M]

5.2.11 Field 2.311 Name-One (NAM1)

This optional field shall accommodate long names and would generally include the last name or family name (surname).

Subfield 1

Item 1

Character Type AS

Characters 1 to 50



5.2.12 Field 2.312 Name-Two (NAM2)

This optional field shall accommodate long names and would generally include the first name or given name.

Subfield 1

Item 1

Character Type AS

Characters 1 to 50



5.2.13 Field 2.313 Name-Three (NAM3)

This optional field shall accommodate long names and would generally include the middle name.

Subfield 1

Item 1


Page 39 of 74

Character Type AS

Characters 1 to 50



5.2.14 Field 2.314 Name-Four (NAM4)

This optional field shall accommodate long names and would generally include the tribe name.

Subfield 1

Item 1

Character Type AS

Characters 1 to 50



5.2.15 Field 2.315 Verification Identifier (VID)

This mandatory field is present only in VER transactions, shall contain the verification identifier on file with the DoD, and may contain the DoD number, SSN, EDIPI, ISN, BATGUID, or DBIDS number.

Subfield 1

Item 1

Character Type ANS

Characters 4 to 57


Used in Transactions: VER[M]

5.2.15.1 Subfield 2.315_1 Verification Identifier Type (VID_TYPE)

This mandatory field identifies the type of verification identifier.


Page 40 of 74

Subfield all

Item 1

Character Type A

Characters 3 to 7


Code Description

SSN Social Security Number

EDIPI EDIPI

ISN Internment Serial Number

DOD DoD Number

BATGUID BAT Global Unique Identifier

DBIDS DBIDS Identifier


5.2.15.2 Subfield 2.315_2 Verification Identifier Value (VID_VALUE)

This mandatory field shall contain the verification identifier on file with the DoD, and may contain the DoD number, SSN, EDIPI, ISN, BATGUID, or DBIDS number.

Subfield all

Item 2

Character Type ANS

Characters 1 to 50



5.2.16 Field 2.316 Request Mug Shot (RMS)

This optional field shall indicate a request to return the most recent mug shot (frontal pose) on file with DoD for the given subject. Otherwise this field may be omitted.


Page 41 of 74

Subfield 1

Item 1

Character Type A

Characters 1


Code Description

Y Yes

N No

Used in Transactions: IRQ[O]

5.2.17 Field 2.317 Request IAFIS Search (RIS)

This optional field shall indicate a request to search IAFIS in addition to the DoD ABIS.

Subfield 1

Item 1

Character Type A

Characters 1


Code Description

Y Yes

N No

Used in Transactions: CAR[O], DEK[O], DEU[O], FANC[O], MAP[O], TPRS[O], DPRS[O]

5.2.18 Field 2.318 XML-based Rap Sheet (XML)

This field shall contain an electronic rap sheet in XML format. The electronic rap sheet shall consist of lines with a maximum of 174 characters per line. The response formatting shall conform to a future DoD standard.


Page 42 of 74

Subfield 1

Item 1

Character Type ANS

Characters 4 to 400,000

Special Characters: Any 7-bit characters, including printer control

Used in Transactions: SRE[O]

5.2.19 Field 2.319 Name of Latent Technician (LATENT_TECH)

This field contains the name of the latent technician (i.e., lifter or latent processor). The surname should be entered first, separated by a comma and followed by the given name(s), which is separated by a space. This field should contain an alpha string of no more than 100 characters. Commas, hyphens, and blanks are allowed as special characters.

Subfield 1

Item 1

Character Type AS

Characters 3 to 100

Special Characters: comma, hyphen, blank

Used in Transactions: LFIS[M], LFFS[M]

5.2.20 Field 2.320 Name of Latent Submitter (LATENT_SUB)

This field contains the name of the latent submitter. The surname should be entered first, separated by a comma and followed by the given name(s), which is separated by a space. This field should contain an alpha string of no more than 100 characters. Commas, hyphens, and blanks are allowed as special characters.

Subfield 1

Item 1

Character Type AS

Characters 3 to 100

Special Characters: comma, hyphen, blank


Page 43 of 74

Used in Transactions: LFIS[M], LFFS[M]

5.2.21 Field 2.321 Geographic Coordinate - Other (CORD_OTHER)

This optional field contains coordinates at which the submission was collected. These coordinates are expressed in the indicated coordinate system. The subfields of this field are: Coordinate System ID and Coordinate Value. All subfields are mandatory if this field is present. The datum for this field is indicated in Field 2.307 Geographic Coordinate Datum ID.

Subfield 1

Item 1

Character Type AN

Characters 7 to 23


5.2.21.1 Subfield 2.321_1 Coordinate System ID (CORD_OTHER_ID)

This field contains the identifier for the coordinate system used in this field.

Subfield all

Item 1

Character Type A

Characters 4 to 6


System ID Value

Definition Maximum Length of Coordinate Value

MGRS Military Grid Reference System 17 Characters GARS Global Area Reference System 7 Characters GEOREF World Geographic Reference 12 Characters


5.2.21.2 Subfield 2.321_2 Coordinate Value (CORD_OTHER_VALUE)

This field contains the value of the coordinate at which the submission was collected.


Page 44 of 74

A MGRS coordinate is in the form of a 3-character grid Zone Designation, followed by a 2-letter grid square designator and a 4, 6, 8, 10 or 12-digit coordinate (e.g. 42BNG112343556789).

A GARS coordinate in composed of a three-digit longitudinal band designator, followed by a two-letter latitudinal band designator, a one-character quadrant number and a one-character “key”(e.g., 006AG39).

A GEOREF coordinate consists of four letters followed by up to eight numerals (e.g., MKPG12041234).

Subfield all

Item 2

Character Type AN

Characters 3 to 17


5.2.22 Field 2.322 Geographic Coordinate UTM (CORD_UTM)

This optional field contains the Universal Trans Mercator (UTM) grid coordinates at which the submission was collected. The subfields of this field are: Zone, Northing and Easting. All subfields are mandatory if this field is present. The datum for this field is indicated in Field 2.307 Geographic Coordinate Datum ID.

Subfield 1

Item 1

Character Type AN

Characters 4 to 27


5.2.22.1 Subfield 2.322_1 Zone (CORD_UTM_ZONE)

This field contains the UTM zone which the submission was collected. This subfield contains the one or two digit UTM zone number followed by the 8° latitudinal band designator.

Subfield all

Item 1


Page 45 of 74

Character Type AN

Characters 2 to 3


5.2.22.2 Subfield 2.322_2 Northing (CORD_UTM_NORTHING)

This field contains the UTM Northing at which the submission was collected. The data is in whole meters.

Subfield all

Item 2

Character Type N

Characters 1 to 8


5.2.22.3 Subfield 2.322_3 Easting (CORD_UTM_EASTING)

This field contains the UTM Easting at which the submission was collected. The data is in whole meters.

Subfield all

Item 3

Character Type N

Characters 1 to 6


5.2.23 Field 2.323 Father’s Name (FATHER_NAME)

This optional field contains the subject’s Father’s Name.

Subfield 1

Item 1


Page 46 of 74

Character Type ANS

Characters 1 to 80



5.2.24 Field 2.324 Mother’s Name (MOTHER_NAME)

This optional field contains the subject’s Mother’s Name.

Subfield 1

Item 1

Character Type ANS

Characters 1 to 80



5.2.25 Field 2.325 Maternal Grandfather’s Name (MAT_FATHER_NAME)

This optional field contains the subject’s Maternal Grandfather’s Name.

Subfield 1

Item 1

Character Type ANS

Characters 1 to 80



5.2.26 Field 2.326 Paternal Grandfather’s Name (PAT_FATHER_NAME)

This optional field contains the subject’s Paternal Grandfather’s Name.

Subfield 1


Page 47 of 74

Item 1

Character Type ANS

Characters 1 to 80



5.2.27 Field 2.327 Spouse’s Name (SPOUSE_NAME)

This optional field contains the subject’s Spouse’s Name.

Subfield 1 to 10

Item 1

Character Type ANS

Characters 1 to 80



5.2.28 Field 2.328 Child’s Name (CHILD_NAME)

This optional field contains the subject’s Child’s Name.

Subfield 1 to 10

Item 1

Character Type ANS

Characters 1 to 80



5.2.29 Field 2.329 Brother’s Name (BROTHER_NAME)

This optional field contains the subject’s Brother’s Name.


Page 48 of 74

Subfield 1 to 10

Item 1

Character Type ANS

Characters 1 to 80



5.2.30 Field 2.330 Sister’s Name (SISTER_NAME)

This optional field contains the subject’s Sister’s Name.

Subfield 1 to 10

Item 1

Character Type ANS

Characters 1 to 80



5.2.31 Field 2.331 Associate’s Name (ASSOCIATES_NAME)

This optional field contains the subject’s Associate’s Name.

Subfield 1 to 10

Item 1

Character Type ANS

Characters 1 to 80




Page 49 of 74

5.2.32 Field 2.332 Age (AGE)

This optional field contains the subject’s exact age. Field 2.332 shall be used when the person’s exact age is known; otherwise an age range shall be given in field 2.023 (as defined in the EFTS).

Subfield 1

Item 1

Character Type N

Characters 1 to 3


5.2.33 Field 2.333 Nationality (NAT)

This optional field contains the subject’s nationality.

Subfield 1

Item 1

Character Type AS

Characters 1 to 50

Special Characters: dash, space, or comma


5.2.34 Field 2.334 Submission Color Code (SCC)

This optional field contains the subject’s color classification. Red Force includes persons that are Enemy Prisoners of War and Enemy Combatants. Blue Force includes persons that are US Military, DoD Contractors, or DoD civilians. Grey Force includes person that are local nationals, 3rd Country Nationals or Contractors, or Coalition.

Subfield 1

Item 1

Character Type A

Characters 3



Page 50 of 74

Value Definition RED Red Force GRY Gray Force BLU Blue Force


5.2.35 Field 2.335 Dossier Number (DOSSIER)

This optional field contains the subject’s Dossier Number.

Subfield 1 to 10

Item 1

Character Type ANS

Characters 1 to 50



5.2.36 Field 2.336 Iris Images Present (IRS)

This optional field indicates the presence of Type-16 records which contain iris images. This field is mandatory if one or more iris images are present, otherwise, it can be omitted. A value of “Y” indicates that there is at least one Type-16 record in the file which contains iris images. If iris images were not able to be captured because of physical characteristics of the subject (e.g., eye missing), the values “L”, “R”, “B” “A”, “X”, and “Z” may be used to indicate this. If an iris image is present along with one of these conditions, the value “A” may be combined with other values. Other combinations are also possible such as “LX”.

Subfield 1

Item 1

Character Type A

Characters 1 to 2


Value Definition Y Iris images present in Type-16(s) L Not possible to capture left iris Z Left eye missing


Page 51 of 74

R Not possible to capture right iris X Right eye missing B Not possible to capture either iris A Both eyes missing


5.2.37 Field 2.337 Religion (RELIGION)

This optional field contains the subject’s religion.

Subfield 1

Item 1

Character Type AS

Characters 1 to 50

Special Characters: blank, comma, slash, dash


5.2.38 Field 2.350 Alert (ALERT)

The following fields will be used when an ORI would like to supply an alert type. The alert data will be included on the responses from subsequent submissions that have associated matches. These fields can be used with the following search transaction types CAR, MAP, FANC, TPRS, DPRS. These fields may also be returned on the SRE and SRT types of responses.

This Optional field contains alert information that will be used in the case where a new submission into the system results in an IDENTED response against the submission containing the alert data. This field contains five subfields and all five must be completed if this field is used.

Subfield 1

Item 1

Character Type ANS

Characters 5 to 338


Used in Transactions: CAR[O], MAP[O], TPRS[O], DPRS[O], SRE[O], SRT[O]


Page 52 of 74

5.2.38.1 Subfield 2.350_1 Alert Function (ALERT_FUN)

This Mandatory field will set the alert function. The alert function is defined as either 0 - Off, or 1 - On.

Subfield all

Item 1

Character Type N

Characters 1


Code Definition 0 Off 1 On

Used in Transactions: CAR[M], MAP[M], TPRS[M], DPRS[M], SRE[M], SRT[M]

5.2.38.2 Subfield 2.350_2 Alert Category (ALERT_CAT)

This field contains alert category info.

Subfield all

Item 2

Character Type N

Characters 1


Code Definition 1 Detain - known or suspected terrorist - DoD watchlist 2 Detain - known or suspected terrorist - US government watchlist 3 Detain - known or suspected terrorist - other country watchlist 4 Detain - individual of interest to US or coalition forces 5 Detain - known or suspected criminal 6 No US or coalition base access 7 Interview but do not detain 8 Detain but do not interview 9 Do not detain or interview



Page 53 of 74

5.2.38.3 Subfield 2.350_3 Alert Value (ALERT_VAL)

This field lists a value of interest from 1 to 4 of which higher values are of more interest.

Subfield all

Item 3

Character Type N

Characters 1


Value Definition 1 None 2 Low Value 3 Medium Value 4 High Value


5.2.38.4 Subfield 2.350_4 Alert Contact (ALERT_CONTACT)

This field contains the agency and individual contact reference. (e.g. NGIC-CEXC #3905-05 or FBI-VGTOF #12345E3).

Subfield all

Item 4

Character Type ANS

Characters 1 to 80



5.2.38.5 Subfield 2.350_5 Alert Detail (ALERT_DETAIL)

This field will contain any special handling instructions or other information about the individual (e.g. Question about XXXXX, do not transfer any Unclassified Details on the individual, tattoo of the word “EMIR” on his right arm, Non-Sympathetic of US, etc…).

Subfield all


Page 54 of 74

Item 5

Character Type ANS

Characters 1 to 255



5.2.39 Field 2.351 Encounter Protection (EP)

The encounter protection fields defined below allow for an incoming submission to identify and conceal associations made with other previously submitted transactions. This set of fields can be used by an individual ORI to either protect or unprotect a single associated match or all associated matches.

This Optional field contains information that will be used in the case where a new submission wants the subject’s association(s) to be protected or unprotected. Protection of either an individual encounter or multiple encounters will be decided based on the entries in this field. This field contains two subfields and both must be completed if this field is used.

Subfield 1

Item 1

Character Type N

Characters 2


5.2.39.1 Subfield 2.351_1 Encounter Protection Function (EP_FUN)

This field contains information that will be used to determine the action to be taken. It will contain a single numeric value 0=Unprotect, 1=Protect

Subfield all

Item 1

Character Type N

Characters 1


Value Definition


Page 55 of 74

0 Unprotect 1 Protect


5.2.39.2 Subfield 2.351_2 Encounter Protection Level (EP_LEVEL)

This field contains information that will be used to determine the level of protection being assigned to the subject being searched. This field will contain a single numeric value 0 = Single Encounter, 1 = All Encounter

Subfield all

Item 2

Character Type N

Characters 1


Value Definition 0 Single Encounter 1 All Encounter


5.2.40 Field 2.352 Transaction Lookup (LOOKUP)

The Transaction Lookup fields allow for an ORI to submit a transaction to the DoD ABIS system that will update or change existing Transaction Data. This field set can be used in connection with the ALERT, ENCOUNTER and SUBSEQUENT NOTIFICATION field sets to identify existing transactions within the DoD ABIS system.

This Optional field contains information that will be used to identify a transaction within the DoD ABIS system. In the case where a subject has already been searched and an identifier is available, the system will first use the demographic identifier instead of using the modality to search. This field contains two subfields and both must be completed if this field is used.

This field may be repeated up to 99 times to provide 99 identifiers.

Subfield 1 to 99

Item 1

Character Type ANS


Page 56 of 74

Characters 2 to 101


5.2.40.1 Subfield 2.352_1 Transaction Lookup Type (LOOKUP_TYPE)

This field contains information that will be used to identify the type of identifier(s) that is being provided. This field will contain a single numeric value that identifies the demographic identifier type: 0 - TCN, 1 - Subject ID returned previously from ABIS, 2 - BAT_GUID, 3 - Internment Serial Number (ISN).

Subfield all

Item 1

Character Type N

Characters 1


Code Definition 0 TCN 1 Subject ID returned previously from ABIS 2 BAT_GUID 3 Internment Serial Number (ISN)


5.2.40.2 Subfield 2.352_2 Transaction Lookup Identifier Values (LOOKUP_VAL)

This field contains the value of the type specified in the previous field.

Subfield all

Item 2

Character Type ANS

Characters 1 to 100




Page 57 of 74

5.2.41 Field 2.353 Subsequent Notification (SN)

This Optional field contains information that will be used to identify that the current submission is requesting that all future associations will return notifications to the defined email address(es). These subsequent notifications will be sent to the email address list if specified.

Subfield 1

Item 1

Character Type ANS

Characters 2 to 251


5.2.41.1 Subfield 2.353_1 Subsequent Notification Function (SN_FUN)

This field identifies the type of notification that should be used. 0 = No Subsequent Notification, 1 - Use Default, 2 - Multiple as listed.

Subfield all

Item 1

Character Type N

Characters 1


Code Definition 0 No subsequent notification 1 Use default 2 Multiple as listed


5.2.41.2 Subfield 2.353_2 Subsequent Notification Email Addresses (SN_ADDRS)

This field set will define the actual email address(es) where subsequent responses will be sent. Individual addresses will be separated by the semi-colon character (;). This field will override any configuration previously made at the ORI level. This field is mandatory if the Subsequent Notification Function is set to 2 - Multiple as listed

Subfield all


Page 58 of 74

Item 2

Character Type ANS

Characters 1 to 250


Used in Transactions: CAR[C], MAP[C], TPRS[C], DPRS[C], SRE[C], SRT[C]

5.3 Type-4 Records

EBTS uses ITL 1-2000 Type-4 records to carry 500 ppi fingerprint images. EBTS Type-4 records are completely defined in ITL 1-2000.

5.4 Type-7 Records

EBTS uses EFTS Type-7 records to carry latent images. EBTS Type-7 records are completely defined in the EFTS.

5.5 Type-9 Records

EBTS uses EFTS Type-9 records to carry fingerprint minutiae data. EBTS Type-9 records are completely defined in the EFTS.

5.6 Type-10 Records

EBTS uses EFTS Type-10 records to carry facial images. EBTS Type-10 records are completely defined in the EFTS.

5.7 Type-13 Records

EBTS uses ITL 1-2000 Type-13 records to carry high resolution (1000 ppi and above) latent fingerprints. EBTS Type-13 records are completely defined in ITL 1-2000.

5.8 Type-14 Records

EBTS uses ITL 1-2000 Type-14 records to carry 1000 ppi fingerprint images. EBTS Type-14 records are completely defined in ITL 1-2000.


Page 59 of 74

5.9 Type-16 Records

EBTS uses ITL 1-2000 Type-16 records to carry iris images. EBTS Type-16 records are defined in the following sections.

5.9.1 Field 16.001 Logical Record Length (LEN)

This mandatory field shall contain the length of the logical record specifying the total number of bytes, including every byte of every field contained in the record.

Subfield all

Item 1

Character Type N

Characters 3 to 7

Used in Transactions: CAR[M], DEK[M], DEU[M[, MAP[M], DPRS[M]

5.9.2 Field 16.002 Image Designation Character (IDC)

This mandatory field shall be used to identify the image data contained in this record. The IDC in this field shall be a binary representation of the IDC found in the file content field of the Type-1 record.

Subfield all

Item 1

Character Type N

Characters 1 to 4


5.9.3 Field 16.003 Feature Identifier (FID)

This mandatory field shall contain an identifier indicating which eye is represented by the image in the record. An entry of “0” in this field indicates that the image in this record is undefined. An entry of “1” in this field indicates that the image in this record is of a right eye. An entry of “2” in this field indicates that the image in this record is of a left eye.

Subfield 1

Item 1

Character Type N


Page 60 of 74

Characters 1


Code Description

0 Left or Right eye not defined

1 Right Eye

2 Left Eye


5.9.4 Field 16.004 Make/Model/Serial Number (MMS)

This optional field contains the make, model, and serial number for the iris capture device.

Subfields 1

Item 1

Character Type ANS

Characters 3 to 150


Used in Transactions: CAR[O], DEK[O], DEU[O[, MAP[O], DPRS[O]

5.9.4.1 Subfield 16.004_1 Make (MMS_MAKE)

This field contains the make for the iris capture device.

Subfield all

Item 1

Character Type ANS

Characters 1 to 50




Page 61 of 74

5.9.4.2 Subfield 16.004_2 Model (MMS_MODEL)

This field contains the model for the iris capture device.

Subfield all

Item 2

Character Type ANS

Characters 1 to 50



5.9.4.3 Subfield 16.004_3 Serial (MMS_SERIAL)

This field contains the serial number for the iris capture device.

Subfield all

Item 3

Character Type ANS

Characters 1 to 50



5.9.5 Field 16.005 Image Format (IFM)

This mandatory ASCII field shall contain the image format code. It shall be used to specify the type of image format used.

Subfield 1

Item 1

Character Type N

Characters 1 to 2


Page 62 of 74


Code Description

0 Undefined

2 Gray Scale (mono) raw image format

4 RGB (color) raw image format

6 RGB gray scale (mono) JPEG image format

8 RGB (color) JPEG image format


5.9.6 Field 16.006 Horizontal line length (HLL)

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

Subfield all

Item 1

Character Type N

Characters 3 to 4


5.9.7 Field 16.007 Vertical line length (VLL)

This mandatory ASCII field shall contain the number of horizontal lines present in the transmitted image.

Subfield all

Item 1

Character Type N

Characters 3 to 4



Page 63 of 74

5.9.8 Field 16.008 Scale units (SLC)

This mandatory ASCII field shall specify the units used to describe the image sampling frequency (pixel density). A “1” in this field indicates pixels per inch; a “2” indicates pixels per centimeter. A “0” in this field indicates that no scale is given. For this case, the quotient of HPS/VPS gives the pixel aspect ratio.

Subfield all

Item 1

Character Type N

Characters 1


5.9.9 Field 16.009 Horizontal pixel scale (HPS)

This mandatory ASCII field shall specify the integer pixel density used in the horizontal direction providing that the scale unit fields contain a “1” or a “2”. Otherwise, it indicates the horizontal component of the pixel aspect ratio.

Subfield all

Item 1

Character Type N

Characters 1 to 4


5.9.10 Field 16.010 Vertical pixel scale (VPS)

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

Subfield all

Item 1

Character Type N

Characters 1 to 4



Page 64 of 74

5.9.11 Field 16.011 Compression algorithm (CGA)

This mandatory ASCII field shall specify the algorithm used to compress the image. An entry of “NONE” in this field indicates that the data contained in this record are uncompressed. The domain registrar, DoD Biometrics, maintains a registry of acceptable compression techniques and corresponding codes.

Subfield all

Item 1

Character Type A

Characters 4 to 5


Code Description

NONE Uncompressed

JPEGB JPEG


5.9.12 Field 16.012 Bits per pixel (BPS)

This mandatory ASCII field shall contain the number of bits used to represent a pixel.

Subfield all

Item 1

Character Type N

Characters 1 to 2


5.9.13 Field 16.013 Iris Image Quality (IIQ)

This optional field shall indicate the image quality value. This field is defined in ANSI-INCITS 379-2004 – Iris Image Interchange Format.


Page 65 of 74

Subfield 1

Item 1

Character Type N

Characters 2 to 3


5.9.14 Field 16.014 Rotation Angle of Eye (RAE)

This optional field shall indicate the rotation angle of the eye. For rectilinear images: rotation angle = round (65536 * angle / 360) modulo 65536. The angle is measured in degrees from horizontal. The value “FFFF” indicates rotation angle of eye is undefined. For polar images, entry shall be “FFFF.”

Subfield 1

Item 1

Character Type AN

Characters 1 to 4


5.9.15 Field 16.015 Rotation Uncertainty (RUC)

This optional field shall indicate the rotation uncertainty. The rotation uncertainty is equal to round (65536 * uncertainty / 180). The uncertainty is measured in degrees and is the absolute value of maximum error. The value “FFFF” indicates uncertainty is undefined.

Subfield 1

Item 1

Character Type AN

Characters 1 to 4



Page 66 of 74

5.9.16 Field 16.016 Image Properties (IPR)

This optional field shall contain the image property code, and shall contain six information items. The information items shall indicate the specific:

1. horizontal orientation 2. vertical orientation 3. scan type 4. iris occlusions 5. occlusion filling 6. boundary extraction

These subfields are defined in ANSI-INCITS 379-2004 – Iris Image Interchange Format.

Subfield 1

Item 1

Character Type N

Characters 6


5.9.16.1 Subfield 16.016_1 Horizontal Orientation (IPR_HZ_OR)

This field contains the horizontal orientation.

Subfield all

Item 1

Character Type N

Characters 1


Code Description

0 Undefined

1 Base

2 Flipped


Page 67 of 74

5.9.16.2 Subfield 16.016_2 Vertical Orientation (IPR_VR_OR)

This field contains the vertical orientation.

Subfield all

Item 2

Character Type N

Characters 1


Code Description

0 Undefined

1 Base

2 Flipped

5.9.16.3 Subfield 16.016_3 Scan Type (IPR_ST)

This field contains the scan type.

Subfield all

Item 3

Character Type N

Characters 1


Code Description

0 Undefined

1 Progressive

2 Interlace Frame

3 Interlace Field


Page 68 of 74

5.9.16.4 Subfield 16.016_4 Iris Occlusions (IPR_IRIS_OCC)

This field contains the iris occlusions.

Subfield all

Item 4

Character Type N

Characters 1


Code Description

0 Undefined

1 Processed

5.9.16.5 Subfield 16.016_5 Occlusion Filling (IPR_OCC_FILL)

This field contains the occlusion filling.

Subfield all

Item 5

Character Type N

Characters 1


Code Description

0 Zerofill

1 Unitfill

5.9.16.6 Subfield 16.016_6 Boundary Extraction (IPR_BEXT)

This field contains the boundary extraction.


Page 69 of 74

Subfield all

Item 6

Character Type N

Characters 1


Code Description

0 Undefined

1 Processed

5.9.17 Field 16.017 Device Unique Identifier (DID)

This optional field shall contain a 16-chatacter string uniquely identifying the device or source of the data. This data can be one of: (1) Device Serial Number, identified by the first character “D,” (2) Host PC Mac address, identified by the first character “M,” (3) Host PC processor ID, identified by the first character “P,” and (4) No Serial Number, identified by all zero’s.

Subfield 1

Item 1

Character Type ANS

Characters 16



5.9.18 Field 16.018 Global Unique Identifier (GUID)

This optional field shall contain a 16-character string to indicate a GUID.

Subfield 1

Item 1

Character Type AN

Characters 16


Page 70 of 74


5.9.19 Field 16.019 Image Transformation (ITF)

This optional field shall specify the transformation type used in the record. A “0” in this filed indicates transformation type undefined,; a “1” indicates standard transformation type.

Subfield 1

Item 1

Character Type N

Characters 1


Code Description

0 Undefined

1 Standard


5.9.20 Field 16.999 Iris Image (DAT)

This mandatory field shall contain the grayscale or color data from an iris, is always assigned field number 999, and must be the last physical field in the feature record.

Subfield 1

Item 1

Character Type B1

Characters 1 to no limit



Page 71 of 74

APPENDIX A: ACRONYM LIST

ACRONYM DEFINITION

ABIS Automated Biometric Identification System

AFIS Automated Fingerprint Identification System

ANSI/NIST American National Standards Institute/National Institute of Standards and Technology

ASCII American Standard Code for Information Interchange

BAT Biometrics Automated Toolset

BTF DoD Biometrics Task Force

CAR Criminal 10-print Submission

CBEFF Common Biometric Exchange File Format

CJIS Criminal Justice Information Systems

CPR Subject Photo Request

DBIDS Defense Biometric Identification System

DEK Known Deceased


DMDC Defense Manpower Data Center

DoD Department of Defense

DPRS DoD Flat Print Rap Sheet Search

EBTS DoD Electronic Biometric Transmission Specification

EDIPI Electronic Data Interchange Personal Identifier

EFTS Electronic Fingerprint Transmission Specification

EPW Enemy Prisoner of War

ERRI Image Transaction Error

ERRL Latent Transaction Error


EVER Verification Error Response

FANC Federal Applicant No Charge

FBI Federal Bureau of Investigations

FIPS Federal Information Processing Standard

GMT Greenwich Mean Time

GUID Global Unique Identifier

IED Improvised Explosive Device


Page 72 of 74

ACRONYM DEFINITION

IOC Initial Operating Capability

IRQ Fingerprint Image Request


ISN Internment Serial Number

ISR Image Response Summary


LFIS Latent Fingerprint Image Search

LRE Latent Result

MAP Miscellaneous Applicant

MGRS Military Grid Reference System

MIO Maritime Interception Operation Encounter

NCIC National Crime Information Center

NIST National Institute of Standards and Technology

ORI Originating Agency Identifier

PIV Personal Identity Verification

ppi Pixels Per Inch

PRR Photo Response

SOP Standard Operating Procedure


SRL Search Result – Latent


TCN Transaction Control Number

TOT Types of Transactions

TPIS 10-print Fingerprint Image Searches

TPRS 10-print Rap Sheet Search

USO United Service Organization

UTC Universal Time Code

v version


VRSP Verification Response – Electronic

WSQ Wavelet Scalar Quantization

XML Extensible Markup Language


Page 73 of 74

APPENDIX B: ACCOMMODATING LONG NAMES

A field for carrying the name of the person from whom data was captured is required in most EFTS and EBTS transactions (for example, latent transactions are exceptions). This field is defined in the EFTS as NAM and is numbered 2.018. The EFTS NAM field has a maximum of 30 characters. While this standard has been in use in an operational system for many years, many people have names that are longer than 30 characters (including commas and spaces). During the design of the EBTS, the authors recognized the issues surrounding the inadequate length of the EFTS name field and added an extra set of four fields, of 50 characters each, to the EBTS to accommodate long names. These fields are titled “Name-One”, “Name-Two”, “Name-Three”, and “Name-Four” and have field identifiers of 2.311, 2.312, 2.313, and 2.314 respectively. The originator of an EBTS transaction must populate the 2.018 NAM field with 30 or fewer characters. The 2.018 NAM field is formatted per EFTS and NCIC Code Manual instructions (e.g., surname followed by a comma, followed by the given name(s)). No instructions are provided for fitting long names into those 30 characters (other than abbreviating middle names). Instructions for shortening names to 30 characters are a local matter. Optionally, the originator may make use of the four additional EBTS fields. Section 5.2, of this document describes that Name-One can be used for surname, Name-Two can be used for given name, Name-Three can be used for middle name, and Name-Four can be used for tribe name. These instructions are for guidance only. The process used to populate these fields (and whether or not they are used at all) in any given implementation is a local matter. The following figure shows the name fields contained in an EBTS Type-2 Logical Record. The 2.018 NAM field must be populated per EFTS convention. The 2.311 through 2.314 name fields may optionally be populated per local convention. The figure shows an example of the use of those fields and does not imply a required implementation. In this example, the person’s:

• Surname (Public) is stored in field 2.311, Name-One (as suggested by Section 5.2.11 - “This optional field shall accommodate long names and would generally include the last name or family name (surname)”)

• First name (John) is stored in field 2.312, Name-Two (as suggested by Section 5.2.12 - “This optional field shall accommodate long names and would generally include the first name or given name”)

• Middle name (Quincy) is stored in field 2.313, Name-Three (as suggested by Section 5.2.13 - “This optional field shall accommodate long names and would generally include the middle name”)

• Tribe name (Crips) is stored in field 2.314, Name-Four (as suggested by Section 5.2.14 - “This optional field shall accommodate long names and would generally include the tribe name“)


Page 74 of 74

Mr. Public is a member of the tribe called the Crips

Type-2 Logical Record2.

018

NA

M

2.31

1 na

me-

one

2.31

2 na

me-

two

2.31

3 na

me-

thre

e

2.31

4 na

me-

four

John Quincy Public

PUBLIC, JOHN QUINCY

Department of Defense Electronic Biometric Transmission … · 2011-05-14 · Electronic Biometric...

Documents

Transcript of Department of Defense Electronic Biometric Transmission … · 2011-05-14 · Electronic Biometric...