The FBI Criminal Justice Information Services Division is moving toward a system that will contain a complete biometric and biographic profile of the subject records in its databases. Although fingerprints will continue to be the FBI's primary mode of identification for the near future, the scope of the EBTS has been expanded over previous versions to include additional biometric modalities (e.g., palm print, facial, and iris) in recognition of the rapidly developing biometric identification industry. The most recent update to the American National Standards Institute /National Institute of Standards and Technology-Information Technology Laboratory 1-2011 standard (ANSI/NIST-ITL 1-2011) includes new record types to facilitate data sharing of new biometric modalities. Implementers should be aware that NIST has published an Errata for ITL 1-2011, correcting some errors in the Type-9 record. Integrating biometric data in accordance with the ANSI/NIST standard and subsequent Errata, the FBI EBTS provides a description of all requests and responses associated with electronic fingerprint and other biometric identification services.
The process of updating an FBI implementation of the ANSI/NIST-ITL 1-2011 standard involves many considerations as well as iterations of reviews and approvals. The EBTS is governed by the Advisory Policy Board (APB) process. Specifically, the Identification Services Coordination Group (ISCG) reviews drafts of the EBTS prior to APB approval. This group provides comments, ranging from very specific to broad, to enhance the standard along with user feedback. The approval process takes into account the impact on legacy users, IAFIS contributors, and interoperability stakeholders, particularly when adding new information and changing functionalities. The resultant changes directly affect cost considerations, business objectives, and other factors that need to be projected and reconciled accordingly.
EBTS v10.0 contains the technical changes necessary for FBI/CJIS to deploy NGI Increment 4 - targeted for summer 2014. EBTS v10.0 also contains interface definitions for the new services within NGI Increment 4. Please refer to "EBTS Summary of Changes" link below for an overview of these changes. All comments to this standard may be submitted via this website by using the 'Comment' button at the top of this web page.
*You must have Adobe Reader to view a PDF file.
Use comment form to submit input.
**This Enhanced Edition contains updated workflow figures and minor typographical corrections.
The following EBTS XML IEPD v10.0 contains all the necessary changes for NGI Increment 4 XML Schema for Web Services, corresponding to EBTS 10.0. All comments to this version may be submitted via this website by using the 'Comment' button at the top right of this window.
The purpose of these tools is to provide users with a suite of tools to use in preparing and validating EBTS transactions. There are currently two tools in the suite: The EBTS TOT Reference Tool and the EBTS Transaction Checker Tool. Each of these tools is described and may be invoked from the paragraphs below.
The EBTS TOT Reference tool provides users with a list of the mandatory and optional fields for the type of transaction (TOT) selected. Type 1 TOT requirements are static but Type 2 and optional information requirements will change depending on the TOT selected.
Note: The mandatory and optional fields listed also apply to EBTS XML. However, please realize that the Logical Record Length for all record types is not required (actually not represented) for EBTS XML.
To use the tool, select the button below and then select a TOT. The records and fields for that TOT will be display and identified as mandatory or optional.
The EBTS Transaction Checker tool provides users with the ability to validate existing EBTS transactions.
Note: This tool runs as an application on your computer. In this way, no information regarding your transaction leaves your computer.
To use the tool, selection the button below. The tool will display a disclaimer, allow the selection of traditional EBTS transaction files, validate the transactions(s), and report any errors—either through on-screen display or export to a report file.
To contact the FBI EBTS Working Group to request items to be placed on monthly meeting agenda, items and recommendations for future changes along with requesting new values for current tables in the EBTS and new allocations of Type-2 fields.