DPS created the EAR program in response to a mandate of Chapter 66 of the Code of Criminal Procedure, which requires the Department to be able to receive criminal history information in an electronic fashion. The EAR program allows local criminal justice agencies to report arrests to the Department in electronic fashion. The program is made up of many components including the local fingerprint capture station, the local records management system, the Multi Biometric Identification System (MBIS), the Computerized Criminal History system (CCH) as well as the FBI's Next Generation Identification (NGI). The EAR program strives to navigate the maze of the aforementioned systems to deliver positive fingerprint identification to contributing agencies in a timely fashion while also facilitating the electronic update of the CCH system. In order to fully understand the EAR concept, each of the component parts of the EAR process must be reviewed. What follows is a breakdown of the EAR program by its various parts.
Local Fingerprint Capture Device – Because DPS will not accept arrest information without associated fingerprints, the local fingerprint capture device is the most critical component in the EAR process. The methodology employed to capture fingerprints electronically is through a livescan. Livescan devices allow arresting agencies to forego the use of ink and paper in order to capture fingerprints of detainees. Using livescan, arresting agencies actually roll the subject's fingerprints across a glass platen where the fingerprint images are digitized and stored electronically. Livescan devices are certified as being compliant with the FBI's Image Quality Specification (IQS). All fingerprint capture devices must be IQS certified in order to participate in the EAR program. The FBI maintains an updated listing of livescan devices that have received IQS certification. Due to the requirements of the IQS, the resultant captured fingerprint images are quite large in size. Because, in their native .TIFF format images are too large for effective electronic transport, the images must subsequently be compressed. Furthermore, since the FBI requires that compression and must have little or no quality loss, the only compression algorithm that is acceptable is Wavelet Scalar Quantization (WSQ).
Local Records Management System – One of the key components of EAR involves the local contributor's ability to format arrest demographic data into the EAR data format used by DPS. This EAR data format then must be consolidated with the fingerprints digitized at the capture device. This step generally requires that the local RMS interface with the capture device in order to produce the final EAR record. While in truth a local records management system (RMS) is not required to complete EAR, most local agencies have a "book-in" system already in place and are justifiably reluctant to do duplicative data entry.
EAR Record – The data format required by the EAR program is compliant with the National Institute for Standards and Technology's (NIST) fingerprint information exchange standard as well as the FBI's Electronic Biometric Transmission Specification (EBTS) interface document. The primary components of the EAR fingerprint record is as follows:
- Type 1 Record – contains basic header information regarding the contents of the entire record.
- Type 2 Record – contains the arrest and personal identification information of the record. The data elements used in the type two record are derived from the DPS remote terminal interface and the Texas Type 2 document. The elements themselves are defined in the DPS CCH data dictionary. All three of these publications as well as the FBI's EBTS accompany this document in electronic format.
- Type 4 Record – contains the WSQ compressed fingerprint images.
- Type 8 Record – contains data representing the signature of a subject and/or an operator (optional).
- Type 10 Record – contains the .JPG mug shot image of the subject (optional).
- Type 15 Record – contains the palm prints of the subject (optional).
The Multi Biometric Identification System (MBIS) – At the MBIS, the fingerprints in the Type 4 record are decompressed and searched against the existing database of known fingerprints. At this point in the process, the need for adherence to the IQS is paramount. If the quality of the fingerprints has been compromised, the submission will be rejected by the MBIS and the arresting agency must resubmit the transaction. If the IQS integrity is maintained and the fingerprints are of good quality, a positive identification can be made by MBIS within minutes of the receipt of the electronic submission.
The Computerized Criminal History System (CCH) - After MBIS positively identifies the arrest fingerprints, the associated demographic data is forwarded to CCH for application to the criminal history repository. Prior to application, CCH edits the data one final time in order to catch any data edit errors that might have made it through the earlier processing. Once the data is applied to CCH, the arresting agency is notified of the CCH update by paper rap or through an electronic notification.
EAR Requirements – In order for an agency to participate in the EAR program, the agency must notify the Livescan Coordinator to verify the purpose of participation. Agencies will not automatically be approved to submit electronic submissions to DPS. The agency will also need to sign and abide by the Livescan User Agreement, fill out the EAR authorization form, fill out the Arrest Process Flow document and then provide the completed documents to the Livescan Coordinator.
Authorization Forms
- Agency LS User Agreement v1.3 (PDF)
- Arrest Process Flow DC (DOC)
- Arrest Process Flow SNF (DOC)
- Class C Arrest Process Flow SNF (DOC)
- DPS Owned LS User Agreement v1.3 (PDF)
- EAR Authorization Form S&F via FTP v1.4 (PDF)
- ME LS User Agreement v1.1 (PDF)
- ME Authorization Form v1.1 (PDF)
Livescan Codes and ORIs
- Arresting Agencies ORIs (XLS) 08-09-2024
- Court ORIs (XLS) 08-09-2024
- Full Offense Code List (XLS) 03-06-2024
Livescan Record Specifications
- Agency Instructions for Submitting EFT via FTP-SFTP v3.1 (PDF)
- ANSI/NIST-ITL
- CCH Transaction Formats (PDF)
- CCH Data Dictionary
- EBTS
- TCN Generation S&F (PDF)
- Texas NIST Type 2 format (PDF)
- TRN Generation (PDF)
- TX Type II (XLS)
2024 EAR Monthly Error Reports
- 2024-01 Chart (PDF)
- 2024-01 Literal (PDF)
- 2024-01 Vendor Chart (PDF)
- 2024-02 Chart (PDF)
- 2024-02 Literal (PDF)
- 2024-02 Vendor Chart (PDF)
- 2024-03 Chart (PDF)
- 2024-03 Literal (PDF)
- 2024-03 Vendor Chart (PDF)
- 2024-04 Chart (PDF)
- 2024-04 Literal (PDF)
- 2024-04 Vendor Chart (PDF)
- 2024-05 Chart (PDF)
- 2024-05 Literal (PDF)
- 2024-05 Vendor Chart (PDF)
- 2024-06 Chart (PDF)
- 2024-06 Literal (PDF)
- 2024-06 Vendor Chart (PDF)
- 2024-07 Chart (PDF)
- 2024-07 Literal (PDF)
- 2024-07 Vendor Chart (PDF)
- 2024-08 Chart (PDF)
- 2024-08 Literal (PDF)
- 2024-08 Vendor Chart (PDF)
- 2024-09 Chart (PDF)
- 2024-09 Literal (PDF)
- 2024-09 Vendor Chart (PDF)
- 2024-10 Chart (PDF)
- 2024-10 Literal (PDF)
- 2024-10 Vendor Chart (PDF)
- 2024-11 Chart (PDF)
- 2024-11 Literal (PDF)
- 2024-11 Vendor Chart (PDF)
2023 EAR Monthly Error Reports
- 2023-01 Chart (PDF)
- 2023-01 Literal (PDF)
- 2023-01 Vendor Chart (PDF)
- 2023-02 Chart (PDF)
- 2023-02 Literal (PDF)
- 2023-02 Vendor Chart (PDF)
- 2023-03 Chart (PDF)
- 2023-03 Literal (PDF)
- 2023-03 Vendor Chart (PDF)
- 2023-04 Chart (PDF)
- 2023-04 Literal (PDF)
- 2023-04 Vendor Chart (PDF)
- 2023-05 Chart (PDF)
- 2023-05 Literal (PDF)
- 2023-05 Vendor Chart (PDF)
- 2023-06 Chart (PDF)
- 2023-06 Literal (PDF)
- 2023-06 Vendor Chart (PDF)
- 2023-07 Chart (PDF)
- 2023-07 Literal (PDF)
- 2023-07 Vendor Chart (PDF)
- 2023-08 Chart (PDF)
- 2023-08 Literal (PDF)
- 2023-08 Vendor Chart (PDF)
- 2023-09 Chart (PDF)
- 2023-09 Literal (PDF)
- 2023-09 Vendor Chart (PDF)
- 2023-10 Chart (PDF)
- 2023-10 Literal (PDF)
- 2023-10 Vendor Chart (PDF)
- 2023-11 Chart (PDF)
- 2023-11 Literal (PDF)
- 2023-11 Vendor Chart (PDF)
- 2023-12 Chart (PDF)
- 2023-12 Literal (PDF)
- 2023-12 Vendor Chart (PDF)