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 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 Subcommittee, Identification Services Coordination Group (ISCG), reviews drafts of the EBTS. This group provides comments, ranging from very specific to broad, to enhance the standard and provide opportunities for user feedback. The approval process takes into account the impact on legacy users, system contributors, and interoperability stakeholders, particularly when adding new information and changing functionalities. Changes to the EBTS require close coordination with users to articulate effects on programming, costs, business objectives, and other factors that need to be projected and reconciled accordingly.
EBTS v10.0 and its cumulative Technical and Operational Updates (TOUs) contain the technical changes necessary for FBI/CJIS to deploy and support NGI Increment 4, which reached Full Operational Capability in the summer of 2014. TOUs are fully incorporated directly into the EBTS, with previous versions moved into the archive. In addition, a redline excerpt of the changes associated with the most recent TOU are provided for quick reference. Changes to the document are either deletions or insertions. Both are identified in red text and/or strikethrough font. 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.
**10.0.x TOUs represent as-delivered NGI Increment 4 functionality and adoption of these cumulative updates is required for EBTS Version 10 compliance.
Use comment form to submit input.
The following EBTS XML IEPD v10.0.8 contains changes necessary for NGI Increment 4 XML Schema for Web Services, corresponding to TOU #8, EBTS 10.0.8. 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 the EBTS Compliance Tool Suite is to provide users with capabilities to prepare and validate EBTS transactions. There are currently two tools in the suite:
These tools run as Java applications on your computer. In this way, no information regarding your transaction, including Personally Identifiable Information (PII), leaves your computer.
The EBTS Reference tool provides users with the ability to display selected information from the EBTS specification.
To use the tool:
For additional information on using the EBTS Reference Tool, click here for a Help document.
The EBTS Transaction tool provides users with the ability to validate user-generated EBTS transactions.
To use the tool:
Thank you for your patience, as these tools often take a significant amount of time to download.
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.