179
TEXAS CRIME INFORMATION CENTER 2000 USER SPECIFICATION PAGES Revised May, 2002 Texas Department of Public Safety Crime Information Center, MSC 0233 PO Box 4143 Austin, TX 78765-4143 e-mail: [email protected] Revised May, 2002 Version 1.1

tlets.dps.texas.gov · Web viewThese are criminal history records mainly associated with arrest events that originated in Texas. Additionally, juvenile records associated with arrest

  • Upload
    ngongoc

  • View
    311

  • Download
    8

Embed Size (px)

Citation preview

TEXAS CRIME INFORMATION CENTER 2000USER SPECIFICATION PAGES

Revised May, 2002

Texas Department of Public SafetyCrime Information Center, MSC 0233

PO Box 4143Austin, TX 78765-4143

e-mail: [email protected]

Revised May, 2002 Version 1.1

PREFACE FOR TEXAS USERS

The Federal Bureau of Investigation (FBI) has administered the National Crime Information Center (NCIC) since its creation in the late 1960's. NCIC operates under a shared management agreement concept in which the FBI shares responsibility for management with a Control Terminal Agency (CTA) in each state. The Department of Public Safety (DPS) is the CTA for Texas. Any questions concerning the Texas Crime Information Center (TCIC) or NCIC should be directed to the TCIC Control Center, Crime Records Service (CRS) at (512) 424-2088, toll free at 1-866-266-TCIC (8242), or mnemonic address "CRDP".

The NCIC 2000 Operating Manual was written by the NCIC Section of the FBI to instruct users nationwide in the functions of the NCIC 2000 system. The CRS has provided one or more pages titled "TEXAS USER SPECIFICATIONS PAGES" to be included in the front of each chapter of this manual. These pages provide special information necessary for Texas Law Enforcement Telecommunications System (TLETS) users. This manual serves Texas users as the operating guide for both TCIC/NCIC 2000.

In TCIC/NCIC 2000 there are four categories of transactions:

TransactionCategory

Description Specification Example

NCIC Only No data kept in Texas (TCIC 2000), also known as "pass thru" transactions.

NCIC 2000 Operating Manual

Enter Stolen Gun (EG)

NCIC/TCIC Data is kept in TCIC 2000 files. Transaction formats and data are exactly the same as NCIC 2000.

NCIC 2000 Operating Manual

Enter Wanted Person into TCIC and NCIC (EW)

NCIC with additional TCIC Specifications

Data is kept in TCIC 2000 files. Transaction formats and data match NCIC 2000 where applicable.

NCIC 2000 Operating Manual; TCIC 2000 Texas User Specifications Pages

Query Vehicle (QV)

TCIC Only Data is kept in TCIC 2000. The transaction is not sent to NCIC 2000.

NCIC 2000 Operating Manual; TCIC 2000 Texas User Specifications Pages

Enter Abandoned/Stored Boat (ERB)

The TCIC 2000 Texas User Specifications Pages document the requirements for the third and fourth categories – NCIC transactions with additional TCIC specifications and TCIC Only transactions. For all others, refer to the NCIC 2000 Operating Manual.

Revised May, 2002 1 Version 1.1

The table below depicts the data file locations of records entered into TCIC and/or NCIC 2000.

BOTH TCIC and NCIC FILES NCIC ONLY FILES TCIC ONLY FILESStolen Vehicles Stolen Vehicle/Boat Parts Abandoned/Stored VehiclesFelony Vehicles Stolen Guns Abandoned/Stored Boats

Stolen License Plates Recovered Guns Concealed Handgun LicenseesStolen Boats Lost Guns H.E.A.T. Vehicles

Wanted Persons Stolen Articles TCIC-Only Wanted PersonsTemporary Felony Wants Stolen Securities Officer Threat

Computerized Criminal History(TCIC CCH, JJIS [Juvenile Justice

Information Systems] and NCIC’s III)

Violent Gang and Terrorist Organization

Individual IdentityPerson Records

Protective Orders U. S. Secret Service Protective File TX GANGWanted Juveniles INS Deported Felon Name Based Disposition

Missing/Unidentified Persons Foreign Fugitive TCIC Only Protective OrdersOn-line ORI Convicted Persons on

Supervised ReleaseRegistered Sexual Offender

As indicated above, some files are in both TCIC/NCIC 2000. All TCIC 2000 entries will receive a unique identifying number known as the "TIC" number. The "TIC" number has no correlation to the "NIC" number. No transactions can be performed using the "TIC" number.

The NCIC 2000 Operating Manual indicates that the "NIC" can be used in modify, cancel, locate, and clear transactions. Texas policy does not allow for use of the "NIC" number to identify records for these transactions.

Texas users will receive either one or two replies to their TCIC/NCIC 2000 transactions, depending upon whether the record is maintained in TCIC 2000 only, NCIC 2000 only, or both TCIC and NCIC 2000.

At the time of entry, agencies should always insure that a record intended for both TCIC/NCIC 2000 has actually been accepted by both systems. (This also applies to the verification of any modification, cancellation, locate or clear transaction performed on a record entered.) This check is accomplished by performing an administrative inquiry on the record.

The NCIC 2000 Operating Manual indicates an image file is available for NCIC 2000 records. Image capability is not available for Texas users at this time.

There are two types of on-line inquiry Message Key (MKE) prefixes: "Q" inquiries – to be used for routine investigative purposes and "Z" inquiries – to be used for administrative (validations), training (test), and quality control purposes.

The Texas User Specifications Pages list the TLETS transaction codes applicable to that file.

Revised May, 2002 2 Version 1.1

For training purposes, agencies may enter test records into TCIC/NCIC 2000 using the header TN01 (NCIC 2000). The test records will not generate any notifications nor will batch processing be performed in the test system.

By replacing 1N01 with TN01 in the transaction header, the transaction becomes a "TEST" transaction and is routed to test databases in TCIC and NCIC which are completely separate from the production databases. Information entered via a TN01 transaction cannot be queried via a 1N01 transaction. TN01 transactions utilize the normal TLETS connection. No special communication requirements are needed.

Revised May, 2002 3 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESFILE LINKS

BOAT FILE

COMPUTERIZED CRIMINAL HISTORY (CCH) FILE

CONCEALED HANDGUN LICENSE FILE

INDIVIDUAL IDENTITY FILE

INTERESTED AGENCY FLAG TRANSACTIONS

LICENSE PLATE FILE

MISSING PERSON FILE

THREAT AGAINST PEACE OFFICER FILE

ORIGINATING AGENCY IDENTIFIER (ORI) FILE

PROTECTIVE ORDER FILE

REGISTERED SEXUAL OFFENDER FILE

TDCJ CORRECTIONS TRACKING SYSTEM (CTS)

VEHICLE FILE

WANTED PERSON FILE

Revised May, 2002 4 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESBOAT FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 MESSAGE KEY (MKE) CODES 1

2. STOLEN BOAT TRANSACTIONS 12.1 ENTRY (EB) 1

2.1.1 EXAMPLE OF ENTRY MESSAGE 12.1.2 ADDITIONAL GUIDELINES FOR ENTRY 1

2.1.2a BOAT REGISTRATION 12.1.2b OAN FIELD 22.1.2c MODEL NUMBERS, ENGINE NUMBERS, OR MOTOR NUMBERS 22.1.2d BOAT TRAILERS 2

2.2 MODIFY (MB) 22.2.1 EXAMPLE OF MODIFICATION MESSAGE 22.2.2 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION 2

2.3 CANCEL (XB) 32.3.1 EXAMPLE OF CANCELLATION MESSAGE 3

2.4 INQUIRY (QB) 32.4.1 EXAMPLE OF INQUIRY MESSAGE 3

2.5 LOCATE (LB) 42.5.1 EXAMPLE OF LOCATE MESSAGE 4

2.6 CLEAR (CB) 42.6.1 EXAMPLE OF CLEAR MESSAGE 4

3. ABANDONED/STORED BOAT TRANSACTIONS 53.1 INTRODUCTION 53.2 MESSAGE KEY (MKE) CODES 53.3 CRITERIA FOR ENTRY 53.4 RECORD RETENTION 53.5 MESSAGE FIELD CODES AND EDITS 63.6 ADDITIONAL MANDATORY FIELDS FOR ENTRY 63.7 ENTRY (ERB) 6

3.7.1 EXAMPLE OF ENTRY MESSAGE 63.7.2 ADDITIONAL GUIDELINES FOR ENTRY 6

3.7.2a BOAT REGISTRATION 63.7.2b OAN FIELD 63.7.2c ENGINE NUMBERS OR MOTOR NUMBERS 73.7.2d BOAT TRAILERS 7

3.8 MODIFY (MRB) 73.8.1 WHEN TO USE A MODIFICATION MESSAGE 73.8.2 EXAMPLE OF MODIFICATION MESSAGE 7

3.9 CANCEL (XRB) 83.9.1 WHEN TO USE A CANCELLATION MESSAGE 83.9.2 EXAMPLE OF CANCELLATION MESSAGE 83.9.3 ADDITIONAL GUIDELINES FOR CANCELLATION 8

3.9.3a RPP FIELD 8

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Boat File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the Stolen Boat File:

MKE FORMATEB ENTER STOLEN BOAT RECORDMB MODIFY STOLEN BOAT RECORDXB CANCEL STOLEN BOAT RECORDLB LOCATE STOLEN BOAT RECORDCB CLEAR STOLEN BOAT RECORDQB BOAT INQUIRY (INVESTIGATIVE PURPOSES)ZB BOAT INQUIRY (ADMINISTRATIVE/TEST PURPOSES)

2. STOLEN BOAT TRANSACTIONS

2.1 ENTRY (EB)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EB ENTER STOLEN BOAT RECORD MKE: EB- A ORI: TX DPS0000 REG: TX1234AB RES: TX REY: 2002 HUL: PL PRO: IN BHN: ZZN12345B678________ BYR: 2000 BMA ZZN_____________________ BTY:JSK BLE: 10BCO: BLU/WHI DOT: 03022002 OCA: TESTOCA_____________ OAN: ____________________CGD: ________ HPT: ____________________ HSP: __ BMO: TIGER SHARK_________ BNM: TEST BOAT ENTRY_____ LKI: _________ LKA: ____________________ MIS: TEST MISCELLANEOUS FIELD________________________________________________________________________________________________________________________________________________________________________________ NOA: Y CONTROL FIELD: __________

2.1.2 ADDITIONAL GUIDELINES FOR ENTRY

2.1.2a BOAT REGISTRATION

The Texas Parks and Wildlife Department requests that an agency making a stolen boat entry into TCIC/NCIC 2000 confirm ownership and complete descriptive data. A formal message (TTY) should be sent to the Texas Parks and Wildlife Department in Austin through TLETS at

Revised May, 2002 1 Version 1.1

mnemonic address "PWAZ". When requesting this information, please advise Parks and Wildlife that the data is needed for entry into TCIC/NCIC 2000.2.1.2b OAN FIELD

The Owner Applied Number field (OAN) may not be used by Texas agencies unless the BHN field has been filled. If there is an OAN, but no BHN available, then the OAN must be placed in the BHN field with a notation in the MIS field indicating that the "BHN is an OAN". Texas Users cannot cancel using an OAN.

2.1.2c MODEL NUMBERS, ENGINE NUMBERS, OR MOTOR NUMBERS

Model numbers are not unique. Model numbers should be entered in the BMO field. Model numbers are not to be entered in the BHN and OAN fields of Stolen Boat records.

An engine or motor number should be entered into the OAN field if the BHN field is already filled. In this case, insert the notation "OAN IS A MOTOR NUMBER" or "OAN IS AN ENGINE NUMBER" in the MIS field.

2.1.2d BOAT TRAILERS

Boat trailers stolen in conjunction with a boat should be entered into the Vehicle file(MKE: "EV"). The NIC numbers of both entries should be cross-referenced in the MIS field.

2.2 MODIFY (MB)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

MB MODIFY STOLEN BOAT RECORD ORI: TX DPS0000 SELECT REG: TX1234AB OR BHN: ____________________ OCA: TESTOCA_____________ ENTER NEW DATA BELOW; '*' DELETES OPTIONAL FIELD. MKE: EB- _ ORI: TX _______ REG: ________ RES: __ REY: YYYY HUL: __ PRO: __ BHN: ____________________ BYR: YYYY BMA ________________________ BTY: ___ BLE: 09BCO: WHI/BLU DOT: MMDDYYYY OCA: ____________________ OAN: ____________________CGD: ________ HPT: TEST HOME PORT______ HSP: __ BMO: ____________________ BNM: ____________________ LKI: _________ LKA: ____________________ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ NOA: _ VLN: ______________________________ CONTROL FIELD: __________

2.2.2 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION

For NCIC/TCIC 2000 validation, a Name of Validator (VLN) may be added to a boat record to indicate that the record has met the criteria for validation. When the VLN is entered, TCIC 2000

Revised May, 2002 2 Version 1.1

and NCIC 2000 store the current date in the record as the Date of Last Validation (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected.The acknowledgment for the modification message containing the VLN will indicate the record has been validated. The VLN can be in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc. The NCIC 2000 policy requiring "on-line" validation has been suspended until further notice.

2.3 CANCEL (XB)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE

XB CANCEL STOLEN BOAT RECORD ORI: TX DPS0000 SELECT ONE: REG: TX1234AB OR BHN: ____________________ OCA: TESTOCA_____________ RPP: NOT STOLEN___________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CB' IF BOAT WAS RECOVERED.

2.4 INQUIRY (QB)

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QB BOAT INQUIRY MKE: QB- _ ORI: TX DPS0000 REG: TX1234ZB AND/OR BHN: ____________________ NIC: __________ RELATED SEARCH HIT: _ REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZB' FOR ADMIN/TEST INQUIRY.

Revised May, 2002 3 Version 1.1

2.5 LOCATE (LB)

2.5.1 EXAMPLE OF LOCATE MESSAGE

LB LOCATE STOLEN BOAT RECORD RECOVERING AGENCY'S ORI: TX 0000000 SELECT ONE: REG: TX1234AB OR BHN: ____________________ OCA IN THE RECORD: TESTOCA_____________ DATE OF RECOVERY: 03032002 RECOVERING AGENCY'S CASE NUMBER: LOCATE OCA__________ RPP: HIT STATE 20020302___ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________

2.6 CLEAR (CB)

2.6.1 EXAMPLE OF CLEAR MESSAGE

CB CLEAR STOLEN BOAT RECORD ORI: TX DPS0000 SELECT ONE: REG: TX1234AB OR BHN: ____________________ OCA: TESTOCA_____________ DATE OF RECOVERY: 03022002 IF THE BOAT WAS RECOVERED BY AN AGENCY OTHER THAN THE ENTERING AGENCY, AND THE RECOVERING AGENCY HAS NOT PLACED A LOCATE ON THE RECORD: RECOVERING AGENCY ORI: _________ RECOVERING AGENCY OCA: ____________________ RPP: _____________________ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF BOAT RECOVERED. USE 'XB' TO CANCEL INVALID RECORD.

Revised May, 2002 4 Version 1.1

3. ABANDONED/STORED BOAT TRANSACTIONS

3.1 INTRODUCTION

For TCIC 2000 purposes, an Abandoned/Stored Boat is a boat that is stored on police property or in a licensed storage facility. This a TCIC 2000 only file.

3.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE’s for Abandoned/Stored Boats:

MKE FORMATERB ENTER ABANDONED/STORED BOAT RECORDMRB MODIFY ABANDONED/STORED BOAT RECORDXRB CANCEL ABANDONED/STORED BOAT RECORDQB BOAT INQUIRY (INVESTIGATIVE PURPOSES)ZB BOAT INQUIRY (ADMINISTRATIVE/TEST PURPOSES)

3.3 CRITERIA FOR ENTRY

The Abandoned/Stored Boat file should be used when an agency stores a boat on police property or in a licensed storage facility or when an agency is notified by a licensed storage facility that they have received a boat for storage. Entry of a boat into this file should only be used after a "QB" inquiry produces no records and the registered owner of the boat cannot be contacted. Registered owner information may be obtained from the Texas Parks and Wildlife Department.

When entering boats stored in state-licensed facilities, the license number issued by the Texas Department of Transportation for that facility should be placed in the first nine characters of the miscellaneous field (MIS), for example, 50000VSF. This is the format that the Texas Department of Transportation uses when issuing numbers to the storage facilities.

3.4 RECORD RETENTION

Abandoned/Stored Boat file records remain in TCIC 2000 one year from the date of entry. Agencies are not notified when the records are purged from the file.

Revised May, 2002 5 Version 1.1

3.5 MESSAGE FIELD CODES AND EDITS

For Abandoned/Stored Boats, additional Texas message field codes and edits are as follows:

PND Name of Licensed Storage Facility Must be the NAME of the licensed storage facility, not the phone number, address or VSF number.

3.6 ADDITIONAL MANDATORY FIELDS FOR ENTRY

In addition to the mandatory fields outlined in the NCIC 2000 Operating Manual for boat entries, the PND field is considered mandatory when entering an abandoned/stored boat.

3.7 ENTRY (ERB)

3.7.1 EXAMPLE OF ENTRY MESSAGE

ERB ENTER ABANDONED/STORED BOAT RECORD ORI: TX DPS0000 REG: TX1212AB RES: TX REY: 2002 HUL: PL BHN: KAW1234N567_________ PRO: IN BYR: 2000 BMA: KAW_____________________ BTY: RUN BLE: 20 BCO: BLK/WHI DOR: 03032002 OCA: ERBTEST_____________ PND: TEST POUND NAME_____ OAN: ____________________ LKI: _________ LKA: ____________________ NOA: _ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

3.7.2 ADDITIONAL GUIDELINES FOR ENTRY

3.7.2a BOAT REGISTRATION

The Texas Parks and Wildlife Department requests that an agency making an abandoned/stored boat entry into TCIC 2000 confirm ownership and complete descriptive data. A formal message (TTY) should be sent to the Texas Parks and Wildlife Department in Austin through TLETS at mnemonic address "PWAZ". When requesting this information, please advise Parks and Wildlife that the data is needed for entry into TCIC 2000.

3.7.2b OAN FIELD

Revised May, 2002 6 Version 1.1

The Owner Applied Number field (OAN) may not be used by Texas agencies unless the BHN field has been filled. If there is an OAN, but no BHN available, then the OAN must be placed in the BHN field with a notation in the MIS field indicating that the "BHN is an OAN". Texas Users cannot cancel using an OAN.

3.7.2c ENGINE NUMBERS, OR MOTOR NUMBERS

An engine or motor number may be entered into the OAN field if the BHN field is already filled. In this case, insert the notation "OAN IS A MOTOR NUMBER" or "OAN IS AN ENGINE NUMBER" in the MIS field.

3.7.2d BOAT TRAILERS

Boat trailers recovered in conjunction with an abandoned/stored boat should be entered into the Abandoned/Stored Vehicle file (MKE: "ERV"). The "TIC" numbers of both entries should be cross-referenced in the MIS field.

3.8 MODIFY (MRB)

3.8.1 WHEN TO USE A MODIFICATION MESSAGE

Modification of a record is restricted to the agency that entered the record. A modification message is used to add, delete, or change data in an active Abandoned/Stored Boat record.

3.8.2 EXAMPLE OF MODIFICATION MESSAGE

MRB MODIFY ABANDONED/STORED BOAT RECORD ORI: TX DPS0000 SELECT ONE: REG: TX1212AB OR BHN: ____________________ OCA: ERBTEST_____________ PUT NEW INFORMATION BELOW. USE '*' TO DELETE AN OPTIONAL FIELD ORI: TX _______ REG: __________ RES: __ REY: YYYY HUL: __ BHN: ____________________ PRO: __ BYR: YYYY BMA: PLE_____________________ BTY: ___ BLE: __ BCO: _______ DOR: MMDDYYYY OCA: ERB TEST____________ PND: ____________________ OAN: ____________________ LKI: _________ LKA: ____________________ NOA: Y MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

Revised May, 2002 7 Version 1.1

3.9 CANCEL (XRB)

3.9.1 WHEN TO USE A CANCELLATION MESSAGE

Cancellation is restricted to the agency that entered the record. A cancellation message should be used after ownership has been determined, if the record was entered in error, or the storage facility released the boat.

3.9.2 EXAMPLE OF CANCELLATION MESSAGE

XRB CANCEL ABANDONED/STORED BOAT ORI: TX DPS0000 SELECT ONE: REG: TX1212AB OR BHN: ____________________ OCA: ERB TEST____________ RPP: AUCTION______________ CONTROL FIELD: __________

3.9.3 ADDITIONAL GUIDELINES FOR CANCELLATION

3.9.3a RPP FIELD

When canceling an Abandoned/Stored Boat record from TCIC 2000, users are expected to enter the Reason for Property Record Removal (RPP). Valid values are AUCTION, TITLE TRANSFERRED, OWNER CLAIMED, or OTHER MEANS.

Revised May, 2002 8 Version 1.1

Revised May, 2002 9 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESCOMPUTERIZED CRIMINAL HISTORY (CCH) FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 SYSTEM OVERVIEW 1

2. QH INQUIRY 22.1 QH INQUIRY 2

2.1.1 EXAMPLE OF QH INQUIRY 22.1.2 REQUIREMENTS FOR QH INQUIRY 22.1.3 ADDITIONAL INFORMATION REGARDING TCIC CCH 3

2.1.3a POSSIBLE TCIC RESPONSES TO CCH INQUIRIES 32.1.3b POSSIBLE INFORMATION ON TCIC CCH RESPONSES 4

3. QR INQUIRY 53.1 QR (RAP) INQUIRY 5

3.1.1 QR OVERVIEW 53.1.2 EXAMPLE OF RAP INQUIRY 63.1.3 EXAMPLE OF QR INQUIRY 6

4. DRIVERS OF PUBLIC TRANSPORTATION VEHICLES 74.1 GOVERNMENT CODE 411 74.2 QH-T INQUIRY 7

4.2.1 QH-T OVERVIEW 74.2.2 EXAMPLE OF QRH INQUIRY 8

5. NLETS CCH INQUIRIES 85.1 NLETS CCH INQUIRIES (IQ, FQ, AQ) 8

5.1.1 EXAMPLE OF NLETS CCH INQUIRY (IQ) 85.1.2 EXAMPLE OF NLETS CCH INQUIRY (FQ) 95.1.3 EXAMPLE OF NLETS CCH INQUIRY (AQ) 9

Revised July, 2002 Version 1.2

1. INTRODUCTION

1.1 SYSTEM OVERVIEW

There are three sources of criminal history data available to local agencies via their telecommunications terminal:

1. Texas Computerized Criminal History files (CCH)These are criminal history records mainly associated with arrest events that originated in Texas. Additionally, juvenile records associated with arrest events that occurred on or after January 1, 1996 are also contained in CCH.

2. FBI Interstate Identification Index files (III)The criminal records of over 38 million people are available. These records represent:

All persons born in 1956 or later with a FBI record. Persons born prior to 1956 whose first arrest fingerprint card was submitted to the

FBI on July 1, 1974, or later. Numerous older records converted to the automated system in the Criminal Justice

Information Services Division Manual Conversion Project, as well as certain fugitives and repeat offenders.

3. Records available from other states using NLETS inquiries ("IQ", "FQ", "AQ")These are NLETS formats that allow agencies to inquire directly to another state for criminal history information. These formats should not be used until after the "QH" and "QR" responses are received from the TCIC CCH and NCIC III files.

CCH inquiries by Texas agencies will search the CCH file and then be forwarded to NCIC to search the Interstate Identification Index (III). (When a "T" is placed in the MKE: "QH-T", only the Texas CCH File will be searched.) Thus, an agency will normally receive two responses to a CCH inquiry. The Texas User Specifications Pages describe the Texas CCH files and the formats used to access them.

The Texas CCH file is created from arrest and disposition information submitted by local criminal justice agencies. Submissions include arrest fingerprint cards, prosecutorial and court dispositions, as well as some custody reports from the Department of Criminal Justice. The completeness and accuracy of the records is dependent upon the completeness and accuracy of the information submitted by the local agencies. Local agencies can only inquire into the CCH files; they cannot directly enter, modify, cancel or clear records contained in CCH.

Criminal history information obtained from the Texas CCH or FBI III files is confidential and subject to restrictions on the use and dissemination, as described in this part of the manual. Effective September 1, 1997, Government Code 411.135 provides citizens access to Texas only conviction and deferred adjudication records of an offender; however, this pertains to records obtained directly from the DPS, not from local agencies using TLETS.

Revised July, 2002 1 Version 1.2

There are many non-criminal justice agencies that are authorized by statute to receive Texas CCH data. These non-criminal justice agencies must obtain this information directly from the Crime Records Service and not through a local law enforcement agency over TLETS, with the exception of checks performed for certain Drivers of Public Transportation Vehicles.

Refer all questions concerning the Texas CCH file and III to the TCIC Control Section of the Crime Records Service at mnemonic address "CRDP", by telephone at (512) 424-2088or toll-free at 1-866-266-TCIC (8242).

2. QH INQUIRY

2.1 QH INQUIRY

2.1.1 EXAMPLE OF QH INQUIRY

QH CRIMINAL HISTORY/IDENTIFICATION INQUIRY MKE: QH- _ ORI: TX DPS0000 PUR: C REQ: TITLE FIRSTNAME LASTNAME______ OPR: FIRSTNAME LASTNAME____________ CHOOSE ONE OF THE FOLLOWING SETS OF IDENTIFIERS: 1. NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 01011962 2. NAM: ______________________________ MNU: __ - ____________ 3. NAM: ______________________________ SOC: _________ 4. SID: __________ *** NOTICE *** FOR SANCTIONS RELATED TO MISUSE OF 5. FBI: _________ CRIMINAL HISTORY RECORD INFORMATION CONTROL FIELD: _____ EFFECTIVE SEPT. 1, 1993, PRESS F1.

2.1.2 REQUIREMENTS FOR QH INQUIRY

ORI: The ORI field must be filled, it will not default. If the requestor is from another agency, that agency's ORI is to be used. If a terminal agency is not authorized to use the other agency's ORI, include that agency's name in the REQ field, in addition to the requestor's identifying information.

PUR: Valid values in the PUR field are: C, J, H or D.

PUR: C – Criminal Justice Purposes

PUR: J – Criminal Justice Employment Purposes

PUR: H – Background Checks on certain Drivers of Public Transportation Vehicles.(If using PUR: H, the Message Key must be MKE: "QH-T".)

PUR: D – Domestic Violence and Stalking Purposes. (Restricted to use by civil or criminal courts only; ORI must end with letter "J".)

Revised July, 2002 2 Version 1.2

REQ: The REQ must identify the person who has requested the inquiry. That is often the officer or investigator who has asked for the inquiry, but it can also be any authorized person who has requested the inquiry. This person must be uniquely identified. This should be the person's name. A number can be used only if it is unique and will stay unique, not the unit number, for example, since it will change. If the requestor is not an employee of the department indicated in the ORI field, then the requestor's department name must also be indicated. For example, REQ: TRPR JOHN JONES/THP BASTROP or REQ: JANICE THOMAS CSCD BRYAN.

ATN: The same rules apply as for REQ shown above.

OPR: The OPR field must uniquely identify the operator of the TLETS telecommunications terminal who performed the inquiry transaction. This should be the operator's name.

SUBJECT IDENTIFIERS:

Note that there are five different sets of identifiers that can be used to inquire into Texas CCH. One set of identifiers must be chosen. To inquire by Name, Sex, Race, Date of Birth and Social Security number: run one "QH" format with NAM, SEX, RAC and DOB (line #1), then run a second "QH" inquiry with NAM and SOC (line #3).

Using name, sex, race and date of birth (line #1) will return any records in CCH based on the Soundex System as follows: Complete name; Black (B) searches all races except White (W), and White (W) searches all races except Black (B); and, same year of birth. The other four options will only return records that match the numeric identifier used (MNU, SOC, SID AND FBI). The name in line #2 and line #3 is for administrative purposes only and does not affect the search.

Operators must review the "QH" return carefully to compare all identifiers in the record with the identifiers of the person in question. Because of the soundex system, the TCIC 2000 and NCIC 2000 systems will provide hits on subjects who are not the same as the person stated in the inquiry. Additionally, CCH and III use different soundex routines that can result in different name based responses from the two different systems. It is the inquiring agency's responsibility to insure that the return received is for the person whose record was requested. Compare all the identifiers in the record. All returns over the telecommunications system are considered possible identifications only. Conclusive identification is possible only by fingerprint comparison.

2.1.3 ADDITIONAL INFORMATION REGARDING TCIC CCH

2.1.3a POSSIBLE TCIC RESPONSES TO CCH INQUIRIES

There are five different responses that an agency may receive from TCIC in response to a "QH" or "QH-T" inquiry.

1. Complete Record Summary. The inquiry identifiers matched one record on file and that record is returned. It is the responsibility of the inquiring agency to read the return carefully to see if it is a good identification for the subject inquired upon. The record is in summary form.

Revised July, 2002 3 Version 1.2

2. No Record. The inquiry identifiers could not be matched to any records. (Note: It is possible the subject has a record under other identifiers. A fingerprint search is necessary for conclusive results.)

3. Complete Record Not Computerized. The inquiry identifiers matched one record on file, but that record is not completely computerized (the identification information is entered into the computer, but not the arrest information.) The response displays the identification segment for that record with a note at the bottom that states, "COMPLETE RECORD NOT COMPUTERIZED/ASK CRS FOR MANUAL CHECK".

It is the responsibility of the inquiring agency to read the return carefully to be sure that it is a good identification for the subject inquired upon. If the agency then wants to see the record information for that subject, a manual search must be requested from CRS. The "MCCH" transaction is used for this request. Manual searches of the criminal history files are available 24-hours a day.

4. More than Five Possible Hits. The identifiers of the inquiry matched more than five recordsin the CCH files. Rather than send this many records to the agency on-line, TCIC returns a message that states "MORE THAN 5 POSSIBLE TCIC HITS—REQ MANUAL SEARCH". The "MCCH" transaction is used for this request. Manual searches of the criminal history files are available 24-hours a day.

It is possible that CRS will not find a record for the subject of the inquiry. Just because there are more than five possibilities does not mean there is a good match.

5. From Two to Five Possible Hits. If the identifiers in the inquiry match between two and five records in CCH, identification information on the matching records will be sent to the inquiring agency. It is the responsibility of the inquiring agency to look through the possibilities and determine whether any are a good identification for the subject in question. If any are determined to be a good match, perform the "QH" transaction by SID.

If no match is found among the records returned, then the subject of the inquiry is considered to have no record.

2.1.3b POSSIBLE INFORMATION ON TCIC CCH RESPONSES

1. If a caveat above the NAME field indicates "SUBJECT IS DECEASED", the Date of Death (DOD) will be displayed in the Identification Comments field in the following format DODMMDDYYYY.

2. If a caveat stating "SUBJECT IS REGISTERED AS A SEX OFFENDER" appears below the header, the Sex Offender file record may be obtained using transaction code "QXS". However, not all sex offenders will have a complete CCH record. The fact that an individual has a Texas SID number does not mean they have a complete Texas CCH record. When a registered sex offender moves to Texas from another state, the sex offender is assigned a Texas SID number based upon fingerprints.

Revised July, 2002 4 Version 1.2

3. III M/S or III S/S. These abbreviations will appear under the DRE (Date Record Entered) and DLU (Date of Last Update) in the return when the subject's record is indexed in the Interstate Identification Index (III). Not all Texas CCH records are indexed in III. "M/S" (Multi-State) indicates that III shows a record for the subject in at least one other state in addition to the record in Texas. "S/S" (Single-State) indicates that III has only the Texas CCH record for the subject.

4. S/S SUB – NO NCIC RESPONSE. This notation at the bottom of a "QH" return indicates a "Single State Subject". Since the Texas CCH record is the only record for the subject in III, no III response will be sent to the inquiring Texas agency.

5. Automated responses from the Texas CCH file to "QH" and "QH-T" inquiries are arrest summaries only. Only the broad categories of offenses for which the subjects were arrested are indicated, not the specific charges. In addition, the only dispositions shown are convictions. Complete transcripts with specific arrest and disposition information are available from the Crime Records Service.

Make requests by letter to the address below, by TLETS administrative message to mnemonic address “CRDP” or by fax at (512) 424-2961. All requests must identify the subject by name, sex, race, date of birth and SID. Include the requesting agency’s name, ORI, name of person that the response will be mailed to, mailing address, and state clearly in the letter, message or fax that the request is for a complete transcript.

Texas Department of Public Safety Crime Records Service Attn: Correspondence P O Box 4143 Austin, Texas 78765-4143

6. Automated responses from the Texas CCH file to "QH-T" inquiries with PUR/H will provide identifiers only. It will then be necessary to re-inquire using transaction code "QRH" to receive conviction data on "drivers of public transportation vehicles".

3. QR INQUIRY

3.1 QR (RAP) INQUIRY

3.1.1 QR OVERVIEW

In addition to the record summary available from Texas CCH with the "QH" inquiry, a complete record (rap sheet) is available to authorized terminals. Authorized terminals must use transaction code "RAP". If just the Texas transcript is desired, place a "T" in the message key of the "RAP" format. With the "QR-T" message key, only a Texas CCH transcript will be received. If the subject has record information available in NCIC, then do not place a "T" in the message key. (Note: Although the Texas SID is being used, a reply from III participants will be received.)

Revised July, 2002 5 Version 1.2

The "QR" format is also available to authorized terminals to receive a complete record. This format allows an inquiry into the Texas CCH and NCIC 2000 III files using the subject’s FBI number only.

3.1.2 EXAMPLE OF RAP INQUIRY

RAP REQUEST FOR TCIC RAP SHEET AND NCIC III RECORD MKE: QR- _ ORI: TX DPS0000 SID: TX0 1234567 OR FBI: _________ PUR: C ATN: TITLE FIRSTNAME LASTNAME______ CONTROL FIELD: _____ *** NOTE *** ENTER ONLY ONE IDENTIFIER: SID OR ELSE FBI NUMBER. *** NOTICE *** FOR NEW SANCTIONS RELATED TO MISUSE OF CRIMINAL HISTORY RECORD INFORMATION EFFECTIVE SEPT. 1, 1993, PRESS PF1 (HELP FILES).

3.1.3 EXAMPLE OF QR INQUIRY

QR NCIC INTERSTATE IDENTIFICATION INDEX RECORD REQUEST ORI: TX DPS0000 FBI: 9005001__ PUR: C ATN: TITLE FIRSTNAME LAST NAME_____ CONTROL FIELD: _____ *** NOTICE *** FOR NEW SANCTIONS RELATED TO MISUSE OF CRIMINAL HISTORY RECORD INFORMATION EFFECTIVE SEPT. 1, 1993, PRESS PF1 (HELP FILES).

Revised July, 2002 6 Version 1.2

4. DRIVERS OF PUBLIC TRANSPORTATION VEHICLES

4.1 GOVERNMENT CODE 411

GC 411.124 ACCESS TO CRIMINAL HISTORY RECORD INFORMATION: POLITICAL SUBDIVISIONS; PUBLIC TRANSPORTATION DRIVERS. A political subdivision of this state that employs, licenses, or regulates drivers of public transportation vehicles is entitled to obtain from the department or from a law enforcement agency of the political subdivision with access to the information the criminal history record information maintained by the department that relates to a person who is: 1) the driver of a public transportation vehicle; and 2) employed, licensed or regulated by the political subdivision. A municipality is entitled to obtain only criminal history record information that relates to a conviction of the person.

GC 411.097 ACCESS TO CRIMINAL HISTORY RECORD INFORMATION FOR: SCHOOL DISTRICTS, CHARTER SCHOOLS, PRIVATE SCHOOLS, REGIONAL EDUCATION SERVICE CENTERS, COMMERCIAL TRANSPORTATION COMPANIES OR EDUCATION SHARED SERVICE ARRANGEMENTS.

An employee of or an applicant for employment with a public or commercial transportation company that contracts with the district, school, service center, or shared services arrangement to provide transportation services shall obtain criminal history record information from the Texas Department of Public Safety, Crime Records Service. Law enforcement agencies may not release or disclose criminal history information to these entities.

4.2 QH-T INQUIRY

4.2.1 QH-T OVERVIEW

Criminal history inquiries made in accordance with GC 411.124 must be searched with transaction code "QH" by placing a "T" in the Message Key (MKE: "QH-T") field and an "H" in the Purpose Code (PUR: H) field. After the SID number has been obtained, inquire using transaction code "QRH" to acquire conviction data. This statute applies to municipal bus and taxi drivers. NCIC 2000 III cannot be given to any non-criminal justice agency and cannot be used for any non-criminal justice purposes; there are no exceptions.

Revised July, 2002 7 Version 1.2

4.2.2 EXAMPLE OF QRH INQUIRY

QRH INQUIRY ON TCIC CONVICTION RECORD – PUBLIC TRANSPORTATION DRIVERS MKE: QR- T ORI: TX DPS0000 SID:TX0 1234578 PUR:H ATN: TITLE FIRSTNAME LASTNAME______ CONTROL FIELD: _____ THIS FORMAT MAY BE USED ONLY IN ACCORDANCE WITH TEXAS GOVERNMENT CODE 411.124, WHICH ALLOWS LOCAL LAW ENFORCEMENT AGENCIES TO PROVIDE RECORD-OF-CONVICTION DATA TO POLITICAL SUBDIVISIONS THAT EITHER EMPLOY OR HAVE THE DUTY AND RESPONSIBILITY OF LICENSING AND REGULATING DRIVERS OF PUBLIC TRANSPORTATION VEHICLES.

5. NLETS CCH INQUIRIES

5.1 NLETS CCH INQUIRIES (IQ, FQ, AQ)

5.1.1 EXAMPLE OF NLETS CCH INQUIRY (IQ)

IQ NLETS CHRI IDENTITY INQUIRY TO DESTINATION STATE(S): AZ __ __ __ __ PUR: C ATN: TITLE FIRSTNAME LASTNAME______ USE: NAM: TEST,RECORD___________________ DOB: 01011966 SEX: M RAC: W OR SELECT OPTION: MNU: _______________ SOC: _________ CONTROL FIELD: __________

Revised July, 2002 8 Version 1.2

5.1.2 EXAMPLE OF NLETS CCH INQUIRY (FQ)

FQ NLETS CHRI FULL RECORD INQUIRY TO DESTINATION STATE: AZ PUR: C ATN: TITLE FIRSTNAME LASTNAME______ SID: AZ12345678 DPT: ______________________________ BLD: ______________________________ ADR: ______________________________ CIS: ______________________________ ZIP: _________ CONTROL FIELD: __________

5.1.3 EXAMPLE OF NLETS CCH INQUIRY (AQ)

AQ NLETS CHRI ADDITIONAL INFORMATION INQUIRY TO DESTINATION(S): AZ_______ _________ _________ _________ _________ PRINT MESSAGE: Y (Y/N) PUR: C ATN: TITLE FIRSTNAME LASTNAME______ CONTROL FIELD: __________ REQUEST COMPLETE CRIMINAL HISTORY TRANSCRIPT BE MAILED ON SUBJECT_____TEST,RECORD M/U DOB/01011966 SID/AZ12345678____________________________________MAIL TRANSCRIPT TO REQUESTING AGENCY NAME REQUESTING AGENCY ADDRESS CITY STATE ZIP CODE ATTN REQUESTORS NAME______________________________________________________________________________________________________________________________________________________________________________________________

Revised July, 2002 9 Version 1.2

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESCONCEALED HANDGUN LICENSE FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 SYSTEM OVERVIEW 11.2 TCIC 2000 ONLY TRANSACTIONS 1

2. QGL INQUIRY 12.1 EXAMPLE OF QGL INQUIRY 12.2 REQUIREMENTS FOR QGL INQUIRY 2

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Concealed Handgun License File document the data field specifications.

1.1 SYSTEM OVERVIEW

TCIC 2000 maintains a file of those individuals who are licensed to carry a concealed handgun under the State's Concealed Handgun Law. This file is searched in response to a wanted person inquiry (transaction code "QW" or "ZW"). The Concealed Handgun File can also be queried by using transaction code "QGL".

For further information regarding the Texas Concealed Handgun Program, contact the Concealed Handgun Section by phone at (512) 424-7293 or (512) 424-7294, toll free at 1-800-224-5744 or via e-mail at [email protected]. Information regarding Concealed Handgun License information may also be obtained from the Texas Department of Public Safety’s web site at www.txdps.state.tx.us.

1.2 TCIC 2000 ONLY TRANSACTIONS

MKE FORMATQGL CONCEALED HANDGUN LICENSE INQUIRY

2. QGL INQUIRY

2.1 EXAMPLE OF QGL INQUIRY

QGL CONCEALED HANDGUN LICENSE INQUIRY MKE: QGL- _ ORI: TX DPS0000 GLN: 12345678 OLN/TID: ________ SOC: _________ NAM: ______________________________ SEX: _ RAC: _ DOB: MM / DD / YYYY CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY.

Revised May, 2002 1 Version 1.1

2.2 REQUIREMENTS FOR QGL INQUIRY

MKE: Message Key. Place the letter "X" for inquiries that contain an exact match on the DOB.

GLN: Gun License Number

OLN/TID: Driver’s License Number or Texas Identification Number

SOC: Social Security Number

NAM, SEX, RAC and DOB: Name, Sex, Race and Date of Birth. An inquiry made with MKE: "QGL-X", will return records that contain an exact match on the DOB. An inquiry made without the "X" will return all records that match the name, sex, race, and year of birth.

Inquiries may be made with one, more than one or all numeric identifiers (GLN, OLN/TID orSOC). Inquiries made by NAM must also include SEX, RAC, and DOB.

Revised May, 2002 2 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESINDIVIDUAL IDENTITY FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 INDIVIDUAL IDENTITY FILE OVERVIEW 11.2 CRITERIA FOR ENTRY 11.3 ADDITIONAL GUIDELINES FOR THE INDIVIDUAL IDENTITY FILE 1

1.3.1 SUBMITTING A SIGNED DECLARATION 11.4 TCIC 2000 ONLY TRANSACTIONS 21.5 RECORD RETENTION 2

2. INDIVIDUAL IDENTITY RECORD TRANSACTIONS 22.1 ENTRY (EIR) 2

2.1.1 EXAMPLE OF ENTRY MESSAGE 22.1.2 MANDATORY FIELDS FOR ENTRY 32.1.3 ADDITIONAL GUIDELINES FOR ENTRY 3

2.1.3a SUBJECT IDENTIFIERS 32.1.3b PASSWORD 3

2.2 MODIFY (MIR) 32.2.1 EXAMPLE OF MODIFICATION MESSAGE 3

2.3 CANCEL (XIR) 42.3.1 EXAMPLE OF CANCELLATION MESSAGE 4

2.4 INQUIRY (QW or ZW) 42.4.1 EXAMPLE OF INQUIRY MESSAGE 42.4.2 EXAMPLE OF INDIVIDUAL IDENTITY

RECORD RESPONSE FROM TCIC 2000 53. STATUTORY REFERENCES 6

3.1 TEXAS GOVERNMENT CODE §411.0421 63.2 CODE OF CRIMINAL PROCEDURE 6

4. SAMPLE DECLARATION OF INDIVIDUAL IDENTITY MISUSE 7

Revised July, 2002 Version 1.2

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Individual Identity File document the data field specifications.

1.1 INDIVIDUAL IDENTITY FILE OVERVIEW

In accordance with House Bill 153, effective September 1, 1999, this file was created to establish a procedure to prevent the fraudulent use of an individual’s identity in circumstances affecting proper law enforcement and to assist law enforcement agencies in verifying that an individual’s identity has been used by another person. This is a TCIC 2000 only file. A record in this file will be returned in response to a Persons inquiry ("QW" or "ZW").

1.2 CRITERIA FOR ENTRY

A record may be entered into this file once the following criteria has been met:

1. An individual must contact the local Sheriff’s Office to make a report that his/her identity has been stolen.

2. The Sheriff's Office is responsible for taking the individual's fingerprints and submitting them to the Department for verification. Agencies with LiveScan may run a TFLU inquiry to verify the individual's identity. After fingerprint verification, notification of the person's identity is sent from DPS (via teletype) to the Sheriff's Office.

3. If the Sheriff and prosecuting attorney determine that the individual's identity has truly been misused, a declaration is signed by the complainant, prosecutor and Sheriff stating that the individual making the report has had his/her identity used fraudulently by another person without consent. The declaration must include the individual’s name, Sex, Race, Date of Birth, Height, Weight, Hair Color, Date of Report, Social Security Number, Drivers License Number, Originating Agency Case Number, Agency ORI, and a unique password. (A sample declaration may be found at the end of this section of the Texas User Specification Pages.)

1.3 ADDITIONAL GUIDELINES FOR THE INDIVIDUAL IDENTITY FILE

1.3.1 SUBMITTING A SIGNED DECLARATION

The Sheriff's Office makes an entry into TCIC 2000 using the transaction code "EIR" and, at the same time, mails a copy of the signed declaration to the following address:

Texas Department of Public SafetyCrime Records Service – MSC 0230ATTN: Error ResolutionP O Box 4143Austin, Texas 78765-4143

Revised July, 2002 1 Version 1.2

Upon receipt of the declaration, DPS will verify that the Individual Identity Record has been entered in TCIC 2000 and then create a corresponding CCH record. One of two record types will be created. One if the individual does not have an existing CCH record, and another when a CCH record already exists.

Once the process is completed, the entire file will be retained in the TCIC Control Room. Questions regarding entry or use of this file may be directed to the TCIC Control Room at(512) 424-2088, 1-866-266-TCIC (8242) or mnemonic address "CRDP".

1.4 TCIC 2000 ONLY TRANSACTIONS

MKE FORMATEIR ENTER INDIVIDUAL IDENTITY INTO TCIC 2000MIR MODIFY INDIVIDUAL IDENTITY INTO TCIC 2000XIR CANCEL TEXAS INDIVIDUAL IDENTITY RECORDQW PERSONS INQUIRY (INVESTIGATIVE PURPOSES)ZW PERSONS INQUIRY (ADMINSTRATIVE/TEST PURPOSES)

1.5 RECORD RETENTION

Records entered into this file will remain in TCIC 2000 indefinitely or until action is taken by the entering agency to remove the record.

2. INDIVIDUAL IDENTITY RECORD TRANSACTIONS

2.1 ENTRY (EIR)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EIR ENTER INDIVIDUAL IDENTITY RECORD INTO TCIC ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: W POB: TX DOB: 01011961 HGT: 601 WGT: 160 EYE: BLU HAI: BRO SKN: FAR SMT: TAT R SHLD FPC: ____________________ MNU: PI - 01234567____ SOC: 555555555 OLN: 12345678____________ OLS: TX OLY: 2007 DOR: 03122002 OCA: TEST OCA____________ PAS: THIS IS A TEST PASSWORD_______ MIS: TEST MISCELLANEOUS FIELD____________________________________________________________________________________________________________________________________________________________________________ NOA: _ CONTROL FIELD: __________

Revised July, 2002 2 Version 1.2

2.1.2 MANDATORY FIELDS FOR ENTRY

The following fields are mandatory for an Individual Identity Record to be accepted byTCIC 2000: Originating Agency Identifier (ORI), Name (NAM), Sex (SEX), Race (RAC), Date of Birth (DOB), Height (HGT), Weight (WGT), Hair (HAI), Date of Report (DOR), Originating Agency Case Number (OCA) and Password (PAS).

2.1.3 ADDITIONAL GUIDELINES FOR ENTRY

2.1.3a SUBJECT IDENTIFIERS

The subject identifier fields found in the Enter Individual Identity Record (transaction code "EIR") are the same as those for a Wanted Person entry format (transaction code "EW" or "EE"). Applicable coding may be found in the Personal Descriptors section of the NCIC 2000 Code Manual.

2.1.3b PASSWORD

The individual whose identity has been used by another person specifies the password (PAS). The password is used for identity verification and may be a maximum of thirty (30) alpha and/or numeric characters. The password may contain spaces but no other special characters, such as a hyphen, are allowed. Examples include but are not limited to a word, phrase, sentence, etc. The password will appear as a caveat in the top portion of the response from TCIC 2000.

2.2 MODIFY (MIR)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

MIR MODIFY INDIVIDUAL IDENTITY RECORD INTO TCIC ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ PUT NEW INFORMATION BELOW. USE '*' TO DELETE AN OPTIONAL FIELD. ORI: TX _______ NAM: ______________________________ SEX: _ RAC: _ POB: __ DOB: 01011962 HGT: ___ WGT: ___ EYE: ___ HAI: ___ SKN: ___ SMT: __________ FPC: ____________________ MNU: __ - ____________ SOC: _________ OLN: ____________________ OLS: __ OLY: YYYY DOR: MMDDYYYY OCA: ____________________ PAS: ______________________________ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ NOA: _ CONTROL FIELD: __________

Revised July, 2002 3 Version 1.2

2.3 CANCEL (XIR)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE

XIR CANCEL TEXAS INDIVIDUAL IDENTITY RECORD ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE AN INVALID RECORD.

2.4 INQUIRY (QW or ZW)

A record in the Individual Identity File will be returned in response to a Persons Inquiry (transaction code "QW" or "ZW").

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QW PERSONS INQUIRY MKE: QW- _ ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 01011965 FBI: _________ SOC: _________ OLN: ____________________ MNU: __ - ____________LIC: __________ LIS: __ VIN: ____________________ VMA: ________________________OCA: ____________________ NIC: __________ RELATED SEARCH HIT: _ EXPANDED NAME SEARCH: _ REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZW' FOR ADMIN/TEST INQUIRY.

Revised July, 2002 4 Version 1.2

2.4.2 EXAMPLE OF INDIVIDUAL IDENTITY RECORD RESPONSE FROM TCIC 2000

***** WARNING - THE IDENTITY INFORMATION IN THIS RECORD TIC/TI1234567890 IS REPORTED TO BE USED FRAUDULENTLY BY OTHER PERSONS. USE CAUTION WHEN VERIFYING THE IDENTITY OF THIS PERSON. THE PASSWORD BELOW IS TO BE USED FOR IDENTITY VERIFICATION. THIS PASSWORD WAS DESIGNATED BY THE PERSON WHO FILED THE REPORT. *ID5432* MKE/INDIVIDUAL IDENTITY RECORD ORI/TXDPS0000 NAM/TEST,RECORD SEX/M RAC/W POB/TX DOB/19650101 HGT/601 WGT/160 EYE/BLU HAI/BRO SKN/FAR SMT/TAT R SHLD MNU/PI-01234567 SOC/555555555 OLN/12345678 OLS/TX OLY/2007 OCA/TEST OCA MIS/THIS IS A TEST ENTRY ONLY TIC/TI1234567890 DTE/20020715 0841 ORI IS DPS COMMUNICATIONS HEADQUARTERS AUSTIN 512 424-2277 **THIS MESSAGE IS FROM THE TCIC 2000 SYSTEM.**

Revised July, 2002 5 Version 1.2

3. STATUTORY REFERENCES

3.1 TEXAS GOVERNMENT CODE §411.0421

§ 411.0421 Information Regarding Fraudulent Use of Identification(a) The department shall create a record of each individual who:(1) in conjunction with the attorney representing the state in the prosecution of felonies in the county in which the individual resides and the sheriff of that county or, if the individual is not a resident of a county in this state, the attorney and sheriff in a county that the individual frequents, signs a declaration that the individual's identity has been used by another person to frustrate proper law enforcement without the individual's consent; and(2) files that declaration with the department.(b) A declaration filed under this section must include:(1) the individual's name, social security number, driver's license number, date of birth, and other identifying data requested by the department;(2) a statement that the individual's name, social security number, driver's license number, date of birth, or other data has been used by another person to frustrate proper law enforcement; and(3) a name, word, number, letter, or combination of 30 or fewer characters designated by the individual as a unique password to verify the individual's identity.(c) On receipt of a declaration under this section, the department shall create a record of the individual's identity, including a record of the individual's unique password, in the criminal history record information maintained by the department under Subchapter F. The department shall ensure that this record, including the unique password, is available online to any criminal justice agency authorized to receive information from the department under Subchapter F.Added by Acts 1999, 76th Leg., ch. 1334, § 1, eff. Sept. 1, 1999.

3.2 CODE OF CRIMINAL PROCEDURE

Art. 60.20 Information Related to Non-Fingerprint Supported ActionsOn receipt of a report of prosecution or court disposition information from a jurisdiction for which corresponding arrest data does not exist in the computerized criminal history system, the Department of Public Safety shall enter the report into a non-fingerprint supported file that is separate from the computerized criminal history system. The department shall grant access to records in the non-fingerprint supported file that include the subject's name or other identifier in the same manner as the department is required to grant access to criminal history record information under Subchapter F, Chapter 411, Government Code. On receipt of a report of arrest information that corresponds to a record in the non-fingerprint supported file, the department shall transfer the record from the non-fingerprint supported file to the computerized criminal history system.Added by Acts 2001, 77th Leg., ch. 474, § 2, eff. Sept. 1, 2001.

Revised July, 2002 6 Version 1.2

4. SAMPLE DECLARATION OF INDIVIDUAL IDENTITY MISUSE

ORI ________________________NAME ______________________________________________________________SEX _________________ RACE ___________________________DATE OF BIRTH _____________________ HGT ______ WGT __________HAIR _____ DATE OF REPORT ____________ OCA ________________SOCIAL SECURITY NUMBER _________________________________________DRIVER LICENSE NUMBER ____________________DL STATE ________ DL EXP ________________

UNIQUE PASSWORD (alpha/numeric combination of 30 characters or less)

______________________________

Optional FieldsPOB______ SMT_____________________________________________________

This declaration has been filed, in conjunction with Chapter 411, Texas Government Code, Section §411.0421 as a result of the above named individual’s identity being used by another person to frustrate proper law enforcement without their consent.

_______________________________________________________________________Complainant Signature Date

_______________________________________________________________________District/County Attorney Signature Date

_______________________________________________________________________Sheriff Signature Agency ORI Date

Please mail to:Texas Department of Public SafetyCrime Records Service – MSC 0230ATTN: Error ResolutionP.O. Box 4143Austin, Texas 78765-4143

Revised July, 2002 7 Version 1.2

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESINTERESTED AGENCY FLAG TRANSACTIONS

TABLE OF CONTENTS

1. INTRODUCTION 11.1 INTERESTED AGENCY FLAG OVERVIEW 11.2 CRITERIA FOR ENTRY 11.3 TCIC 2000 ONLY TRANSACTIONS 1

2. INTERESTED AGENCY RECORD TRANSACTIONS 12.1 ENTRY (EIA) 1

2.1.1 EXAMPLE OF ENTRY MESSAGE 12.1.2 MANDATORY FIELDS FOR ENTRY 22.1.3 ADDITIONAL GUIDELINES FOR ENTRY 2

2.1.3a NOTIFICATION 22.2 CANCEL (XIA) 2

2.2.1 EXAMPLE OF CANCELLATION MESSAGE 2

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Interested Agency Flag transactions document the data field specifications.

1.1 INTERESTED AGENCY FLAG OVERVIEW

This transaction capability was created to establish a procedure to "flag" a record maintained in TCIC 2000 when a Texas law enforcement agency (who is not the entering agency) has an interest in another Texas law enforcement agency's record. For example, a Sheriff's Office enters a warrant for a person wanted in connection with a police department's case. The warrant could be canceled or served without the Police Department being aware. With the "Interested Agency" flag, TCIC 2000 will notify the police department whenever a transaction occurs against the record. This is a TCIC 2000 only file. Only records maintained in TCIC 2000 will be flagged. An interested agency flag record cannot be modified. If an error is made in an interested agency flag record, the record must be canceled (transaction code "XIA") and then re-entered.

1.2 CRITERIA FOR ENTRY

Any record entered in TCIC 2000 may have an "Interested Agency" flag placed on it. A record to be flagged must be identified by TCIC number (TIC) and Originating Agency Case Number (OCA). This flag may only be used for official criminal justice purposes.

1.3 TCIC 2000 ONLY TRANSACTIONS MKE FORMATEIA ENTER INTERESTED AGENCY FLAG RECORDXIA CANCEL INTERESTED AGENCY FLAG RECORD

2. INTERESTED AGENCY RECORD TRANSACTIONS

2.1 ENTRY (EIA)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EIA ENTER INTERESTED AGENCY RECORD ORI: TX 0000000 ENTER RECORD TO BE TAGGED: TIC: TV0123456789 OCA: 123TEST_____________ ENTER INTERESTED AGENCY INFORMATION BELOW: MNEMONIC: XXXZ ORI: TX 0000000 ATN: DETECTIVE JOE SMITH___________ SECONDARY TERMINAL ID: XXXP______ REASON FOR INTEREST: MURDER INVESTIGATION_________________________ NOTIFICATION: INQUIRY ONLY X ALL TRANSACTIONS: _ CONTROL FIELD: __________

Revised May, 2002 1 Version 1.1

2.1.2 MANDATORY FIELDS FOR ENTRY

The following fields are mandatory for an interested agency record to be accepted by TCIC 2000: Originating Agency Identifier (ORI), TCIC Number (TIC), Originating Agency Case Number (OCA), Mnemonic, Interested Agency Identifier (ORI), Attention (ATN), Reason for Interest, and Notification (Inquiry Only or All Transactions).

2.1.3 ADDITIONAL GUIDELINES FOR ENTRY

2.1.3a NOTIFICATION

When entering an interested agency record into TCIC 2000, the agency placing the flag must indicate whether they want to be notified only when an inquiry is made on the record or when all transactions are performed against the record. Place an "X" in the field that corresponds to the appropriate notification. The interested agency will be automatically notified by teletype to the mnemonic entered in the record when a transaction is performed against the record. The TCIC Control Room also gets an exact duplicate of each notification.

2.2 CANCEL (XIA)

2.2.1 EXAMPLE OF CANCELLATION MESSAGE (XIA)

XIA CANCEL INTERESTED AGENCY RECORD ORI: TX 0000000 ENTER RECORD TO BE TAGGED: TIC: TV0123456789 OCA: 123TEST_____________ ENTER INTERESTED AGENCY INFORMATION BELOW: MNEMONIC: XXXZ ORI: TX 0000000 ATN: DETECTIVE JOE SMITH___________ SECONDARY TERMINAL ID: __________ CONTROL FIELD: __________

Revised May, 2002 2 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESLICENSE PLATE FILETABLE OF CONTENTS

1. INTRODUCTION 11.1 MESSAGE KEY (MKE) CODES 11.2 NCIC TRANSACTIONS WITH ADDITIONAL TCIC SPECIFICATIONS 1

2. STOLEN LICENSE PLATE TRANSACTIONS 12.1 ENTRY (EL) 1

2.1.1 EXAMPLE OF ENTRY MESSAGE 12.1.2 ADDITIONAL GUIDELINES FOR ENTRY 2

2.1.2a TEXAS APPORTIONED/DEALER LICENSE PLATES 22.1.2b MISCELLANEOUS (MIS) FIELD 2

2.2 MODIFY (ML) 22.2.1 EXAMPLE OF MODIFICATION MESSAGE 22.2.2 VALIDATION GUIDELINES

FOR NCIC/TCIC 2000 MODIFICATION 32.3 CANCEL (XL) 3

2.3.1 EXAMPLE OF CANCELLATION MESSAGE 32.4 INQUIRY (QV) 3

2.4.1 EXAMPLE OF INQUIRY MESSAGE 32.4.2 REQUIREMENTS FOR INQUIRY 42.4.3 ADDITIONAL MESSAGE FIELD CODES FOR INQUIRY 42.4.4 ADDITIONAL GUIDELINES FOR INQUIRY 4

2.4.4a H.E.A.T. DECAL 42.5 LOCATE (LL) 4

2.5.1 EXAMPLE OF LOCATE MESSAGE 42.6 CLEAR (CL) 5

2.6.1 EXAMPLE OF CLEAR MESSAGE 5

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Stolen License Plate File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the Stolen License Plate File:

MKE FORMATEL ENTER STOLEN LICENSE PLATEML MODIFY STOLEN LICENSE PLATE RECORDXL CANCEL STOLEN LICENSE PLATE RECORDLL LOCATE STOLEN LICENSE PLATE RECORDCL CLEAR STOLEN LICENSE PLATE RECORD

1.2 NCIC TRANSACTIONS WITH ADDITIONAL TCIC SPECIFICATIONS

MKE FORMATQV QUERY VEHICLE (INVESTIGATIVE PURPOSES)ZV QUERY VEHICLE (ADMINISTRATIVE/TEST PURPOSES)

2. STOLEN LICENSE PLATE TRANSACTIONS

2.1 ENTRY (EL)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EL ENTER STOLEN LICENSE PLATE MKE: EL- _ ORI: TX DPS0000 LIC: ABC123____ LIS: TX LIY: 2002 LIT: PC DOT: 02042002 OCA: TEST123_____________ LKI: _________ LKA: ____________________ MIS: FRONT PLATE___________________________________________________________________________________________________________________________________________________________________________________________ NOA: Y CONTROL FIELD: __________

Revised May, 2002 1 Version 1.1

2.1.2 ADDITIONAL GUIDELINES FOR ENTRY

In addition to the information outlined in the NCIC 2000 Operating Manual, License Plate File, page 8, regarding additional guidelines for entry, the following are applicable for Texas Users:

2.1.2a TEXAS APPORTIONED/DEALER LICENSE PLATES

Texas Apportioned and Dealer license plates are issued annually. The same license plate number may be issued to more than one vehicle, but with a different year of expiration. Therefore, when entering or inquiring on a Texas Apportioned or Dealer plate, the year of expiration must be verified.

Paper Texas Dealer license plates are not allowed entry into TCIC/NCIC 2000 because the number on each plate is not unique to that plate.

Metal Texas dealer license plates can be entered if they fall within the following range of numbers:

1D0001 to 9D9999

The Motor Vehicle Division of the Texas Department of Transportation has advised that all other dealer plates are non-unique. Therefore, they are not allowed entry into TCIC/NCIC 2000.

2.1.2b MISCELLANEOUS (MIS) FIELD

When the LIS field is "TX", Texas agencies must indicate which plate was stolen in the MIS field. For example: front, rear, one plate or both plates.

2.2 MODIFY (ML)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

ML MODIFY STOLEN LICENSE PLATE RECORD ORI: TX DPS0000 LIC: ABC123____ OCA: TEST123_____________ ENTER NEW INFORMATION BELOW. USE AN ASTERISK '*' TO DELETE AN OPTIONAL FIELD. MKE: EL- _ ORI: TX _______ LIC: __________ LIS: __ LIY: YYYY LIT: PC DOT: MMDDYYYY OCA: ____________________ LKI: _________ LKA: ____________________ MIS: FRONT PLATE WAS STOLEN__________________________________________________________________________________________________________________________________________________________________________________ NOA: _ VLN: ______________________________ CONTROL FIELD: __________

Revised May, 2002 2 Version 1.1

2.2.2 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION

For NCIC/TCIC 2000 validation, a Name of Validator (VLN) may be added to a license plate record to indicate that the record has met the criteria for validation. When the VLN is entered, TCIC 2000 and NCIC 2000 store the current date in the record as the Date of Last Validation (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected. The acknowledgment for the modification message containing the VLN will indicate the record has been validated. The VLN can be in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc. The NCIC 2000 policy requiring "on-line" validation has been suspended until further notice.

2.3 CANCEL (XL)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE

XL CANCEL STOLEN LICENSE PLATE RECORD ORI: TX DPS0000 LIC: ABC123____ OCA: TEST123_____________ RPP: CASE DROPPED_________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CL' IF PLATE WAS RECOVERED.

2.4 INQUIRY (QV)

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QV VEHICLE INQUIRY MKE: QV- _ ORI: TX DPS0000 LIC: ABC123____ LIS: TX VIN: ____________________ VMA: ________________________ NIC: __________ RELATED SEARCH HIT: N IS THIS QUERY DUE TO A DISPLAYED H.E.A.T. DECAL? Y REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZV' FOR ADMIN/TEST INQUIRY.

Revised May, 2002 3 Version 1.1

2.4.2 REQUIREMENTS FOR INQUIRY

Inquiries can be made using the NIC only or LIC only. The LIS is set to default as "TX" in the TLETS format. If the LIS is other than "TX", enter the appropriate LIS code for the license plate being inquired upon.

2.4.3 ADDITIONAL MESSAGE FIELD CODES FOR INQUIRY BY TEXAS USERS

Field Name RequirementsMessage Field

Code Field Length Data Type

H.E.A.T. Decal Optional HDN 1-1Alphabetic

Y=Stopped due to H.E.A.T. decalN=Not stopped due to H.E.A.T. decal

2.4.4 ADDITIONAL GUIDELINES FOR INQUIRY

2.4.4a H.E.A.T. DECAL

This field should be used to indicate whether or not the query is due to a displayed H.E.A.T. decal. Place a "Y" for yes or "N" for no. If the H.E.A.T. decal field is not filled, it will default to "N".

2.5 LOCATE (LL)

2.5.1 EXAMPLE OF LOCATE MESSAGE

LL LOCATE STOLEN LICENSE PLATE RECOVERING AGENCY'S ORI: TX 0000000 LIC: ABC123____ OCA IN THE RECORD: TEST123_____________ DATE OF RECOVERY: 03022002 RECOVERING AGENCY'S CASE NUMBER: OCA TEST____________ RPP: HIT NCIC 20020302____ NPA: 1__ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________

Revised May, 2002 4 Version 1.1

2.6 CLEAR (CL)

2.6.1 EXAMPLE OF CLEAR MESSAGE

CL CLEAR STOLEN LICENSE PLATE RECORD ORI: TX DPS0000 LIC: ABC123____ OCA: TEST123_____________ DATE OF RECOVERY: 03022002 IF THE LICENSE PLATE WAS RECOVERED BY AN AGENCY OTHER THAN THE ENTERING AGENCY, THE RECOVERING AGENCY HAS NOT PLACED A LOCATE ON THE RECORD: RECOVERING AGENCY ORI: _________ RECOVERING AGENCY OCA: _________________ RPP: HIT NCIC 20020302____ NPA: 1__ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF PLATE(S) RECOVERED. USE 'XL' TO CANCEL INVALID RECORD.

Revised May, 2002 5 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESMISSING PERSON FILETABLE OF CONTENTS

1. INTRODUCTION 11.1 MESSAGE KEY (MKE) CODES 1

2. MISSING PERSON TRANSACTIONS 12.1 ENTRY (EM) 1

2.1.1 EXAMPLE OF ENTRY MESSAGE 12.1.2 ADDITIONAL GUIDELINES FOR ENTRY 2

2.1.2a MISSING PERSONS CLEARINGHOUSE 22.1.2b ENTRY AND FLAGGING CRITERIA 22.1.2c PLACE OF BIRTH (POB) 32.1.2d DATE OF EMANCIPATION (DOE) 3

2.2 MODIFY (MM) 32.2.1 EXAMPLE OF MODIFICATION MESSAGE 32.2.2 VALIDATION GUIDELINES

FOR NCIC/TCIC 2000 MODIFICATION 42.3 CANCEL (XM) 4

2.3.1 EXAMPLE OF CANCELLATION MESSAGE 42.4 INQUIRY (QW or ZW) 5

2.4.1 EXAMPLE OF INQUIRY MESSAGE 52.4.2 ADDITIONAL GUIDELINES FOR INQUIRY 5

2.4.2a QW-X INQUIRIES 52.4.2b QW-T INQUIRIES 52.4.2c MISSING PERSON INQUIRIES 52.4.2d CROSS SEARCH 6

2.4.3 NON-UNIQUE IDENTIFIER (QM) INQUIRY 62.4.3a ADDITIONAL GUIDELINES FOR

NON-UNIQUE IDENTIFIER (QM) INQUIRY 62.5 LOCATE (LM) 7

2.5.1 EXAMPLE OF LOCATE MESSAGE 72.5.2 ADDITIONAL GUIDELINES FOR LOCATE 7

2.5.2a IMMEDIATE REMOVAL 72.6 CLEAR (CM) 7

2.6.1 EXAMPLE OF CLEAR MESSAGE 73. SUPPLEMENTAL DATA TRANSACTIONS 8

3.1 INTRODUCTION 83.2 MESSAGE KEY (MKE) CODES 83.3 ENTRY (EMN1, EMN2, EDD) 8

3.3.1 EXAMPLE OF SUPPLEMENTALDATA TRANSACTION (EMN1) 8

3.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (EMN2) 9

3.3.3 EXAMPLE OF SUPPLEMENTAL DENTAL DATA TRANSACTION (EDD) 9

3.4 MODIFY (MDD) 10

Revised May, 2002 Version 1.1

3.4.1 EXAMPLE OF MODIFYSUPPLEMENTAL DENTAL DATA TRANSACTION 10

3.5 CANCEL (XMN, XDD) 113.5.1 EXAMPLE OF CANCEL

SUPPLEMENTAL DATA TRANSACTION (XMN) 113.5.2 EXAMPLE OF CANCEL

SUPPLEMENTAL DATA TRANSACTION (XDD) 11

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Missing Person File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the Missing Person File:

MKE FORMATEM ENTER MISSING PERSON RECORDMM MODIFY MISSING PERSON RECORDXM CANCEL MISSING PERSON RECORDLM LOCATE MISSING PERSON RECORDCM CLEAR MISSING PERSON RECORDQW QUERY PERSON (INVESTIGATIVE PURPOSES)ZW QUERY PERSON (ADMINISTRATIVE/TEST PURPOSES)QM MISSING PERSON NON-UNIQUE IDENTIFIER INQUIRY

2. MISSING PERSON TRANSACTIONS

2.1 ENTRY (EM)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EM ENTER MISSING PERSON RECORD-- PAGE ONE MKE: EM J_ ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: W POB: TX DOB: 01011987 DOE: 01012005 HGT: 510 WGT: 140 EYE: BLU HAI: BLU FBI: _________ SKN: FAR SMT: TAT BACK__ FPC: ____________________ MNU: PI - 01234567____ SOC: 555555555 OLN: 12345678____________ OLS: TX OLY: 2005 MNP: MP DLC: 03022002 OCA: TESTOCA_____________ LKI: _________ LKA: ____________________ NOA: N MPC: R LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ BLT: _____ CRC: C FPA: N BXR: N (MIS DATA IS TO BE ENTERED ON PAGE 2).

Revised May, 2002 1 Version 1.1

EM2 ENTER MISSING PERSON RECORD--PAGE TWO VRX: ________________________________________ JWT: __________________________________________________ JWL ____________________________________________________________________________________________________ MIS TEST MISCELLANEOUS FIELD____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________CONTROL FIELD: __________

2.1.2 ADDITIONAL GUIDELINES FOR ENTRY

2.1.2a MISSING PERSONS CLEARINGHOUSE

The Missing Persons Clearinghouse (MPCH) is part of the Special Crimes Service of the Texas Department of Public Safety Criminal Law Enforcement Division. The Clearinghouse serves as the central repository of information regarding Texas' missing persons or persons missing from other states but believed to be in Texas. The function of the MPCH is to establish a system of intrastate communication; collect, process, maintain, and disseminate information on missing persons; facilitate awareness programs on how to prevent child abduction; and provide a statewide toll-free telephone number for the reporting and receiving of information on missing persons. Agencies in need of missing person reports, medical releases, dental releases, birth certificate flag forms or data collection entry guides may contact the MPCH at (512) 424-2812, toll free at 1-800-346-3243 or via e-mail at [email protected]. MPCH also has a web site at www.txdps.state.tx.us/mpch.

2.1.2b ENTRY AND FLAGGING CRITERIA

According to Chapter 63 of the Code of Criminal Procedures and Section 79.008 of the Human Resources Code, at the time of receiving a report of a missing child (person under 18 years of age), a law enforcement agency must:

1. Provide the complainant with dental and medical record release forms.

2. If the child is under 11 years of age, immediately notify each school or day care the child attended or was enrolled in as well as the Bureau of Vital Statistics, if the child was born in this state, that the child is missing. If the child was born in another state, the law enforcement agency must notify the law enforcement agency or clearinghouse of the appropriate state and request they contact the state birth certificate agency and each school or licensed day care the child attended to flag the missing child's records. Please fax the Birth Certificate Flag form to the MPCH at 512-424-2885 within five working days.

Revised May, 2002 2 Version 1.1

3. Immediately enter the name and identifiers of the child into NCIC 2000, placing a notation in the MIS field stating STRANGER ABDUCTION, PARENTAL or FAMILY ABDUCTION, RUNAWAY, or CIRCUMSTANCES UNK. The MPC field may also be used to indicate the circumstances of the missing person. Information not immediately available must be obtained and the record modified with the new information as soon as possible. Records entered into NCIC 2000 having a Texas ORI are automatically entered into the MPCH.

According to Chapter 63, Articles 63.006 and 63.007 of the Code of Criminal Procedures, at any time a report is made for a missing adult, the officer shall issue a medical release and shall complete a dental release form that state the missing adult has not voluntarily relocated or removed him/herself from communication with others. This form is not valid unless signed by the missing person's spouse, adult child who is reasonably available, parent, or legal guardian. The law enforcement agency should immediately enter the person's name and identifiers into TCIC/NCIC 2000. Information not immediately available must be obtained and the record modified with the new information as soon as possible.

2.1.2c PLACE OF BIRTH (POB)

The Place of Birth field should be completed for any child under the age of eleven (11).

2.1.2d DATE OF EMANCIPATION (DOE)

The Date of Emancipation (DOE) is determined by the laws of the state of residence of the missing juvenile. Effective September 1, 1995, Texas State law emancipates juveniles on their eighteenth (18) birthday, and that date should be reflected in the DOE field. Texas users entering missing juveniles who legally reside in another state should determine that state's laws regarding the age of emancipation, and use that date in the DOE field.

2.2 MODIFY (MM)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

MM MODIFY MISSING PERSON RECORD – PAGE ONE ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ ENTER NEW INFORMATION BELOW. USE '*' TO DELETE OPTIONAL FIELD. MKE: EM __ ORI: TX _______ NAM: ______________________________ SEX: _ RAC: _ POB: __ DOB: MMDDYYYY DOE: MMDDYYYY HGT: 511 WGT: 150 EYE: ___ HAI: BRO FBI: _________ SKN: ___ SMT: __________ FPC: ____________________ MNU: __ - ____________ SOC: _________ OLN: ____________________ OLS __ OLY YYYYMNP: __ DLC: MMDDYYYY OCA: ____________________ LKI: _________ LKA: ____________________ NOA: _ MPC: _ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ BLT: OPOS CRC: _ FPA: _ BXR: _

Revised May, 2002 3 Version 1.1

MM2 MODIFY MISSING PERSON RECORD - PAGE TWO VRX: ________________________________________ JWT: RI,WA_____________________________________________ JWL TEST RING,TEST WATCH________________________________________________________________________________ MIS MODIFY MISCELLANEOUS FIELD____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________VLN: ______________________________ CONTROL FIELD: __________

2.2.2 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION

For NCIC/TCIC 2000 validation, a Name of Validator (VLN) may be added to a missing person record to indicate that the record has met the criteria for validation. When the VLN is entered, TCIC 2000 and NCIC 2000 store the current date in the record as the Date of Last Validation (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected. The acknowledgment for the modification message containing the VLN will indicate the record has been validated. The VLN can be in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc. The NCIC 2000 policy requiring "on-line" validation has been suspended until further notice.

2.3 CANCEL (XM)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE

XM CANCEL MISSING PERSON RECORD ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ RPS: VOL RETURN 20020325__ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CM' IF PERSON WAS FOUND.

Revised May, 2002 4 Version 1.1

2.4 INQUIRY (QW or ZW)

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QW PERSONS INQUIRY MKE: QW- _ ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 01011985 FBI: _________ SOC: _________ OLN: ____________________ MNU: __ - ____________LIC: __________ LIS: __ VIN: ____________________ VMA: ________________________OCA: ____________________ NIC: __________ RELATED SEARCH HIT: _ EXPANDED NAME SEARCH: Y REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZW' FOR ADMIN/TEST INQUIRY.

2.4.2 ADDITIONAL GUIDELINES FOR INQUIRY

2.4.2a QW-X INQUIRIES

TCIC 2000 Missing Person inquiries use the New York State Identification and Intelligence System (NYSIIS), like NCIC 2000, to match a name in an inquiry with a name in a record on file. TCIC 2000 inquiries containing DOB search exactly as NCIC 2000. If the MKE: "QW-X" is used, TCIC 2000 searches the exact match of the date of birth.

2.4.2b QW-T INQUIRIES

Missing Person file inquiries using MKE: "QW-T" will search TCIC 2000 only. An NCIC 2000 search will not be performed.

2.4.2c MISSING PERSON INQUIRIES

The TLETS Persons inquiry format (transaction code "QW" or "ZW") allows an inquiry to be made by: 1. NAM and one, more than one, or all of the following alphanumeric identifiers:

DOB (including month, day, year), FBI, SOC, OLN, and MNU.2. Vehicle data (LIC/LIS or VIN/VMA).3. NAM and OCA only (exact spelling of the name contained in the record is required).4. NIC only.

This means that a TLETS inquiry can be made on multiple identifiers in one format.

Revised May, 2002 5 Version 1.1

2.4.2d CROSS SEARCH

The "QW" format cross-searches the following TCIC/NCIC 2000 files: Wanted Person, Missing Person, Protective Order, Foreign Fugitive, Deported Felon, Sex Offender, U.S. Secret Service Protection file, Canadian Warrants, Violent Gang and Terrorist Organization, Convicted Person on Supervised Release, Officer Threat, Individual Identity and the Texas Concealed Handgun License file. If vehicle identifiers are included in the inquiry, the Vehicle, Boat, Vehicle/Boat Part, and License Plate files will be searched.

2.4.3 NON-UNIQUE IDENTIFIER (QM) INQUIRY

QM MISSING PERSONS FILE NON-UNIQUE IDENTIFIER INQUIRY ORI: TX DPS0000 AGE: 25 SEX: M RAC: W HGT: 510 WGT: 150 EYE: BLU HAI: BRO NAM: ______________________________ EXPANDED NAME SEARCH: _ CONTROL FIELD: __________ (NAM IS THE ONLY OPTIONAL IDENTIFIER.)

2.4.3a ADDITIONAL GUIDELINES FOR NON-UNIQUE IDENTIFIER (QM) INQUIRY

When a non-unique identifier inquiry is received, TCIC/NCIC 2000 searches the Missing Person File for possible matches, i.e., candidate records. A score is assigned to each candidate record and is computed based upon the variance between the inquiry AGE, HGT, and WGT,the representation of the relative similarity between the inquiry data and the data in the candidate records. The score is used by TCIC/NCIC 2000 to select up to 20 most likely candidate records for the response to the inquiring agency. When the Expanded Name Search (ESN) field is used, primary hits will be determined using each input name part as a last name, interchanging the remaining name parts as given names.

Revised May, 2002 6 Version 1.1

2.5 LOCATE (LM)

2.5.1 EXAMPLE OF LOCATE MESSAGE

LM LOCATE MISSING PERSON RECORD LOCATING AGENCY'S ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA IN THE RECORD: TESTOCA_____________ DATE MISSING PERSON WAS FOUND: 03252002 LOCATING AGENCY'S OCA: TEST LMOCA__________ RPS: HIT NCIC 20020325____ PAR: _ HIT: __ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ DISPOSITION ('DETN' OR 'RELD'): RELD CONTROL FIELD: __________

2.5.2 ADDITIONAL GUIDELINES FOR LOCATE

2.5.2a IMMEDIATE REMOVAL

A missing person record, including all supplemental data, is automatically removed from both TCIC 2000 and NCIC 2000 when a locate message is placed on the record.

2.6 CLEAR (CM)

2.6.1 EXAMPLE OF A CLEAR MESSAGE

CM CLEAR MISSING PERSON ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ DATE OF CLEAR 03252002 IF THE PERSON WAS FOUND BY AN AGENCY OTHER THAN THE ENTERING AGENCY: APPREHENDING AGENCY ORI TX0000000 APPREHENDING AGENCY OCA TEST CMOCA_________RPS: HIT NCIC 20020325____ PAR: _ HIT: __ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF PERSON FOUND. USE 'XM' TO CANCEL INVALID RECORD.

Revised May, 2002 7 Version 1.1

3. SUPPLEMENTAL DATA TRANSACTIONS

3.1 INTRODUCTION

Texas TLETS direct users must add supplemental data to a missing person record using transaction codes "EMN1" and "EMN2" depending upon the type of additional identifier being added. Before a supplemental field may be entered, data must exist in that field of the existing base record. If that field was not filled upon entry, a modification message (transaction code "MM") must be used to add that field information to the base record before supplemental data can be added. Supplemental data cannot be modified. If there is an error in the supplemental data added to a base record, the supplemental data must be canceled and re-entered. Texas TLETS direct users cancel supplemental data using transaction code "XMN".

Texas TLETS direct users must add supplemental dental data to a missing person record using transaction code "EDD". Supplemental dental data can be modified using transaction code "MDD". To cancel supplemental dental data, Texas TLETS direct users must use transaction code "XDD".

3.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for Supplemental Data transactions in the Missing Person File:

MKE FORMATEMN1 ENTER SUPPLEMENTAL AKA/DOB INFORMATIONEMN2 ENTER SUPPLEMENTAL DATA RECORD

(SMT, SOC, MNU, OLN, LIC, VIN, CMC)XMN CANCEL SUPPLEMENTAL DATAEDD ENTER SUPPLEMENTAL DENTAL DATAMDD MODIFY SUPPLEMENTAL DENTAL DATAXDD CANCEL SUPPLEMENTAL DENTAL DATA

3.3 ENTRY (EMN1, EMN2, EDD)

3.3.1 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (EMN1)

EMN1 ENTER SUPPLEMENTAL AKA/DOB INFORMATION--MISSING PERSON FILE MKE: EMN ORI: TX DPS0000 NAM: TEST, RECORD__________________ OCA: 123TEST_____________ ENTER MULTIPLE AKA AND/OR DOB DATA BELOW: AKA: RECORD, TESTING___________ _ AKA: RECORD, JOE___________________ AKA: ______________________________ AKA: ______________________________ AKA: ______________________________ AKA: ______________________________ DOB: 02251987 DOB: MMDDYYYY DOB: MMDDYYYY CONTROL FIELD: __________

Revised May, 2002 8 Version 1.1

3.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (EMN2)

EMN2 ENTER SUPPLEMENTAL DATA RECORD--MISSING PERSON FILE MKE: EMN ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: 123TEST_____________ ENTER SUPPLEMENTAL DATA BELOW: SMT: TAT L LEG_ SMT: __________ SMT: __________ SOC: _________ SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ CONTROL FIELD: __________

3.3.3 EXAMPLE OF SUPPLEMENTAL DENTAL DATA TRANSACTION (EDD)

EDD ENTER SUPPLEMENTAL DENTAL DATA FOR MISSING OR UNIDENTIFIED PERSONS MKE: ED ORI: TX DPS0000 NIC: M123456789 OCA: 123TEST_____________ DXR: Y MPA: N DRE: __________________________________________________ DCH: ALL______________________________________________________________________ ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________CONTROL FIELD: __________ (ENTER 'X' TO ENTER RECORD; LEAVE EMPTY FOR PAGE 2)

EDD2 SECOND PAGE OF ENTER SUPPLEMENTAL DENTAL DATA DCH (CONTINUED): ______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ (ENTER 'X' TO ENTER RECORD, OR LEAVE EMPTY FOR PAGE 3.) _

Revised May, 2002 9 Version 1.1

EDD3 THIRD PAGE OF ENTER SUPPLEMENTAL DENTAL DATA DCH (CONTINUED): ______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

3.4 MODIFY (MDD)

3.4.1 EXAMPLE OF MODIFY SUPPLEMENTAL DENTAL DATA TRANSACTION

MDD MODIFY SUPPLEMENTAL DENTAL DATA FOR MISSING OR UNIDENTIFIED PERSONS MKE: MD ORI: TX DPS0000 NIC: M123456789 OCA: 123TEST_____________ PUT NEW INFORMATION BELOW. USE AN ASTERISK '*' TO DELETE AN OPTIONAL FIELD. DXR: _ MPA: Y DRE: __________________________________________________ DCH: ______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________ (ENTER 'X' TO ENTER RECORD; LEAVE EMPTY FOR PAGE 2) _

MDD2 SECOND PAGE OF MODIFY SUPPLEMENTAL DENTAL DATA DCH (CONTINUED): ______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ (ENTER 'X' TO ENTER RECORD, OR LEAVE EMPTY FOR PAGE 3.) _

Revised May, 2002 10 Version 1.1

MDD3 THIRD PAGE OF MODIFY SUPPLEMENTAL DENTAL DATA DCH (CONTINUED): ______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

3.5 CANCEL (XMN, XDD)

3.5.1 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XMN)

XMN CANCEL SUPPLEMENTAL DATA--MISSING PERSON FILE MKE: XMN ORI: TX DPS0000 NAM: TEST, RECORD__________________ OCA: 123TEST_____________ ENTER DATA TO BE CANCELED BELOW: AKA: ______________________________ DOB: MMDDYYYY SMT: TAT L LEG_ SOC: _________ MNU: _______________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ CONTROL FIELD: __________

3.5.2 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XDD)

XDD CANCEL SUPPLEMENTAL DENTAL DATA FOR MISSING OR UNIDENTIFIED PERSONS MKE: XD ORI: TX DPS0000 NIC: M123456789 OCA: 123TEST_____________ CONTROL FIELD: __________

Revised May, 2002 11 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESTHREAT AGAINST PEACE OFFICER FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 THREAT AGAINST PEACE OFFICER FILE OVERVIEW 11.2 CRITERIA FOR ENTRY 11.3 TCIC 2000 ONLY TRANSACTIONS 21.4 VALIDATION 21.5 RECORD RETENTION 2

2. THREAT AGAINST PEACE OFFICER TRANSACTIONS 22.1 ENTRY (EOT) 2

2.1.1 EXAMPLE OF ENTRY MESSAGE 22.1.2 MANDATORY FIELDS FOR ENTRY 32.1.3 ADDITIONAL GUIDELINES FOR ENTRY 3

2.1.3a IMMEDIATE ENTRY 32.1.3b SUBJECT IDENTIFIERS 3

2.1.4 MESSAGE FIELD CODES AND EDITS 32.2 MODIFY (MOT) 6

2.2.1 EXAMPLE OF MODIFICATION MESSAGE 62.3 CANCEL (XOT) 6

2.3.1 EXAMPLE OF CANCELLATION MESSAGE 62.4 INQUIRY (QW, ZW, QOT) 7

2.4.1 EXAMPLE OF INQUIRY MESSAGE (QW or ZW) 72.4.2 EXAMPLE OF INQUIRY MESSAGE (QOT) 7

3. SUPPLEMENTAL DATA TRANSACTIONS 73.1 INTRODUCTION 73.2 MESSAGE KEY (MKE) CODES 83.3 ENTRY (ENTO, ENTA) 8

3.3.1 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENTO) 83.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENTA) 8

3.4 CANCEL (XNTO, XNTA) 93.4.1 EXAMPLE OF CANCEL

SUPPLEMENTAL DATA TRANSACTION (XNTO) 93.4.2 EXAMPLE OF CANCEL

SUPPLEMENTAL DATA TRANSACTION (XNTA) 94. STATUTORY REFERENCE 10

4.1 GOVERNMENT CODE §411.048 10

Revised July, 2002 Version 1.2

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for Threat Against Peace Officer File document the data field specifications.

1.1 THREAT AGAINST PEACE OFFICER FILE OVERVIEW

In accordance with House Bill 776, this file was created to establish a database to collect threat information to help protect officers and to provide rapid, statewide access to information about threats made against peace officers. This file is intended to be an alert for any officer(s) at risk due to a recorded threat by a known individual. This is a TCIC 2000 only file. A record in this file will be returned in response to a Persons inquiry (transaction code "QW" or "ZW").

Agencies may not use data received solely based on a Threat Against Peace Officer query to populate another searchable database. This file merely serves as an alert to officers and to identify the agency to contact in order to verify an officer threat record.

A record entered in this file indicates a potentially dangerous individual, not necessarily a wanted person. No officer or agency may use a record in this file by itself to provide probable cause for a warrantless arrest, probable cause in an affidavit for an arrest or search warrant, a grounds of denial for a permit or other license, or reasonable suspicion to stop or detain an individual. An officer or agency may only use an officer threat record to take reasonable action to protect the officer or citizens, engage in a consensual citizen encounter, or to establish reasonable suspicion to frisk a suspect already stopped or detained for another independent reason.

An individual who is the subject of an entry into the Threat Against Peace Officer File may request that the Director of DPS, or the Director's designee, or a court review the information to determine compliance with established rules.

1.2 CRITERIA FOR ENTRY

A person who threatens a peace officer can be entered into this file at the discretion of the entering agency if the following criteria have been met:

1. The threat consists of an individual’s expression of intent to inflict serious bodily injury or death on a peace officer; and

2. The threat is not from an anonymous source.

This file does not apply to every threat or offense targeting an officer or threats made by a group rather than an individual. Agencies may not submit an entry without proper criminal predicate directly related to the threat information supporting the record entry. The individual need not have been arrested for the threat being investigated or any other crime, as a predicate for submitting an entry into this file.

"Peace officer" means a person elected, employed, or appointed as a peace officer under Article 2.12, Code of Criminal Procedure, Section 51.212 or 51.214, Education Code, or other law. (Texas Penal Code, Section 1.07(a))

Revised July, 2002 1 Version 1.2

1.3 TCIC 2000 ONLY TRANSACTIONS

MKE FORMATEOT ENTER PERSON THREATENING A PEACE OFFICERMOT MODIFY PERSON THREATENING A PEACE OFFICERXOT CANCEL PERSON THREATENING A PEACE OFFICERQOT QUERY THREAT TO PEACE OFFICERQW PERSONS INQUIRY (INVESTIGATIVE PURPOSES)ZW PERSONS INQUIRY (ADMINSTRATIVE/TEST PURPOSES)

1.4 VALIDATION

Agencies that enter a Threat Against Peace Officer record(s) are required to validate their entry within a five-year review period.

1.5 RECORD RETENTION

Records entered into this file will remain in TCIC 2000 indefinitely or until action is taken by the entering agency to remove the record.

2. THREAT AGAINST PEACE OFFICER TRANSACTIONS

2.1 ENTRY (EOT)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EOT ENTER PERSON THREATENING A PEACE OFFICER INTO TCIC - PAGE ONE MKE: EOT- C CMC: 05 ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: W POB: TX DOB: 01011961 HGT: 601 WGT: 150 EYE: BRO HAI: BRO HLN: 1 HST: 4 HFC: 3 FBI _________ SKN: MEDSMT: TAT NECK__ FPC: ____________________ MNU: PI - 01234567____ SOC: 555555555OLN: 12345678____________ OLS: TX OLY: 2005 OCA: TESTOCA_____________ DTM: 03182002 THR: 1 THT: 01 SRI: TX DPS0000 NPO TEST,OFFICER NAME_____________DPO: 03202002 POC: POINT OF CONTACT NAME_________ CNO: 512 555 - 5555 LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

EOT2 ENTER PERSON THREATENING A PEACE OFFICER INTO TCIC - PAGE TWO RTI: Y LCL: 1 PHS: Y PHC: Y DNA: N IND: Y GPH: Y FEI: N GNG: GANG NAME HERE________ WPI: WEAPON INFORMATION HERE _____ MIS: TEST MISCELLANEOUS FIELD______________________________________________

Revised July, 2002 2 Version 1.2

__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

2.1.2 MANDATORY FIELDS FOR ENTRY

The following fields are mandatory for a Threat Against Peace Officer record to be accepted by TCIC 2000: Originating Agency Identifier (ORI), Name (NAM), Sex (SEX), Race (RAC),Date Threat Made (DTM), Originating Agency Case Number (OCA), Threat Type (THT) andat least one numeric identifier, such as Date of Birth (DOB), Social Security Number (SOC), Operator’s License Number (OLN), Miscellaneous Number (MNU) or FBI Number (FBI),

2.1.3 ADDITIONAL GUIDELINES FOR ENTRY

2.1.3a IMMEDIATE ENTRY

Under Government Code 411.048, a criminal justice agency must, upon determining that an individual has made a serious threat against an officer, immediately enter an electronic report of the threat into the DPS database (TCIC 2000).

2.1.3b SUBJECT IDENTIFIERS

The subject identifier fields found in the Enter Person Threatening a Peace Officer (transaction code "EOT") format are the same as those for a Wanted Person entry format (transaction code "EW" or "EE"). Applicable coding may be found in the Personal Descriptors section of the NCIC 2000 Code Manual.

2.1.4 MESSAGE FIELD CODES AND EDITS

There are additional message field codes and edits for Threat Against Peace Officer records, which are as follows:

CNO Agency Contact Person Phone Number

Optional. The telephone number of the contact person. Enter telephone number with area code first. Example: 512-555-5555

DNA DNA Available Optional. A one-character value indicating if DNA is available for the subject who threatened the peace officer. Valid values: "Y" for

Revised July, 2002 3 Version 1.2

Yes or "N" for No.DPO Date Peace Officer

Notified of ThreatOptional. Must be a valid eight digit date. Enter in MMDDYYYY format. Example: 05222002.

FEI Firearms/Explosive Experience

Optional. A one-character value indicating if the subject who threatened the peace officer has experience with firearms and/or explosives. Valid values: "Y" for Yes or "N" for No.

GNG Affiliate Group Name Optional. Enter the name of the group (such as a gang) the subject is affiliated with (if any).

GPH Generic Photo Optional. A one-character value indicating if a photo is available for the subject who threatened the peace officer. Valid values: "Y" for Yes or "N" for No.

HFC Facial Hair Optional. A two-digit value representing the subject's facial hair. Valid values:1 = Full Beard 5 = Other2 = Goatee 6 = None3 = Mustache 4 = Unusual Sideburns

HLN Hair Length Optional. A two-digit value representing the subject's hair length. Valid values:1 = Shoulder 4 = Short2 = Collar 5 = Bald/Balding3 = Eartop 6 = Other

HST Hair Style Optional. A two-digit value representing the subject's hairstyle. Valid values: 1 = Afro 5 = Braided2 = Wavy 6 = Ponytail3 = Shag 7 = Razor Cut4 = Straight 8 = Other

IND Image of Subject Available Optional. A one-character value indicating if an image of the subject is available. Valid values: "Y" for Yes or "N" for No.

LCL Likelihood Code Level Optional. A one-digit value indicating the likelihood of the subject carrying out the threat made against the peace officer.

Revised July, 2002 4 Version 1.2

Valid values:1 = Probable 2 = Possible 3 = Unknown

NPO Name of Peace Officer Optional. Enter name of the peace officer threatened.

POC Agency Point of Contact Optional. Enter name of contact person.

PHC Previous Charge or Conviction for Crimes Against Peace Officers

Optional. A one-character value indicating if subject who made the threat has been previously charged or convicted for crimes against peace officers. Valid values: "Y" for Yes or "N" for No.

PHS Past History of Violence Optional. A one-character value indicating if the subject who threatened the peace officer has a history of violence. Valid values: "Y" for Yes or "N" for No.

RTI Repeat Threatener Information

Optional. A one-character value indicating if the subject who threatened the peace officer has threatened officer (s) in the past. Valid values: "Y" for Yes or"N" for No.

SRI Subject’s ORI Optional. The ORI of the threatened peace officer(s) agency.

THR Threat Reason Optional. Basis of the threat made against a peace officer. Valid values: 1 = Disagrees with police authority or 2 = Retaliation

THT Threat Type Mandatory. A two-digit value representing the method in which the threat was conveyed.Valid values:01 = Verbal threat made in person.02 = Verbal threat made via telephone.03 = Written threat made via letter.04 = Written threat made via informal note.05 = Written threat made viae-mail.

WPI Weapon Information Optional. Enter any known weapon information for the subject who threatened the peace officer.

2.2 MODIFY (MOT)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

Revised July, 2002 5 Version 1.2

MOT MODIFY PERSON THREATENING A PEACE OFFICER INTO TCIC - PAGE ONE ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ ENTER NEW DATA. '*' DELETES OPTIONAL FIELD. MKE: EOT- _ CMC: __ ORI: TX _______NAM: ______________________________ SEX: _ RAC: _ POB: __ DOB: 01011962 HGT: ___ WGT: ___ EYE: ___ HAI: ___ HLN: _ HST: _ HFC: _ FBI _________ SKN: ___SMT: __________ FPC: ____________________ MNU: __ - ____________ SOC: _________OLN: ____________________ OLS: __ OLY: YYYY OCA: ____________________ DTM: 03192002 THR: _ THT: __ SRI: TX _______ NPO ______________________________DPO: MMDDYYYY POC: ______________________________ CNO: 512 445 - 5555 LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

MOT2 MODIFY PERSON THREATENING A PEACE OFFICER INTO TCIC - PAGE TWO RTI: _ LCL: 2 PHS: _ PHC: _ DNA: _ IND: _ GPH: _ FEI: Y GNG: ______________________ WPI: ________________________________________ MIS: MODIFY MISCELLANEOUS FIELD__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

2.3 CANCEL (XOT)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE

XOT CANCEL PERSON THREATENING A PEACE OFFICER ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE AN INVALID RECORD.

2.4 INQUIRY (QW, ZW, QOT)

A record in the Threat Against Peace Officer File will be returned in response to a Persons Inquiry (transaction code "QW" or "ZW"). The Threat to Peace Officer Inquiry (transaction

Revised July, 2002 6 Version 1.2

"QOT") may be used to access only the Threat Against Peace Officer File. An inquiry of this type will display all data in the record whereas the "QW" or "ZW" search displays only certain data fields.

2.4.1 EXAMPLE OF INQUIRY MESSAGE (QW or ZW)

QW PERSONS INQUIRY MKE: QW- _ ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 01011962 FBI: _________ SOC: _________ OLN: ____________________ MNU: __ - ____________LIC: __________ LIS: __ VIN: ____________________ VMA: ________________________OCA: ____________________ NIC: __________ RELATED SEARCH HIT: _ EXPANDED NAME SEARCH: _ REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZW' FOR ADMIN/TEST INQUIRY.

2.4.2 EXAMPLE OF INQUIRY MESSAGE (QOT)

QOT THREAT TO PEACE OFFICER INQUIRY MKE: QOT ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 01011962 FBI: _________ SOC: _________ OLN: ____________________ MNU: __ - ____________LIC: __________ LIS: __ VIN: ____________________ VMA: ________________________OCA: ____________________ CONTROL FIELD: __________

3. SUPPLEMENTAL DATA TRANSACTIONS

3.1 INTRODUCTION

Texas direct TLETS member agencies may add supplemental data to a Threat Against Peace Officer record using transaction codes "ENTO" or "ENTA" depending upon the type of additional identifier being added. Before a supplemental field may be entered for the subject who threatened the peace officer, data must exist in that field of the existing base record. If that field was not filled upon entry, a modification message (transaction code "MOT") must be used to add that field information to the base record before supplemental data can be added. Supplemental data cannot be modified. If there is an error in the supplemental data added to a base record, the supplemental data must be canceled and re-entered. Texas TLETS direct users cancel supplemental data using transaction codes "XNTO" and "XNTA" depending upon the type of additional identifier being canceled.

Revised July, 2002 7 Version 1.2

3.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for Supplemental Data transactions in the Threat Against Peace Officer File:

MKE FORMATENTO ENTER SUPPLEMENTAL DATA RECORD

(AKA, DOB, SMT, SOC, MNU, OLN, LIC, VIN, CMC)ENTA ENTER THREAT TO PEACE OFFICER ADDRESS/PHONE DATAXNTO CANCEL SUPPLEMENTAL DATA RECORDXNTA CANCEL THREAT TO PEACE OFFICER ADDRESS/PHONE DATA

3.3 ENTRY (ENTO, ENTA)

3.3.1 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENTO)

ENTO ENTER SUPPLEMENTAL DATA RECORD - THREAT TO PEACE OFFICER FILE ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ ENTER SUPPLEMENTAL IDENTIFIERS BELOW: AKA: TESTING,JOE___________________ AKA: RECORD,TEST___________________ DOB: 01191965 DOB: MMDDYYYY SMT: TAT L LEG_ SMT: SC NOSE___ SOC: 444444444 SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: 15 CONTROL FIELD: __________

3.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENTA)

ENTA ENTER THREAT TO PEACE OFFICER ADDRESS/PHONE DATA ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ ENTER ADDRESS INFORMATION. ADDRESS TYPE: H ADDRESS STATUS: C STREET ADDRESS: 1234 STREET ADDRESS HERE______ CITY: CITY NAME HERE______ STATE: TX ZIP: 777775555 LOCATION: LOCATION NAME HERE__ ENTER PHONE INFORMATION BELOW: PHONE NUMBER TYPE: H TELEPHONE NUMBER: 512 222 - 1234 CONTROL FIELD: __________

3.4 CANCEL (XNTO, XNTA)

3.4.1 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XNTO)

Revised July, 2002 8 Version 1.2

XNTO CANCEL SUPPLEMENTAL DATA RECORD - THREAT TO PEACE OFFICER FILE ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ ENTER SUPPLEMENTAL IDENTIFIERS TO BE CANCELED BELOW: AKA: RECORD,TEST___________________ AKA: ______________________________ DOB: MMDDYYYY DOB: MMDDYYYY SMT: SC NOSE___ SMT: __________ SOC: _________ SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ CONTROL FIELD: __________

3.4.2 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XNTA)

XNTA CANCEL THREAT TO PEACE OFFICER ADDRESS/PHONE DATA ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TESTOCA_____________ ENTER ADDRESS INFORMATION TO BE CANCELED. ADDRESS TYPE: _ ADDRESS STATUS: _ STREET ADDRESS: ______________________________ CITY: ____________________ STATE: __ ZIP: _________ LOCATION: ____________________ ENTER PHONE INFORMATION TO BE CANCELED BELOW: PHONE NUMBER TYPE: H TELEPHONE NUMBER: 512 222 - 1234 CONTROL FIELD: __________

4. STATUTORY REFERENCE

4.1 TEXAS GOVERNMENT CODE §411.048

Revised July, 2002 9 Version 1.2

§411.048. THREATS AGAINST PEACE OFFICERS

(a) In this section: (1) "Criminal justice agency" has the meaning assigned by Article 60.01, Code of Criminal Procedure. (2) "Peace officer" has the meaning assigned by Section 1.07, Penal Code.(b) The bureau of identification and records shall establish and maintain a central index in the law enforcement information system maintained by the department to: (1) collect and disseminate information relating to an individual's expression of intent to inflict serious bodily injury or death on a peace officer; and (2) alert a peace officer of an expression of intent to inflict serious bodily injury or death on the officer.(c) A criminal justice agency, after making each determination required under Subsection (d), shall immediately enter into the information system an electronic report of an individual who expresses an intent to inflict serious bodily injury or death on a peace officer. The agency shall enter the information in the form and manner provided by rules adopted by the director.(d) Before entering information collected under this section into the information system, a criminal justice agency must determine that the report described by Subsection (c): (1) is not from an anonymous source; and (2) consists of an expression of intent to inflict serious bodily injury or death on a peace officer.(e) On proper inquiry into the information system, the department shall disseminate information collected under this section to a criminal justice agency as reasonably necessary to protect the safety of a peace officer. The criminal justice agency may use information disseminated under this subsection in the manner provided by rules adopted by the director.(f) The department shall promptly respond to a request to disclose information collected under this section by an individual who is the subject of the information.(g) An individual who is the subject of information collected under this section may request that the director, the director's designee, or a court review the information to determine whether the information complies with rules adopted by the director. The review shall be conducted using the same procedure for reviewing criminal information collected under Chapter 61, Code of Criminal Procedure.(h) A peace officer or criminal justice agency is not liable for an act or omission relating to the collection, use, or dissemination of information collected under this section in accordance with rules adopted by the director.(i) The director may adopt rules to implement and enforce this section. Any rule adopted by the director under this section must comply with the provisions of the Code of Federal Regulations, Title 28, Part 23, as it applies to criminal intelligence systems.

Revised July, 2002 10 Version 1.2

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESORIGINATING AGENCY IDENTIFIER (ORI) FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 VALIDATION 1

2. ORI TRANSACTIONS 12.1 INQUIRY (QO, ZO) 1

2.1.1 EXAMPLE OF INQUIRY MESSAGE (QO) 12.1.2 EXAMPLE OF INQUIRY MESSAGE (ZO) 22.1.3 ADDITIONAL GUIDELINES FOR INQUIRY 2

2.2 MODIFY (MO) 22.2.1 EXAMPLE OF MODIFICATION MESSAGE 22.2.2 ADDITIONAL GUIDELINES FOR MODIFICATION 3

2.2.2a VALIDATION GUIDELINEFOR NCIC/TCIC 2000 MODIFICATION 3

2.2.2b VERIFY MODIFICATION 3

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Originating Agency Identifier (ORI) File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 VALIDATION

In accordance with the NCIC 2000 validation requirement for ORI's, law enforcement and criminal justice agencies in Texas must validate the "QO" record for their agency on a biennial basis. Validation of an ORI is accomplished via the Modify On-line ORI transaction "MO". The validation process includes verifying the agency's status and authority, as well as other information listed in the ORI record, e.g., telephone number, street address, and ZIP code. Agencies who have authorization to inquire or enter for other agencies (i.e., District Attorney, County Attorney, Community Supervision and Corrections Department, Justice of the Peace, Constable, etc.) should also validate the "QO" record for the other agency.

2. ORI TRANSACTIONS

2.1 INQUIRY (QO, ZO)

2.1.1 EXAMPLE OF INQUIRY MESSAGE (QO)

QO INQUIRE IN NCIC ON-LINE ORI FILE YOUR ORI: TX DPS0000 ORI OF INQUIRY: TX0000000 CONTROL FIELD: __________

Revised May, 2002 1 Version 1.1

2.1.2 EXAMPLE OF INQUIRY MESSAGE (ZO)

ZO QUICK NCIC ON-LINE ORI FILE INQUIRY YOUR ORI: TX DPS0000 QUICK INQUIRY ON THIS ORI: TX0000000 CONTROL FIELD: __________

2.1.3 ADDITIONAL GUIDELINES FOR INQUIRY

Inquiries into the ORI File are used to display the translation of a nine-character ORI or to determine an agency's address and/or telephone number. A "ZO" inquiry displays the ORI translation, whereas a "QO" inquiry displays the entire ORI record. Since the ORI File is maintained in TCIC 2000 and NCIC 2000, a response will be returned from both systems when an ORI inquiry transaction is performed.

2.2 MODIFY (MO)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

MO MODIFY ON-LINE ORI RECORD ORI OF RECORD TO BE MODIFIED: TX DPS0000 PUT NEW INFORMATION BELOW. FILL IN ONLY THE FIELDS TO BE MODIFIED. ENTER AN ASTERISK '*' TO DELETE AN OPTIONAL FIELD. CT1: 512 555-5555 CT2: ____________ CT3: ____________ CRY: ______________________________ SNU: 1000___ SNA: TEST ADDRESS___________CTY: ____________________ ZIP: __________ FPP: ______ VLN : VALIDATORS NAME HERE__________ CONTROL FIELD: __________

Revised May, 2002 2 Version 1.1

2.2.2 ADDITIONAL GUIDELINES FOR MODIFICATION

2.2.2a VALIDATION GUIDELINE FOR NCIC/TCIC 2000 MODIFICATION

A Name of Validator (VLN) may be added to an ORI record to indicate that the record has met the criteria for validation. When the Name of Validator is entered, TCIC 2000 and NCIC 2000 store the current date in the record as the Date Last Validated (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected. The acknowledgement for the modification message containing a VLN will indicate the record has been validated. The VLN can be entered in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc.

2.2.2b VERIFY MODIFICATION

There is an Originating Agency Identifier (ORI) file maintained in TCIC 2000 and NCIC 2000. When a modification message is performed, agencies should verify the modification was accepted by both systems. This check can be accomplished by performing a "QO" inquiry on the ORI after modification.

Revised May, 2002 3 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESPROTECTIVE ORDER FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 CRITERIA FOR ENTRY 11.2 RECORD RETENTION 11.3 MESSAGE KEY (MKE) CODES 1

2. PROTECTIVE ORDER TRANSACTIONS 22.1 ENTRY (EPO) 2

2.1.1 EXAMPLE OF ENTRY MESSAGE 22.1.2 ADDITIONAL GUIDELINES FOR ENTRY 2

2.1.2a AGENCY JURISDICTION 22.1.2b MESSAGE KEY CODE 3

2.1.3 MESSAGE FIELD CODES AND EDITS 32.2 MODIFY (MPO) 5

2.2.1 EXAMPLE OF MODIFICATION MESSAGE 52.2.2 VALIDATION GUIDELINES

FOR NCIC/TCIC 2000 MODIFICATION 52.2.3 ADDITIONAL GUIDELINES FOR MODIFICATION 6

2.2.3a MESSAGE KEY CODE 62.3 CANCEL (XPO) 6

2.3.1 EXAMPLE OF CANCELLATION MESSAGE 62.3.2 ADDITIONAL GUIDELINES FOR CANCELLATION 6

2.3.2a MESSAGE KEY CODE 62.4 INQUIRY (QPO) 7

2.4.1 EXAMPLE OF INQUIRY MESSAGE 72.4.2 ADDITIONAL GUIDELINES FOR INQUIRY 7

2.4.2a PROTECTIVE ORDER INQUIRIES 72.5 CLEAR (CPO) 7

2.5.1 EXAMPLE OF CLEAR MESSAGE 72.5.2 ADDITIONAL GUIDELINES FOR CLEAR 8

2.5.2a MESSAGE KEY CODE 82.5.2b CLEARED PROTECTIVE ORDER STATUS 8

3. SUPPLEMENTAL DATA TRANSACTIONS 83.1 INTRODUCTION 83.2 MESSAGE KEY (MKE) CODES 83.3 ENTRY (ENPO, ENPT) 9

3.3.1 EXAMPLE OF SUPPLEMENTALDATA TRANSACTION (ENPO) 9

3.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENPT) 9

3.3.3 MESSAGE FIELD CODES AND EDITS 93.4 CANCEL (XNPO, XNPT) 10

3.4.1 EXAMPLE OF CANCEL SUPPLEMENTAL DATA (XNPO) 103.4.2 EXAMPLE OF CANCEL SUPPLEMENTAL DATA (XNPT) 10

4. COUNTY CODE LIST 11

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Protective Order File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 CRITERIA FOR ENTRY

Each record in the Protective Order file must be supported by a protective order. The protective order must have been issued for the purpose of preventing violent or threatening acts or harassment against, or contact or communication with or physical proximity to, another person. This includes final orders issued by civil or criminal courts (other than support or child custody orders) whether obtained by filing an independent action or as a pendente lite order (pending outcome of litigation) in another proceeding so long as the civil order was issued in response to a complaint, petition, or motion filed by or on behalf of a person seeking protection. Reasonable notice and opportunity to be heard must be given to the person against whom the order is sought or notice and opportunity to be heard must be provided within the time required by state law and within reasonable time after the order is issued.

Temporary ex parte orders (issued for ten days or less) are not allowed entry. A magistrate’s order for emergency protection (expires on the 31st day) meets entry criteria. Any order issued for less than thirty (30) days is not allowed entry.

1.2 RECORD RETENTION

A record will remain active until action is taken by the entering agency to remove the record or until the order expires. Five days prior to an order’s expiration date, an unsolicited $.P. administrative message will be sent to the ORI of record. If no action is taken to modify the expiration date (EXP), the record will expire after the fifth day. Inactive records (cleared and expired) will be maintained on-line for the remainder of the year plus five (5) more years. If the record is non-expiring, the record will remain on file until action is taken by the entering agency to remove the record.

1.3 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the Protective Order File:

MKE FORMATEPO ENTER PROTECTIVE ORDERMPO MODIFY PROTECTIVE ORDERXPO CANCEL PROTECTIVE ORDERCPO CLEAR PROTECTIVE ORDERQPO QUERY PROTECTIVE ORDERZPO QUERY PROTECTIVE ORDER (TCIC 2000 RESPONSE ONLY)QW PERSONS INQUIRY (INVESTIGATIVE PURPOSES)ZW PERSONS INQUIRY (ADMINISTRATIVE/TEST PURPOSES)

Revised May, 2002 1 Version 1.1

2. PROTECTIVE ORDER TRANSACTIONS

2.1 ENTRY (EPO)

2.1.1 EXAMPLE OF ENTRY MESSAGE

EPO ENTER TCIC/NCIC PROTECTIVE ORDER RECORD – PAGE ONE OPTIONAL: ENTRY INTO TEXAS-ONLY: _ MAGISTRATE ORDER: _ (MARK WITH 'X') MKE: EPO- _ ORI: TX DPS0000 OCA 123TESTPO___________ PNO 123TESTPO______ PCO 01CTI: TX _______ CTD: 33RD JUDICIAL DISTRICT COURT ISD: 03022002 EXP: 03022003 RESPONDENT INFORMATION: RPP: 01 CMC: __ NOA: _ NAM: TEST,RECORD___________________ SEX: M RAC: W ETH: N POB: TX DOB: 01011961HGT: 601 WGT: 160 SKN: FAR EYE: BLU HAI: BRO SID: TX 01234567 FBI: _________ SMT: TAT L SHLD FPC: ____________________ MNU: PI - 01234567____ SOC: 555555555OLN: 12345678____________ OLS: TX OLY: 2005 ADR: 1234 STREET NAME HERE_________ADC: CITY________________ ADS: TX ADZ: 111112222 ACC: 227 LIC: 1234BC____ LIS: TX LIY: 2002 LIT: TK VIN: 123TESTVINFAKE123___ VYR: 2002 VMA: DODG____________________ VMO: R15 VST: PK VCO: BLK____

EPO2 PROTECTED PERSON INFORMATION -- PAGE TWO PPN: TEST,SALLY____________________ PSX: F PPR: W PPE: N PPB: 01011962 PPA: 1234 STREET NAME HERE_________ PPC: CITY________________ PST: TX PCC: 227PPZ: 111111111 PEN: EMPLOYER NAME HERE__ PEA: EMPLOYER ADDRESS HERE________ PEC: CITY________________ PES: TX PEZ: 111111111 MIS TEST MISCELLANEOUS FIELD____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________CONTROL FIELD: __________

2.1.2 ADDITIONAL GUIDELINES FOR ENTRY

2.1.2a AGENCY JURISDICTION

The law enforcement agency having jurisdiction over the protected person’s residence is responsible for the record entry, e.g., if the protected person resides within the incorporated city limits, the record should be entered by the police department or if the protected person resides outside the incorporated city limits, the sheriff’s office is responsible for the entry.

Revised May, 2002 2 Version 1.1

2.1.2b MESSAGE KEY CODE

The NCIC 2000 Operating Manual indicates the message key code to enter a temporary protective order is "ETO". In order to enter a temporary order, Texas direct TLETS member agencies must use the Enter Protective Order transaction code ("EPO") and place the letter "X" in the space marked "Magistrate Order". TLETS will translate the message key as "ETO" when the transaction is forwarded to NCIC 2000.

Texas direct TLETS member agencies may enter a protective order into TCIC only by using the Enter Protective Order transaction code ("EPO") and placing a letter "X" in the space marked "Texas Only".

2.1.3 MESSAGE FIELD CODES AND EDITS

In addition to the message field codes and edits outlined in the NCIC 2000 Operating Manual for Protective Order entries, there are additional message field codes and edits for entry by Texas users, which are as follows:

ACC Respondent’s Address County Code

Mandatory. County code of respondent’s residence at the time the protective order is issued. Refer to the County Code List for 3 digit codes.

ADC Respondent’s Address City

Mandatory. City of residence used by respondent at the time the protective order is issued.

ADR Respondent’s Address Street

Mandatory. Street address used by respondent at the time the protective order is issued. If the only address known is the same as the Protected Person’s or is based on Drivers License data, this can be entered with a notation made in the MIS field that "respondent’s address listed is the last known address".

ADS Respondent’s Address State

Mandatory. State or Country of residence used by the respondent at the time the protective order is issued. Refer to NCIC 2000 Code Manual, State and Country Data Codes, for coding.

ADZ Respondent’s Address Zip Code

Mandatory. Zip code of residence used by respondent at the time the protective order is issued.

CTD Court Name Mandatory. Name of court issuing the protective order.

ETH Respondent’s Ethnicity Optional. Ethnic origin of respondent.Valid values: H = Hispanic; N = Non-Hispanic;U = Unknown

PCC Protected Person’s County Code

Mandatory. County code of protected person’s residence at the time the protective order is issued. Refer to the County Code List for 3 digit codes.

Revised May, 2002 3 Version 1.1

PEA Protected Person’s Employment Address

Optional set. Street address of employment at the time the protective order is issued.

PEC Protected Person’s Employment City

Optional set. City of employment at the time the protective order is issued

PEN Protected Person’s Employment Name

Optional set. Name of place of employment at the time the protective order is issued.

PES Protected Person’s Employment State

Optional set. State or Country of employment at the time the protective order is issued. Refer to NCIC 2000 Code Manual, State and Country Data Codes, for coding.

PEZ Protected Person’s Employment Zip Code

Optional set. Zip code of place of employment at the time the protective order is issued.

PPA Protected Person’s Address

Optional set. Street address used at the time the protective order is issued.

PPB Protected Person’s Date of Birth

Conditional within set. Protected person’s date of birth. Must be entered if PPN is entered.

PPC Protected Person’s Address City

Optional set. City of residence of protected person at the time the protective order is issued.

PPE Protected Person’s Ethnicity

Optional. Ethnic origin of protected person. Valid values: H = Hispanic; N = Non-Hispanic; U = Unknown

PPN Protected Person’s Name

Conditional set. Name of protected person.

PPZ Protected Person’s Address Zip

Optional set. Zip code used by individual at the time the protective order is issued.

PST Protected Person’s Address State

Optional set. State or Country of residence at the time the protective order is issued.

RPP Respondent’s Relationship to Protected Person

Mandatory. Valid values: 01 = Spouse 12 = Other Family 02 = Common-law spouse Member 03 = Parent 13 = Roommate04 = Sibling 14 = Foster Parent05 = Child 15 = Foster Child06 = Grandparent 16 = Ex-spouse07 = Grandchild 17 = Other (Explain 08 = In-law in MIS field) 09 = Step-parent *18 = Date Violence10 = Step-child *19 = Hate Crime11 = Stepsibling *New RPP values with TCIC 2000.

Revised May, 2002 4 Version 1.1

2.2 MODIFY (MPO)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE

MPO MODIFY PROTECTIVE ORDER RECORD - PAGE ONE TEXAS ONLY: _ MAGISTRATE _ NAM TEST,RECORD___________________ OCA 123TESTPO___________ PNO _______________ORI: TX DPS0000 ENTER NEW DATA; '*' DELETES OPTIONAL FIELD. RPP __ CMC __ NOA _MKE: E ___ ORI: TX _______ OCA: ____________________ PNO _______________ PCO __CTI: TX _______ CTD: ______________________________ ISD: MMDDYYYY EXP: MMDDYYYYNAM: ______________________________ SEX: _ RAC: _ ETH: _ POB: __ DOB: MMDDYYYYHGT: ___ WGT: ___ SKN: LGT EYE: BRO HAI: ___ SID: TX ________ FBI: _________ SMT: __________ FPC: ____________________ MNU: __ - ____________ SOC: _________OLN: ____________________ OLS: __ OLY: YYYY ADR: ______________________________ADC: ____________________ ADS: __ ADZ: _________ ACC: ___ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______

MPO2 MODIFY PROTECTIVE ORDER RECORD -- PAGE TWO PPN: ______________________________ PSX: _ PPR: _ PPE: _ PPB: MMDDYYYY PPA: ______________________________ PPC: ____________________ PST: __ PCC: ___PPZ: _________ PEN: ____________________ PEA: ______________________________ PEC: ____________________ PES: __ PEZ: _________ MIS: ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________VLN: ______________________________ CONTROL FIELD: __________

2.2.2 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION

For NCIC/TCIC 2000 validation, a Name of Validator (VLN) may be added to a protective order record to indicate that the record has met the criteria for validation. When the VLN is entered, TCIC and NCIC 2000 store the current date in the record as the Date of Last Validation (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected. The acknowledgment for the modification message containing the VLN will indicate the record has been validated. The VLN can be in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc. The NCIC 2000 policy requiring "on-line" validation has been suspended until further notice.

Revised May, 2002 5 Version 1.1

2.2.3 ADDITIONAL GUIDELINES FOR MODIFICATION

2.2.3a MESSAGE KEY CODE

The NCIC 2000 Operating Manual indicates the message key code to modify a temporary protective order is "MTO". In order to modify a temporary order, Texas direct TLETS member agencies must use the Modify Protective Order transaction code ("MPO") and place the letter "X" in the space marked "Magistrate Order". TLETS will translate the message key as "MTO" when the transaction is forwarded to NCIC 2000.

To modify a TCIC 2000 only temporary protective order, Texas direct TLETS member agencies must use the Modify Protective Order transaction code ("MPO") and place the letter "X" in the space marked "Texas Only".

2.3 CANCEL (XPO)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE

XPO CANCEL PROTECTIVE ORDER RECORD ORI: TX DPS0000 MAGISTRATE ORDER: _ NAM: TEST,RECORD___________________ OCA: 123TESTPO___________ OR PNO: _______________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CPO' IF COURT CANCELED ORDER.

2.3.2 ADDITIONAL GUIDELINES FOR CANCELLATION

2.3.2a MESSAGE KEY CODE

The NCIC 2000 Operating Manual indicates the message key code to cancel a temporary protective order is "XTO". In order to cancel a temporary order, Texas direct TLETS member agencies must use the Cancel Protective Order transaction code ("XPO") and place the letter "X" in the space marked "Magistrate Order". TLETS will translate the message key as "XTO" when the transaction is forwarded to NCIC 2000.

Revised May, 2002 6 Version 1.1

2.4 INQUIRY (QPO)

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QPO PROTECTIVE ORDER RECORD INQUIRY ORI: TX DPS0000 INQUIRE USING FIELDS IN ONE GROUP, ONLY: 1. NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 01011961 SOC: 555555555 MNU: __ - ____________ FBI _________ OLN ____________________ LIC: __________ LIS __ VIN ____________________ VMA ________________________ RELATED SEARCH HIT: _ EXPANDED NAME SEARCH: _ 2. NAM: ______________________________ OCA: ____________________ 3. NAM: ______________________________ PNO: _______________ 4. NIC: __________ CONTROL FIELD: __________

2.4.2 ADDITIONAL GUIDELINES FOR INQUIRY

2.4.2a PROTECTIVE ORDER INQUIRIES

The TLETS Protective Order inquiry format (transaction code "QPO" or "ZPO") allows an inquiry to be made by:1. NAM and one, more than one, or all of the following alphanumeric identifiers:

DOB (including month, day, year), FBI, SOC, OLN, MNU, LIC (with LIS), VMA (with VIN) or VIN.

2. NAM and OCA only (exact spelling of the name contained in the record is required).3. NAM and PNO only (exact spelling of the name contained in the record is required).4. NIC only.

This means that an inquiry can be made on multiple identifiers in one format. Inquiries made with transaction code "ZPO" will search the TCIC 2000 files only. Protective order records will also be returned in response to a "QW" or "ZW" inquiry.

2.5 CLEAR (CPO)

2.5.1 EXAMPLE OF CLEAR MESSAGE

CPO CLEAR PROTECTIVE ORDER RECORD ORI: TX DPS0000 MAGISTRATE ORDER: _ NAM: TEST,RECORD___________________ OCA: 123TESTPO___________ OR PNO: _______________ CONTROL FIELD: __________ USE THIS FORMAT IF ORDER WAS CANCELED. USE 'XPO' TO CANCEL INVALID RECORD.

Revised May, 2002 7 Version 1.1

2.5.2 ADDITIONAL GUIDELINES FOR CLEAR

2.5.2a MESSAGE KEY CODE

The NCIC 2000 Operating Manual indicates the message key code to clear a temporary protective order is "CTO". In order to clear a temporary order, Texas direct TLETS member agencies must use the Clear Protective Order transaction code ("CPO") and place the letter "X" in the space marked "Magistrate Order". TLETS will translate the message key as "CTO" when the transaction is forwarded to NCIC 2000.

2.5.2b CLEARED PROTECTIVE ORDER STATUS

When a protective order record is cleared, its status will be changed to inactive. During this period of time, the record can be accessed via the "QPO" transaction. Inactive records cannot be modified.

3. SUPPLEMENTAL DATA TRANSACTIONS

3.1 INTRODUCTION

Texas direct TLETS member agencies must add supplemental data to a protective order record using transaction codes "ENPO" and "ENPT" depending upon the type of additional identifier being added. Before a supplemental field may be entered, that field must be filled in the base record. If that field was not filled upon entry, a modification message (transaction code "MPO") must be used to add that field information to the base record before supplemental data can be added. Supplemental data cannot be modified. If there is an error in the supplemental data added to a base record, the supplemental data must be canceled and re-entered. Texas direct TLETS member agencies cancel supplemental data using transaction codes "XNPO" and "XNPT" depending upon the type of additional identifier being removed.

3.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for Supplemental Data transactions in the Protective Order File:

MKE FORMATENPO ENTER SUPPLEMENTAL RESPONDENT IDENTIFIERS, PCO'S,

CMC'S AND PROTECTED PERSONS ENPT ENTER TEXAS SUPPLEMENTAL PROTECTIVE ORDER ADDRESS DATAXNPO CANCEL SUPPLEMENTAL PROTECTIVE ORDER RECORDXNPT CANCEL TEXAS SUPPLEMENTAL PROTECTIVE ORDER ADDRESS DATA

Revised May, 2002 8 Version 1.1

3.3 ENTRY (ENPO, ENPT)

3.3.1 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENPO)

ENPO ENTER SUPPLEMENTAL PROTECTIVE ORDER RECORD ORI: TX DPS0000 NAM: TEST,RECORD___________________ SELECT OCA: 123TESTPO___________ OR PNO: _______________ ENTER SUPPLEMENTAL INFORMATION BELOW: AKA: TESTING,RECORD________________ AKA: ______________________________ DOB: MMDDYYYY DOB: MMDDYYYY SMT: SC CHEST__ SMT: __________ SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ __ __ __ __ __ PCO __ __ __ __ __ __ PPN TESTING,RECORD JR___________PSX: M PPR: W PPE: N PPB: 05051981 PCC: 227 CONTROL FIELD: __________

3.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENPT)

ENPT ENTER TEXAS SUPPLEMENTAL PROTECTIVE ORDER DATA ORI: TX DPS0000 NAM: TEST,RECORD___________________ SELECT OCA: 123TESTPO___________ OR PNO: _______________ PPN: TEST,RECORD JR________________ PPB: 05051981 ENTER TEXAS SUPPLEMENTAL PROTECTED PERSON DATA BELOW: PPA: ______________________________ PPC: ____________________ PST: __ PPZ: _________ PEN: ____________________ PEA: ______________________________ PEC: ____________________ PES: __ PEZ: _________ CCN: SECOND CHILD CARE___ CCA: SECOND CHILD CARE ADDRESS_____ CCC: CITY________________ CCS: TX CCZ: 777777777 CONTROL FIELD: __________

3.3.3 MESSAGE FIELD CODES AND EDITS

In addition to the message field codes and edits outlined in the NCIC 2000 Operating Manual for Protective Order Supplemental entries, there are additional message field codes and edits for supplemental entry to Protective Orders by Texas direct TLETS member agencies, which are as follows:

CCA Protected Child’sChild Care Facility Street Address

Optional set. Street address of child care facility or school used by protected child at the time the protective order is issued. If more than one facility is protected, use the ENPT format to add additional child care facility addresses.

Revised May, 2002 9 Version 1.1

CCC Protected Child’sChild Care Facility City

Optional set. City of child care facility or school used by protected child at the time the protective order is issued.

CCN Protected Child’sChild Care Facility Name

Optional set. Name of child care facility or school used by protected child at the time the protective order is issued.

CCS Protected Child’sChild Care Facility State

Optional set. State or Country of child care facility or school used by protected child at the time the protective order is issued. Refer to the NCIC 2000 Code Manual, State and Country Data Codes, for coding.

CCZ Protected Child’sChild Care FacilityZip Code

Optional set. Zip code of child care facility or school used by protected child at the time the protective order is issued.

3.4 CANCEL (XNPO, XNPT)

3.4.1 EXAMPLE OF CANCEL SUPPLEMENTAL DATA (XNPO)

XNPO CANCEL SUPPLEMENTAL PROTECTIVE ORDER RECORD ORI: TX DPS0000 NAM: TEST,RECORD___________________ SELECT OCA: 123TESTPO___________ OR PNO: _______________ ENTER SUPPLEMENTAL INFORMATION TO BE CANCELED BELOW: AKA: ______________________________ AKA: ______________________________ DOB: MMDDYYYY DOB: MMDDYYYY SMT: SC CHEST__ SMT: __________ SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ __ __ __ __ __ PCO __ __ __ __ __ __ PPN ______________________________PSX: _ PPR: _ PPE: _ PPB: MMDDYYYY PCC: ___ CONTROL FIELD: __________

3.4.2 EXAMPLE OF CANCEL SUPPLEMENTAL DATA (XNPT)

XNPT CANCEL TEXAS SUPPLEMENTAL PROTECTIVE ORDER DATA ORI: TX DPS0000 NAM: TEST,RECORD___________________ SELECT OCA: 123TESTPO___________ OR PNO: _______________ PPN: TEST,RECORD JR________________ PPB: 05051981 ENTER TEXAS SUPPPLEMENTAL PROTECTED PERSON DATA TO BE CANCELED BELOW: PPA: ______________________________ PPC: ____________________ PST: __ PPZ: _________ PEN: ____________________ PEA: ______________________________ PEC: ____________________ PES: __ PEZ: _________ CCN: SECOND CHILD CARE___ CCA: SECOND CHILD CARE ADDRESS___ CCC: CITY________________ CCS: TX CCZ: 777777777 CONTROL FIELD: __________

Revised May, 2002 10 Version 1.1

4. COUNTY CODE LIST

COUNTY CODE COUNTY CODE COUNTY CODEANDERSON 001 CORYELL 050 HARDEMAN 099ANDREWS 002 COTTLE 051 HARDIN 100ANGELINA 003 CRANE 052 HARRIS 101ARANSAS 004 CROCKETT 053 HARRISON 102ARCHER 005 CROSBY 054 HARTLEY 103ARMSTRONG 006 CULBERSON 055 HASKELL 104ATASCOSA 007 DALLAM 056 HAYS 105AUSTIN 008 DALLAS 057 HEMPHILL 106BAILEY 009 DAWSON 058 HENDERSON 107BANDERA 010 DEAF SMITH 059 HIDALGO 108BASTROP 011 DELTA 060 HILL 109BAYLOR 012 DENTON 061 HOCKLEY 110BEE 013 DEWITT 062 HOOD 111BELL 014 DICKENS 063 HOPKINS 112BEXAR 015 DIMMIT 064 HOUSTON 113BLANCO 016 DONLEY 065 HOWARD 114BORDEN 017 DUVAL 066 HUDSPETH 115BOSQUE 018 EASTLAND 067 HUNT 116BOWIE 019 ECTOR 068 HUTCHINSON 117BRAZORIA 020 EDWARDS 069 IRION 118BRAZOS 021 ELLIS 070 JACK 119BREWSTER 022 EL PASO 071 JACKSON 120BRISCOE 023 ERATH 072 JASPER 121BROOKS 024 FALLS 073 JEFF DAVIS 122BROWN 025 FANNIN 074 JEFFERSON 123BURLESON 026 FAYETTE 075 JIM HOGG 124BURNET 027 FISHER 076 JIM WELLS 125CALDWELL 028 FLOYD 077 JOHNSON 126CALHOUN 029 FOARD 078 JONES 127CALLAHAN 030 FORT BEND 079 KARNES 128CAMERON 031 FRANKLIN 080 KAUFMAN 129CAMP 032 FREESTONE 081 KENDALL 130CARSON 033 FRIO 082 KENEDY 131CASS 034 GAINES 083 KENT 132CASTRO 035 GALVESTON 084 KERR 133CHAMBERS 036 GARZA 085 KIMBLE 134CHEROKEE 037 GILLESPIE 086 KING 135CHILDRESS 038 GLASSCOCK 087 KINNEY 136CLAY 039 GOLIAD 088 KLEBERG 137COCHRAN 040 GONZALES 089 KNOX 138COKE 041 GRAY 090 LAMAR 139COLEMAN 042 GRAYSON 091 LAMB 140COLLIN 043 GREGG 092 LAMPASAS 141COLLINGSWORTH 044 GRIMES 093 LA SALLE 142COLORADO 045 GUADALUPE 094 LAVACA 143COMAL 046 HALE 095 LEE 144COMANCHE 047 HALL 096 LEON 145CONCHO 048 HAMILTON 097 LIBERTY 146

Revised May, 2002 11 Version 1.1

COOKE 049 HANSFORD 098 LIMESTONE 147COUNTY CODE COUNTY CODE COUNTY CODE

LIPSCOMB 148 PARMER 185 TERRELL 222LIVE OAK 149 PECOS 186 TERRY 223LLANO 150 POLK 187 THROCKMORTON 224LOVING 151 POTTER 188 TITUS 225LUBBOCK 152 PRESIDIO 189 TOM GREEN 226LYNN 153 RAINS 190 TRAVIS 227MCCULLOCH 154 RANDALL 191 TRINITY 228MCLENNAN 155 REAGAN 192 TYLER 229MCMULLEN 156 REAL 193 UPSHUR 230MADISON 157 RED RIVER 194 UPTON 231MARION 158 REEVES 195 UVALDE 232MARTIN 159 REFUGIO 196 VAL VERDE 233MASON 160 ROBERTS 197 VAN ZANDT 234MATAGORDA 161 ROBERTSON 198 VICTORIA 235MAVERICK 162 ROCKWALL 199 WALKER 236MEDINA 163 RUNNELS 200 WALLER 237MENARD 164 RUSK 201 WARD 238MIDLAND 165 SABINE 202 WASHINGTON 239MILAM 166 SAN AUGUSTINE 203 WEBB 240MILLS 167 SAN JACINTO 204 WHARTON 241MITCHELL 168 SAN PATRICIO 205 WHEELER 242MONTAGUE 169 SAN SABA 206 WICHITA 243MONTGOMERY 170 SCHLEICHER 207 WILBARGER 244MOORE 171 SCURRY 208 WILLACY 245MORRIS 172 SHACKELFORD 209 WILLIAMSON 246MOTLEY 173 SHELBY 210 WILSON 247NACOGDOCHES 174 SHERMAN 211 WINKLER 248NAVARRO 175 SMITH 212 WISE 249NEWTON 176 SOMERVELL 213 WOOD 250NOLAN 177 STARR 214 YOAKUM 251NUECES 178 STEPHENS 215 YOUNG 252OCHILTREE 179 STERLING 216 ZAPATA 253OLDHAM 180 STONEWALL 217 ZAVALA 254ORANGE 181 SUTTON 218PALO PINTO 182 SWISHER 219PANOLA 183 TARRANT 220 UNKNOWN 000PARKER 184 TAYLOR 221 OUT-OF-STATE 000

Revised May, 2002 12 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESREGISTERED SEXUAL OFFENDER FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 REGISTERED SEXUAL OFFENDER FILE OVERVIEW 1

2. REGISTERED SEXUAL OFFENDER TRANSACTIONS 12.1 INQUIRY (QXS) 1

2.1.1 EXAMPLE OF INQUIRY MESSAGE 12.1.2 REQUIREMENTS FOR INQUIRY 2

Revised July, 2002 Version 1.2

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Registered Sexual Offender File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 REGISTERED SEXUAL OFFENDER FILE OVERVIEW

State law requires DPS to maintain a central database containing sex offender registration information. If a person was under supervision as of September 1, 1997, for an offense that occurred on or after September 1, 1970, they are required to register as a sex offender. A "QXS" inquiry will allow criminal justice agencies to view limited information on registered sex offenders via TLETS. All information can be viewed via the internet on the DPS secure website at http://secure.txdps.state.tx.us. Law enforcement agencies are allowed to modify their registered sex offender records via this website. Certain information in this database is considered public information and is available via the internet on the DPS public website at http://records.txdps.state.tx.us. Agencies wishing to have access to the secure Sex Offender Register (SOR) website should contact the CJIS office at (512) 424-2478.

2. REGISTERED SEXUAL OFFENDER TRANSACTIONS

2.1 INQUIRY (QXS)

2.1.1 EXAMPLE OF INQUIRY MESSAGE

QXS SEX OFFENDER REGISTRATION INQUIRY MKE: QXS ORI:TX DPS0000 CHOOSE ONE OF THE FOLLOWING SETS OF IDENTIFIERS: 1. NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 05151955 SOC: _________ MNU: __ - ____________ FBI _________ OLN ____________________ LIC: __________ LIS __ VIN ____________________ VMA ________________________ RELATED SEARCH HIT: _ EXPANDED NAME SEARCH: _ 2. NAM: ______________________________ OCA: ____________________ 3. ZIP: _____ - ____ SOS: _ CONTROL FIELD: __________

Revised July, 2002 1 Version 1.2

2.1.2 REQUIREMENTS FOR QXS INQUIRY

The TLETS Sex Offender Registration inquiry format (transaction code "QXS") allows an inquiry to be made by:

5. NAM and one, more than one, or all of the following alphanumeric identifiers:DOB (including month, day, year), FBI, SOC, OLN, MNU, LIC (with LIS), VMA (with VIN) or VIN.

6. NAM and OCA only (exact spelling of the name contained in the record is required).7. ZIP and/or SOS (Sexual Offender Status) only.

This means that a TLETS inquiry can be made on multiple identifiers in one format. Sex Offender Registration records will also be returned in response to a "QW" or "ZW" inquiry.

Inquiries made using the "QXS" transaction code restricts the search to just the Sexual Offender Registry File and may retrieve a Sexual Offender Registry File record that is active, expired, or inactive. A "QW" inquiry searches the Sexual Offender Registry File in addition to other identifiable person files and retrieves active records only.

Revised July, 2002 2 Version 1.2

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESTDCJ CORRECTIONS TRACKING SYSTEM (CTS)

TABLE OF CONTENTS

1. INTRODUCTION 11.1 SYSTEM OVERVIEW 1

2. CTSI INQUIRY 12.1 EXAMPLE OF CTSI INQUIRY 12.2 REQUIREMENTS FOR CTSI INQUIRY 2

Revised May, 2002 Version 1.1

1. INTRODUCTION

1.1 SYSTEM OVERVIEW

TLETS agencies authorized access to TCIC CCH files may also make inquiries over TLETS regarding custody data on individuals who are currently, or formerly were, supervised by the Texas Department of Criminal Justice. This data is stored in the Corrections Tracking System which is maintained by the Texas Department of Criminal Justice (TDCJ).

This data includes demographics, sentencing, offense, and parole information. Individuals in the database include inmates, probationers, and parolees. This information is available for criminal justice purposes only. Certain data fields contain confidential information that is protected by state or federal legislation.

Inquiries may be made only from an agency or terminal that has been properly authorized. The level of access required for these CTS inquiries is the same as that for "QH" or "QR" inquiries.

Required fields are SID, PURPOSE and ATTENTION fields. The request will be sent to the CTS database at TDCJ in Huntsville, and the response will include a record return or a notice that the individual is not found in the database.

For further assistance or information regarding inmates, probationers, parolees and revocation warrants, contact the TDCJ – Parole Board in Austin at the appropriate number: Inmate Status (512) 406-5204; Probation Information (512) 305-9381; Parole Information (512) 406-5317; and Revocation or Pre-revocation Warrants at (512) 406-5469.

2. CTSI INQUIRY

2.1 EXAMPLE OF CTSI INQUIRY

CTSI CORRECTIONS TRACKING SYSTEM INQUIRY REQUESTING AGENCY DATA: ORI: TX DPS0000 CONTROL: _____ SID: TX0 1234567 PURPOSE: C ATTENTION: TITLE FIRSTNAME LASTNAME______

Revised May, 2002 1 Version 1.1

2.2 REQUIREMENTS FOR CTSI INQUIRY

ORI: Enter ORI of inquiring agency. If the requestor is from another agency, that agency’s ORI must be used. If a terminal agency is not authorized to use the other agency’s ORI, include that agency’s name in the ATTENTION field.

SID: Enter Texas SID Number

PURPOSE: Purpose Code field will only accept "C". No other purpose codes are authorized.

ATTENTION: Title and full name of individual requesting the information.For example, SGT JOE THOMAS.

CONTROL FIELD: If used, enter up to a maximum of five (5) alpha and/or numeric characters. Data entered into this field will be returned in the response from TDCJ.

Revised May, 2002 2 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESVEHICLE FILE

TABLE OF CONTENTS

1. INTRODUCTION 11.1 MESSAGE KEY (MKE) CODES 11.2 NCIC TRANSACTIONS WITH ADDITIONAL TCIC SPECIFICATIONS 11.3 TCIC 2000 ONLY TRANSACTIONS 1

2. STOLEN/FELONY VEHICLE TRANSACTIONS 22.1 ENTRY (EV, EF) 2

2.1.1 EXAMPLE OF ENTRY MESSAGE (EV) 22.1.2 EXAMPLE OF ENTRY MESSAGE (EF) 22.1.3 ADDITIONAL GUIDELINES FOR ENTRY 2

2.1.3a TEXAS APPORTIONED/DEALER LICENSE PLATES 22.1.3b OAN FIELD 32.1.3c SVIN 32.1.3d MODEL NUMBERS,

ENGINE NUMBERS, OR MOTOR NUMBERS 32.2 MODIFY (MV, MF) 4

2.2.1 EXAMPLE OF MODIFICATION MESSAGE (MV) 42.2.2 EXAMPLE OF MODIFICATION MESSAGE (MF) 42.2.3 VALIDATION GUIDELINES

FOR NCIC/TCIC 2000 MODIFICATION 52.3 CANCEL (XV, XF) 5

2.3.1 EXAMPLE OF CANCELLATION MESSAGE (XV) 52.3.2 EXAMPLE OF CANCELLATION MESSAGE (XF) 5

2.4 INQUIRY (QV) 52.4.1 EXAMPLE OF INQUIRY MESSAGE 52.4.2 ADDITIONAL MESSAGE

FIELD CODES FOR INQUIRY BY TEXAS USERS 62.4.3 ADDITIONAL GUIDELINES FOR INQUIRY 6

2.4.3a H.E.A.T. DECAL 62.5 LOCATE (LV, LF) 6

2.5.1 EXAMPLE OF LOCATE MESSAGE (LV) 62.5.2 EXAMPLE OF LOCATE MESSAGE (LF) 6

2.6 CLEAR (CV, CF) 72.6.1 EXAMPLE OF CLEAR MESSAGE (CV) 72.6.2 EXAMPLE OF CLEAR MESSAGE (CF) 7

3. ABANDONED/STORED VEHICLE TRANSACTIONS 73.1 INTRODUCTION 73.2 MESSAGE KEY (MKE) CODES 83.3 CRITERIA FOR ENTRY 83.4 RECORD RETENTION 83.5 MESSAGE FIELD CODES AND EDITS 83.6 ENTRY (ERV) 9

3.6.1 EXAMPLE OF ENTRY MESSAGE 93.6.2 ADDITIONAL MANDATORY FIELDS FOR ENTRY 9

Revised May, 2002 Version 1.1

3.7 MODIFY (MRV) 93.7.1 WHEN TO USE A MODIFICATION MESSAGE 93.7.2 EXAMPLE OF MODIFICATION MESSAGE 9

3.8 CANCEL (XRV) 103.8.1 WHEN TO USE A CANCELLATION MESSAGE 103.8.2 EXAMPLE OF CANCEL MESSAGE 103.8.3 ADDITIONAL GUIDELINES FOR CANCELLATION 10

3.8.3a RPP FIELD 104. H.E.A.T. VEHICLES 10

4.1 INTRODUCTION 104.2 MESSAGE KEY (MKE) CODES 124.3 CRITERIA FOR ENTRY 124.4 RECORD RETENTION 124.5 MESSAGE FIELD CODES AND EDITS 124.6 VALIDATION 134.7 CRITERIA FOR REJECTING DUPLICATE RECORDS 134.8 ENTRY (EHV) 14

4.8.1 EXAMPLE OF ENTRY MESSAGE 144.8.2 ADDITIONAL GUIDELINES FOR ENTRY 14

4.9 MODIFY (MHV) 144.9.1 WHEN TO USE A MODIFICATION MESSAGE 144.9.2 EXAMPLE OF MODIFICATION MESSAGE 14

4.10 CANCELLATION (XHV) 154.10.1 EXAMPLE OF CANCELLATION MESSAGE 15

4.11 INQUIRY (QHV) 154.11.1 EXAMPLE OF INQUIRY MESSAGE 15

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Vehicle File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the Stolen/Felony Vehicle File:

MKE FORMATEV ENTER STOLEN VEHICLE RECORDEF ENTER FELONY VEHICLE RECORDMV MODIFY STOLEN VEHICLE RECORDMF MODIFY FELONY VEHICLE RECORDXV CANCEL STOLEN VEHICLE RECORDXF CANCEL FELONY VEHICLE RECORDLV LOCATE STOLEN VEHICLE RECORDLF LOCATE FELONY VEHICLE RECORDCV CLEAR STOLEN VEHICLE RECORDCF CLEAR FELONY VEHICLE RECORD

1.2 NCIC TRANSACTIONS WITH ADDITIONAL TCIC SPECIFICATIONS

MKE FORMATCV CLEAR STOLEN VEHICLE RECORDLV LOCATE STOLEN VEHICLE RECORDQV QUERY VEHICLE (INVESTIGATIVE PURPOSES)ZV QUERY VEHICLE (ADMINISTRATIVE/TEST PURPOSES)

1.3 TCIC 2000 ONLY TRANSACTIONS

MKE FORMATERV ENTER ABANDONED/STORED VEHICLE RECORDMRV MODIFY ABANDONED/STORED VEHICLE RECORDXRV CANCEL ABANDONED/STORED VEHICLE RECORDEHV ENTER H.E.A.T. VEHICLE RECORDMHV MODIFY H.E.A.T. VEHICLE RECORDXHV CANCEL H.E.A.T. VEHICLE RECORD

Revised May, 2002 1 Version 1.1

2. STOLEN/FELONY VEHICLE TRANSACTIONS

2.1 ENTRY (EV, EF)

2.1.1 EXAMPLE OF ENTRY MESSAGE (EV)

EV ENTER STOLEN VEHICLE RECORD MKE: EV- A ORI: TX DPS0000 LIC: ABC123____ LIS: TX LIY: 2002 LIT: PC VIN: TEST123VIN__________ VYR: 2001 VMA: FORD____________________ VMO: MUS VST: 2D VCO: GRY____ DOT: 03022002 OCA:TESTOCA_____________ LKI: _________ LKA: ____________________ OAN: ____________________ MIS: DENT ON RIGHT FENDER____________________________________________________________________________________________________________________________________________________________________________ NOA: Y CONTROL FIELD: __________

2.1.2 EXAMPLE OF ENTRY MESSAGE (EF)

EF ENTER FELONY VEHICLE RECORD MKE: EF- _ ORI: TX DPS0000 LIC: ABC123____ LIS: TX LIY: 2002 LIT: PC VIN: TEST123VIN4567890___ VYR: 1998 VMA: CHEV____________________ VMO: BLZ VST: LL VCO: BLK____ DOT: 03022002 OCA: TESTOCA_____________ LKI: _________ LKA: ____________________ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ NOA: _ CONTROL FIELD: __________

2.1.3 ADDITIONAL GUIDELINES FOR ENTRY

In addition to the information outlined in the NCIC 2000 Operating Manual, Vehicle File, page 15, regarding additional guidelines for entry, the following are applicable for Texas Users:

2.1.3a TEXAS APPORTIONED/DEALER LICENSE PLATES

Texas Apportioned and Dealer license plates are issued annually. The same license plate number may be issued to more than one vehicle, but with a different year of expiration. Therefore, when entering or inquiring on a Texas Apportioned or Dealer plate, the year of expiration must be verified.

Revised May, 2002 2 Version 1.1

Paper Texas Dealer license plates are not allowed entry into TCIC/NCIC 2000 because the number on each plate is not unique to that plate.

Metal Texas dealer license plates can be entered if they fall within the following range of numbers:

1D0001 to 9D9999

The Motor Vehicle Division of the Texas Department of Transportation has advised that all other dealer plates are non-unique. Therefore, they are not allowed entry into TCIC/NCIC 2000.

2.1.3b OAN FIELD

The Owner Applied Number field (OAN) may not be used by Texas agencies unless the VIN field has been filled. If there is an OAN, but no VIN available, then the OAN must be placed in the VIN field with a notation in the MIS field indicating that the "VIN is (an) OAN". Texas Users cannot cancel or clear using an OAN or NIC.

2.1.3c SVIN

Many out-of-synchronization vehicle records are trailers entered with a 17 character non-conforming VIN. NCIC 2000 edits the record using the VIN edit and check digit system. If the trailer entry is allowed by TCIC 2000 but rejected by NCIC 2000, the TCIC 2000 record must be canceled and re-entered into TCIC 2000 and NCIC 2000 by entering "SVIN" as the first item in the miscellaneous (MIS) field. This is the only time an agency may use the "SVIN" code without prior authorization from TCIC Operations. If an attempt to enter any other type of vehicle into TCIC/NCIC 2000 results in the same reject message, contact the TCIC Control Center at "CRDP", (512) 424-2088, or 1-866 266-TCIC (8242) for assistance.

2.1.3d MODEL NUMBERS, ENGINE NUMBERS, OR MOTOR NUMBERS

Model numbers are not unique. Model numbers should be entered in the MIS field. Model numbers are not to be entered in the VIN and OAN fields of Stolen Vehicle records.

An engine or motor number may be entered into the OAN field if the VIN field is already filled. In this case, insert the notation "OAN IS A MOTOR NUMBER" or "OAN IS AN ENGINE NUMBER" in the MIS field.

Revised May, 2002 3 Version 1.1

2.2 MODIFY (MV, MF)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE (MV)

MV MODIFY STOLEN VEHICLE RECORD ORI: TX DPS0000 SELECT LIC: ABC123____ OR VIN: ____________________ OCA: TESTOCA_____________ ENTER NEW INFORMATION BELOW. USE '*' TO DELETE OPTIONAL FIELDS. MKE: EV- _ ORI: TX _______ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: BLU____ DOT: MMDDYYYY OCA: ____________________ LKI: _________ LKA: ____________________ OAN: ____________________ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ NOA: _ VLN: ______________________________ CONTROL FIELD: __________

2.2.2 EXAMPLE OF MODIFICATION MESSAGE (MF)

MF MODIFY FELONY VEHICLE RECORD ORI: TX DPS0000 SELECT LIC: ABC123____ OR VIN: ____________________ OCA: TESTOCA_____________ ENTER NEW INFORMATION BELOW. USE '*' TO DELETE OPTIONAL FIELDS. MKE: EF- _ ORI: TX _______ LIC: ABC123____ LIS: TX LIY: 2003 LIT: PC VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ DOT: MMDDYYYY OCA: ____________________ LKI: _________ LKA: ____________________ MIS: VEHICLE USED IN HOMICIDE____________________________________________________________________________________________________________________________________________________________________________ NOA: _ VLN: ______________________________ CONTROL FIELD: __________

2.2.3 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION

For NCIC/TCIC 2000 validation, a Name of Validator (VLN) may be added to a vehicle record to indicate that the record has met the criteria for validation. When the VLN is entered, TCIC 2000 and NCIC 2000 store the current date in the record as the Date of Last Validation (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected. The acknowledgment for the modification message containing the VLN will indicate the record has been validated. The VLN can be in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc. The NCIC 2000 policy requiring "on-line" validation has been suspended until further notice.

Revised May, 2002 4 Version 1.1

2.3 CANCEL (XV, XF)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE (XV)

XV CANCEL STOLEN VEHICLE RECORD ORI: TX DPS0000 SELECT ONE: LIC: ABC123____ OR VIN: ____________________ OCA: TESTOCA_____________ RPP: NOT STOLEN___________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CV' IF VEHICLE WAS RECOVERED.

2.3.2 EXAMPLE OF CANCELLATION MESSAGE (XF)

XF CANCEL FELONY VEHICLE RECORD ORI: TX DPS0000 SELECT ONE: LIC: ABC123____ OR VIN: ____________________ OCA: TESTOCA_____________ RPP: CASE DROPPED_________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CF' IF VEHICLE WAS RECOVERED.

2.4 INQUIRY (QV)

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QV VEHICLE INQUIRY MKE: QV- _ ORI: TX DPS0000 LIC: ABC123____ LIS: TX VIN: ____________________ VMA: ________________________ NIC: __________ RELATED SEARCH HIT: N IS THIS QUERY DUE TO A DISPLAYED H.E.A.T. DECAL? Y REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZV' FOR ADMIN/TEST INQUIRY.

Revised May, 2002 5 Version 1.1

2.4.2 ADDITIONAL MESSAGE FIELD CODES FOR INQUIRY BY TEXAS USERS

Field Name RequirementsMessage Field

Code Field Length Data Type

H.E.A.T. Decal Optional HDN 1-1Alphabetic

Y=Stopped due to H.E.A.T. decalN=Not stopped due to H.E.A.T. decal

2.4.3 ADDITIONAL GUIDELINES FOR INQUIRY

2.4.3a H.E.A.T. DECAL

This field should be used to indicate whether or not the query is due to a displayed H.E.A.T. decal. Place a "Y" for yes or "N" for no. If the H.E.A.T. decal field is not filled, it will default to "N".

2.5 LOCATE (LV, LF)

2.5.1 EXAMPLE OF LOCATE MESSAGE (LV)

LV LOCATE STOLEN VEHICLE RECOVERING AGENCY'S ORI: TX 0000000 SELECT ONE: LIC: ABC123____ OR VIN: ____________________ OCA IN THE RECORD: TESTOCA_____________ DATE OF RECOVERY: 03022002 IS THIS TRANSACTION DUE TO A DISPLAYED H.E.A.T. DECAL? Y RECOVERING AGENCY'S CASE NUMBER: ____________________ RPP: HIT NCIC 20020302____ NPA: 1__ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________

2.5.2 EXAMPLE OF LOCATE MESSAGE (LF)

LF LOCATE FELONY VEHICLE RECOVERING AGENCY'S ORI: TX 0000000 SELECT ONE: LIC: ABC123____ OR VIN: ____________________ OCA IN THE RECORD: TESTOCA_____________ DATE OF RECOVERY: 03032002 RECOVERING AGENCY'S CASE NUMBER: OCA TEST____________ RPP: HIT STATE 20020303___ NPA: 2__ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________

Revised May, 2002 6 Version 1.1

2.6 CLEAR (CV, CF)

2.6.1 EXAMPLE OF CLEAR MESSAGE (CV)

CV CLEAR STOLEN VEHICLE RECORD ORI: TX DPS0000 SELECT ONE: LIC: ABC123____ OR VIN: ____________________ OCA: TESTOCA_____________ DATE OF RECOVERY: 03022002 IS THIS TRANSACTION DUE TO A DISPLAYED H.E.A.T. DECAL? Y IF THE VEHICLE WAS RECOVERED BY AN AGENCY OTHER THAN THE ENTERING AGENCY, AND THE RECOVERING AGENCY HAS NOT PLACED A LOCATE ON THE RECORD: RECOVERING AGENCY ORI: _________ RECOVERING AGENCY OCA:____________________ RPP: HIT NCIC 20020302____ NPA: 1__ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF VEHICLE RECOVERED. USE 'XV' TO CANCEL INVALID RECORD.

2.6.2 EXAMPLE OF CLEAR MESSAGE (CF)

CF CLEAR FELONY VEHICLE RECORD ORI: TX DPS0000 SELECT ONE: LIC: ABC123____ OR VIN: ____________________ OCA: TESTOCA_____________ DATE OF RECOVERY: 03032002 IF THE VEHICLE WAS RECOVERED BY AN AGENCY OTHER THAN THE ENTERING AGENCY, AND THE RECOVERING AGENCY HAS NOT PLACED A LOCATE ON THE RECORD:RECOVERING AGENCY ORI: _________ RECOVERING AGENCY OCA:____________________RPP: HIT STATE 20020303___ NPA: 2__ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF VEHICLE RECOVERED. USE 'XF' TO CANCEL INVALID RECORD.

3. ABANDONED/STORED VEHICLE TRANSACTIONS

3.1 INTRODUCTION

For TCIC 2000 purposes, an Abandoned/Stored Vehicle is a vehicle that is stored on police property or in a licensed storage facility. This is a TCIC 2000 only file.

Revised May, 2002 7 Version 1.1

3.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE’s for Abandoned/Stored Vehicles:

MKE FORMATERV ENTER ABANDONED/STORED VEHICLEMRV MODIFY ABANDONED/STORED VEHICLEXRV CANCEL ABANDONED/STORED VEHICLEQV QUERY VEHICLE (INVESTIGATIVE PURPOSES)ZV QUERY VEHICLE (ADMINISTRATIVE/TEST PURPOSES)

3.3 CRITERIA FOR ENTRY

The Abandoned/Stored Vehicle file should be used when an agency stores a vehicle on police property or in a licensed storage facility or when an agency is notified by a licensed storage facility that they have received a vehicle for storage. Entry of a vehicle into this file should only be used after a "QV" inquiry produces no records and the registered owner of the vehicle cannot be contacted.

When entering vehicles stored in state-licensed facilities, the license number issued by the Texas Department of Transportation for that facility should be placed in the first nine characters of the miscellaneous field (MIS), for example, 50000VSF. This is the format that the Texas Department of Transportation uses when issuing numbers to the storage facilities.

3.4 RECORD RETENTION

Abandoned/Stored Vehicle File records remain in TCIC 2000 one year from the date of entry. Agencies are not notified when the records are purged from the file.

3.5 MESSAGE FIELD CODES AND EDITS

For Abandoned/Stored Vehicles, there are additional Texas message field codes and edits which are as follows:

PND Name of Licensed Storage FacilityMust be the NAME of the licensed storage facility, not the phone number, address or VSF number.

Revised May, 2002 8 Version 1.1

3.6 ENTRY (ERV)

3.6.1 EXAMPLE OF ENTRY MESSAGE

ERV ENTER ABANDONED/STORED VEHICLE RECORD ORI: TX DPS0000 LIC: LIC123____ LIS: TX LIY: 2000 LIT: PC VIN: 123TESTVIN45677894___ VYR: 2000 VMA: HOND___________________VMO: ACC VST: 2D VCO: RED____ DOR: 02062001 OCA: OCAERV______________ MIS: TEST MIS ERV FOR DATA STREAM ________________________________________________________________________________________________________________________________________________________________________ PND: PND TEST____________ IS THIS TRANSACTION DUE TO A DISPLAYED H.E.A.T. DECAL? Y LKI: _________ LKA: ___________________ NOA: _CONTROL FIELD: TEST

3.6.2 ADDITIONAL MANDATORY FIELDS FOR ENTRY

In addition to the mandatory fields outlined in the NCIC 2000 Operating Manual, the PND field is considered mandatory when entering an abandoned/stored vehicle into TCIC 2000.

3.7 MODIFY (MRV)

3.7.1 WHEN TO USE A MODIFICATION MESSAGE

Modification of a record is restricted to the agency that entered the record. A modification message is used to add, delete, or change data in an active Abandoned/Stored Vehicle record.

3.7.2 EXAMPLE OF MODIFICATION MESSAGE

MRV MODIFY ABANDONED/STORED VEHICLE RECORD ORI: TX DPS0000 SELECT ONE: LIC: LIC123____ OR VIN: ____________________ OCA: OCAERV______________ PUT NEW INFORMATION BELOW. USE '*' TO DELETE AN OPTIONAL FIELD ORI: TX _______ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: RED/BLU DOR: MMDDYYYY OCA: ____________________ PND: DPS IMPOUND_________ LKI: _________ LKA: ____________________ NOA: _ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

Revised May, 2002 9 Version 1.1

3.8 CANCEL (XRV)

3.8.1 WHEN TO USE A CANCELLATION MESSAGE

Cancellation is restricted to the agency that entered the record. A cancellation message should be used after ownership has been determined, if the record was entered in error, or the storage facility released the vehicle.

3.8.2 EXAMPLE OF CANCELLATION MESSAGE

XRV CANCEL ABANDONED/STORED VEHICLE ORI: TX DPS0000 SELECT ONE: LIC: LIC123____ OR VIN: ____________________ OCA: OCAERV______________ RPP: OWNER CLAIMED_______ CONTROL FIELD: __________

3.8.3 ADDITIONAL GUIDELINES FOR CANCELLATION

3.8.3a RPP FIELD

When canceling an Abandoned/Stored Vehicle record from TCIC 2000, users are expected to enter the Reason for Property Record Removal (RPP). Valid values are AUCTION, TITLE TRANSFERRED, OWNER CLAIMED, or OTHER MEANS.

4. H.E.A.T. VEHICLES

4.1 INTRODUCTION

The Texas H.E.A.T. program was developed by DPS under the direction and funding of the Texas Automobile Theft Prevention Authority as a result of Texas Revised Civil Statutes, Article 4413(37). Texas H.E.A.T. or Help End Auto Theft, is a voluntary statewide automobile registration program designed to help reduce auto theft in Texas. As such, this program will be primarily a deterrent to auto theft rather than an apprehension tool.

Revised May, 2002 10 Version 1.1

To enroll, the vehicle owner signs a registration form either via the Internet, mail order brochure or with any participating law enforcement agency stating that their vehicle may be stopped between the hours of 1:00 a.m. and 5:00 a.m. anywhere in Texas to verify ownership. Vehicle owners participating in this program may also voluntarily extend the authority to a peace officer to stop a registered vehicle whenever that vehicle is about to cross the Mexico border directly from Texas. Color-coded decals are placed on the vehicle to indicate registration in the program. A white front decal indicates the owner consents to a stop of the registered vehicle at the Texas/Mexico border twenty-four hours a day. A yellow front decal indicates the owner does not consent to a stop of the vehicle at the Texas/Mexico border, except between the hours of 1:00 a.m. and 5:00 a.m. Both colors of front decals indicate that an officer has the authority to stop the registered vehicle between the program hours of 1:00 a.m. and 5:00 a.m. anywhere in Texas to verify ownership. H.E.A.T. registration does not prevent the owner (or anyone to whom the owner grants permission) from driving the vehicle during the program hours of enforcement, but it does give the owner’s consent for any peace officer to stop the registered vehicle under the above stated conditions. The front decal bears a serial number that will correspond to the TCIC 2000 H.E.A.T. vehicle record. There is only one type of rear decal. It has a white background and no numbers.

The Texas H.E.A.T. vehicle file is to be used when a vehicle is registered in the Texas H.E.A.T. Program. The Texas H.E.A.T. vehicle file is maintained in TCIC 2000 only. Local agencies are responsible for their own H.E.A.T. vehicle entries. Entry delay should not exceed 48 hours after registration. As with all TCIC 2000 entries, the record entry must be double-checked for accuracy by a second person. TXDOT registration and driver license inquiries should be made against each registration. Registrants should be made aware that they are to provide any change in registration information such as change of address, transfer or sale of the vehicle, change in phone number etc., to either the DPS H.E.A.T. staff (if they registered over the Internet or by mail order) or to the local agency (the agency who entered the record into the TCIC 2000 H.E.A.T. vehicle file). All changes or updates to any pre-existing H.E.A.T. registration should be copied and faxed to the DPS H.E.A.T. staff in Austin for quality control purposes. H.E.A.T. registrations remain active for a period of four years after the date of decal (DOD), which is the date the decals have been provided to the citizen. The DPS H.E.A.T. staff will mail renewal instructions to all registrants whose registrations are about to expire. Local agencies should not renew H.E.A.T. registrations. Please provide our contact information to those citizens wishing to renew their registration.

The H.E.A.T. Program staff may be contacted by phone at (512) 424-2483, toll free at 1-888-447-5933, by fax at (512) 424-5665 or by e-mail at [email protected]

*Please refer to the H.E.A.T. Program's web-site at http://records.txdps.state.tx.us/heat and select the appropriate link to access future changes in our policy along with our newsletter and statistics.

Revised May, 2002 11 Version 1.1

4.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the H.E.A.T. Vehicle File:

MKE FORMATQHV INQUIRE ON H.E.A.T. VEHICLE ONLYEHV ENTER H.E.A.T. VEHICLEMHV MODIFY H.E.A.T. VEHICLEXHV CANCEL H.E.A.T. VEHICLE

QV QUERY VEHICLELV LOCATE STOLEN VEHICLECV CLEAR STOLEN VEHICLE

4.3 CRITERIA FOR ENTRY

When entering a vehicle into the TCIC 2000 H.E.A.T. vehicle file, a Texas H.E.A.T. registration form must be on file. The information required to enter a record into the TCIC 2000 H.E.A.T. vehicle file can be found on the completed Texas H.E.A.T. registration form. Only street legal vehicles (except motorcycles) registered through TXDOT can be entered in the TCIC 2000 H.E.A.T. vehicle file.

4.4 RECORD RETENTION

Each registration remains active for a period of four years after the date in which the citizen was provided with their set of decals (Date of Decal), or until the citizen decides they no longer wish to participate in the Program. Registrations reaching their four-year retention period shall be purged from the file.

4.5 MESSAGE FIELD CODES AND EDITS

For H.E.A.T. registered vehicles, there are additional Texas message field codes and edits which are as follows:

ADD Vehicle owner’s address Mandatory. Physical address of vehicle owner. For out-of-state participants, this field must indicate the physical address of their Texas residence.

Revised May, 2002 12 Version 1.1

CTY Vehicle owner’s city Mandatory. City of residence. For out-of-state participants, this field must indicate the city of their Texas residence.

ST Vehicle owner's state Mandatory. "TX" for residents and non- residents of Texas. Non-residents of Texas must have a valid Texas residence address.

ZIP Vehicle owner's zip code Mandatory. Texas zip code for residents and non-residents of Texas.

FAX Vehicle owner's fax number Optional. The fax number including area code in which vehicle owner can be contacted.

ALT1 Alternate Driver 1 Optional. Persons known to drive the vehicle other than the vehicle owner.

ALT2 Alternate Driver 2 Optional. Persons known to drive the vehicle other than the vehicle owner.

4.6 VALIDATION

Validation of the TCIC 2000 H.E.A.T. vehicle file involves the use of the four-year retention period. The DPS H.E.A.T. staff will mail renewal instructions to all registrants whose registrations are about to expire. Local agencies should not renew H.E.A.T. registrations. Local agencies will receive a list of their H.E.A.T. vehicle records which have been purged due to four-year retention period.

4.7 CRITERIA FOR REJECTING DUPLICATE RECORDS

If the DSN (decal serial number) or VIN fields of a H.E.A.T. vehicle entry are the same as those field codes of an EHV already on file in TCIC 2000, the second entry will be rejected.

Revised May, 2002 13 Version 1.1

4.8 ENTRY (EHV)

4.8.1 EXAMPLE OF ENTRY MESSAGE

EHV * ENTER H.E.A.T. VEHICLE RECORD * MKE: EHV ORI: TX DPS0000 DSN: 12345678 DOD: 01162001 LIC: LIC123____ LIS: TX LIY: 2002 LIT: PC VIN: VIN123TESTXXXXXXXX20 VYR: 1999 VMA: FORD____________________ VMO: XPL VST: LL VCO: DBL/BLU NAM: TEST,NAME FIELD_______________ ADD: 123 TEST ADDRESS FIELD________ CTY: WICHITA FALLS_______ ST: TX ZIP: 79605 - 1234 OLN: 12345678____________ OLS: TX PHN: 940 424 - 2285 FAX: 940 555 - 5555 ALT1: TEST,ALTERNATE DRIVER_________ ALT2: TEST,ALTERNATE DRIVER TWO_____ MIS: MIS FIELD 200___________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

4.8.2 ADDITIONAL GUIDELINES FOR ENTRY

In the H.E.A.T. vehicle file, all fields are mandatory except the FAX, ALT1, ALT2, MIS, and Control fields. If more than two alternate drivers are listed, the MIS field is to be used for the 3 rd

and 4th names etc.; however, the ALT1 and ALT2 fields must be used before the MIS can be utilized for this purpose.

4.9 MODIFY (MHV)

4.9.1 WHEN TO USE A MODIFICATION MESSAGE

Modification of a H.E.A.T. vehicle record is restricted to the agency ORI who entered the record. If an error is made in the DSN field at the time of entry the record should be cancelled and re-entered. When a citizen sells their vehicle and wants to enroll their new vehicle in the Program the old record should be cancelled and a new registration form must be completed to be entered into the TCIC 2000 H.E.A.T. vehicle file.

4.9.2 EXAMPLE OF MODIFICATION MESSAGE

Revised May, 2002 14 Version 1.1

MHV * MODIFY H.E.A.T. RECORD * ORI: TX DPS0000 DSN: 12345678 PUT NEW INFORMATION BELOW. USE (*) TO DELETE AN OPTIONAL FIELD. DOD: 01152001 LIC: __________ LIS: __ LIY: YYYY LIT __ VIN ____________________VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: DBL/RED NAM: ______________________________ ADD: ______________________________ CTY: ____________________ ST: __ ZIP: _____ - ____ OLN: ____________________ OLS: __ PHN: ___ ___ - ____ FAX: ___ ___ - ____ ALT1: ______________________________ ALT2: ______________________________ MIS: ________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________

4.10 CANCELLATION (XHV) For a H.E.A.T. record, this format should be used when an error has been made in the DSN field at the time of entry, or the record has been determined to be invalid, i.e. the owner withdraws from the program or transfers possession of the vehicle.

4.10.1 EXAMPLE OF CANCELLATION MESSAGE

XHV * CANCEL H.E.A.T. VEHICLE RECORD * MKE: XHV ORI: TX DPS0000 IDENTIFY H.E.A.T. RECORD TO BE CANCELED BY DECAL SERIAL NUMBER: DSN: 12345678 CONTROL FIELD: CNTRL

4.11 INQUIRY (QHV)

The format QHV will search the TCIC 2000 H.E.A.T. vehicle file by DSN (Decal Serial Number), LIC (License Number) or VIN (Vehicle Identification Number). The QV inquiry will also search for possible H.E.A.T. hits and will be returned to any TLETS agency making a stolen vehicle inquiry by license plate and/or VIN. NOTE: A search of the Texas Vehicle Registration (TXDOT) file will NOT search the TCIC 2000 H.E.A.T. file; however, a combination vehicle registration/stolen vehicle inquiry (TLETS transaction code: RSDW) will search the TCIC 2000 H.E.A.T. file. The stolen vehicle file cannot be searched by the DSN. The format QHV should be used.

4.11.1 EXAMPLE OF INQUIRY MESSAGE

QHV H.E.A.T. VEHICLE INQUIRY

Revised May, 2002 15 Version 1.1

MKE: QHV ORI: TX DPS0000 INQUIRE ON H.E.A.T. VEHICLE BY DECAL SERIAL NUMBER, LICENSE OR VIN: DSN: 12345678 LIC: LIC123XX10VIN: 123TESTXXXXXXXX20 CONTROL FIELD: CNTRL

Revised May, 2002 16 Version 1.1

TCIC 2000 – TEXAS USER SPECIFICATIONS PAGESWANTED PERSON FILETABLE OF CONTENTS

1. INTRODUCTION 11.1 MESSAGE KEY (MKE) CODES 1

2. WANTED PERSON TRANSACTIONS 12.1 ENTRY (EW, ET, EWJ) 1

2.1.1 EXAMPLE OF ENTRY MESSAGE (EW) 12.1.2 EXAMPLE OF ENTRY MESSAGE (ET) 22.1.3 EXAMPLE OF ENTRY MESSAGE (EWJ) 32.1.4 ADDITIONAL GUIDELINES FOR ENTRY 3

2.1.4a NONEXTRADITABLE WARRANTS 32.1.4b OFFENSES IN THE WANTED PERSON FILE 3

2.2 MODIFY (MW, MT) 42.2.1 EXAMPLE OF MODIFICATION MESSAGE (MW) 42.2.2 EXAMPLE OF MODIFICATION MESSAGE (MT) 42.2.3 VALIDATION GUIDELINES

FOR NCIC/TCIC 2000 MODIFICATION 52.3 CANCEL (XW, XT) 5

2.3.1 EXAMPLE OF CANCELLATION MESSAGE (XW) 52.3.2 EXAMPLE OF CANCELLATION MESSAGE (XT) 6

2.4 INQUIRY (QW) 62.4.1 EXAMPLE OF INQUIRY MESSAGE 62.4.2 ADDITIONAL GUIDELINES FOR INQUIRY 6

2.4.2a QW-X INQUIRIES 62.4.2b QW-T INQUIRIES 72.4.2c WANTED PERSON INQUIRIES 72.4.2d CROSS SEARCH 7

2.5 LOCATE (LW, LT) 72.5.1 EXAMPLE OF LOCATE MESSAGE (LW) 72.5.2 EXAMPLE OF LOCATE MESSAGE (LT) 8

2.6 CLEAR (CW, CT) 82.6.1 EXAMPLE OF CLEAR MESSAGE (CW) 82.6.2 EXAMPLE OF CLEAR MESSAGE (CT) 8

3. TCIC 2000 ONLY WANTED PERSON TRANSACTIONS 93.1 INTRODUCTION 93.2 MESSAGE KEY (MKE) CODES 93.3 CRITERIA FOR ENTRY 93.4 RECORD RETENTION 93.5 ENTRY (EE) 10

3.5.1 EXAMPLE OF ENTRY MESSAGE 103.5.2 ADDITIONAL GUIDELINES FOR ENTRY 10

3.5.2a NONEXTRADITABLE WARRANTS 103.5.2b OFFENSES IN THE WANTED PERSON FILE 10

4. SUPPLEMENTAL DATA TRANSACTIONS 114.1 INTRODUCTION 114.2 MESSAGE KEY (MKE) CODES 11

Revised May, 2002 Version 1.1

4.3 ENTRY (EN1, EN2, ENS) 114.3.1 EXAMPLE OF

SUPPLEMENTAL DATA TRANSACTION (EN1) 114.3.2 EXAMPLE OF

SUPPLEMENTAL DATA TRANSACTION EN2) 124.3.3 EXAMPLE OF

SUPPLEMENTAL DATA TRANSACTION (ENS) 124.4 CANCEL (XN, XNS) 12

4.4.1 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XN) 12

4.4.2 EXAMPLE OF CANCELSUPPLEMENTAL DATA TRANSACTION (XNS) 13

Revised May, 2002 Version 1.1

1. INTRODUCTION

The TCIC 2000 Texas User Specifications Pages for the Wanted Person File document the specifications for TCIC/NCIC 2000 transactions that contain data fields specific to Texas.

1.1 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for the Wanted Person File:

MKE FORMATEW ENTER WANTED PERSON INTO TCIC AND NCICET ENTER TEMPORARY FELONY WANT RECORDEWJ ENTER WANTED JUVENILE RECORDMW MODIFY WANTED PERSON RECORDMT MODIFY TEMPORARY FELONY WANT RECORDXW CANCEL WANTED PERSON RECORDXT CANCEL TEMPORARY WANTED PERSON RECORDLW LOCATE WANTED PERSON RECORDLT LOCATE TEMPORARY WANTED PERSON RECORDCW CLEAR WANTED PERSON RECORDCT CLEAR TEMPORARY WANTED PERSON RECORDQW PERSONS INQUIRY (INVESTIGATIVE PURPOSES)ZW PERSONS INQUIRY (ADMINSTRATIVE/TEST PURPOSES)

2. WANTED PERSON TRANSACTIONS

2.1 ENTRY (EW, ET, EWJ)

2.1.1 EXAMPLE OF ENTRY MESSAGE (EW)

EW ENTER WANTED PERSON RECORD INTO TCIC AND NCIC - PAGE ONE MKE: EW- _ CMC: 55 ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: W POB: TX DOB: 02221962 HGT: 602 WGT: 140 EYE: BLU HAI: BLN FBI: _________ SKN: FAR SMT: TAT R SHLD FPC: ____________________ MNU: __ - ____________ SOC: 123456789 OLN ____________________ OLS __ OLY: YYYYOFF: 5012____________________ OOC: 2399 DOW: 03042002 OCA: TEST OCA____________WNO: 12345__________ CTI: _________ LIC: ABC123____ LIS: TX LIY: 2002 LIT: PC VIN: ____________________ VYR: 2001 VMA: FORD____________________ VMO: XPL VST: LL VCO: BLU____ LKI: _________ LKA: ____________________ NOA: _

Revised May, 2002 1 Version 1.1

EW2 ENTER WANTED PERSON RECORD INTO TCIC AND NCIC - PAGE TWO MIS: PROBATION VIOLATION / ORIGINAL CHARGE THEFT / SID/TX12345678______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________ ENTER STOLEN/FRAUDULENT IDENTIFIERS BELOW: NAM: ______________________________ DOB: MMDDYYYY SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY

2.1.2 EXAMPLE OF ENTRY MESSAGE (ET)

ET ENTER TEMPORARY FELONY WANT RECORD - PAGE ONE MKE: ET- C CMC: 00 ORI: TX DPS0000 NAM: RECORD,IMA TEST_______________ SEX: F RAC: U POB: AZ DOB: 05151965 HGT: 507 WGT: 130 EYE: BRO HAI: BRO FBI: _________ SKN: ___ SMT: __________ FPC: ____________________ MNU: __ - ____________ SOC: 555555555 OLN 12345678____________ OLS TX OLY: 2007OFF: 2399____________________ OOC: ____ DOW: 03042002 OCA: OCA TEST_________WNO: _______________ CTI: _________ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

ET2 ENTER TEMPORARY FELONY WANT RECORD - PAGE TWO MIS: THEFT $200-$750____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________ ENTER STOLEN/FRAUDULENT IDENTIFIERS BELOW: NAM: ______________________________ DOB: MMDDYYYY SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY

Revised May, 2002 2 Version 1.1

2.1.3 EXAMPLE OF ENTRY MESSAGE (EWJ)

EWJ ENTER WANTED JUVENILE RECORD - PAGE ONE MKE: EWJ- _ CMC: __ ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC W POB __ DOB: 08151987 DOE: 08152004 HGT 511 WGT 150 EYE BRO HAI BROFBI: _________ SKN: ___ SMT: __________ FPC: ____________________ MNU: __ - ____________ SOC: 121212121 OLN 01234567____________ OLS TX OLY: 2005OFF: 8100____________________ OOC: 2411 DOV: 03042002 OCA: EWJ TEST____________WNO: _______________ CTI: _________ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

EWJ2 ENTER WANTED JUVENILE RECORD - PAGE TWO MIS: TEST MISCELLANEOUS FIELD______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________ ENTER STOLEN/FRAUDULENT IDENTIFIERS BELOW: NAM: ______________________________ DOB: MMDDYYYY SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY

2.1.4 ADDITIONAL GUIDELINES FOR ENTRY

2.1.4a NONEXTRADITABLE WARRANTS

Nonextraditable warrants may be entered into TCIC/NCIC 2000 in situations where an agency is absolutely certain that the wanted person will not be extradited by placing NOEX as the first four characters of the (MIS) field. Texas agencies must be willing to transport from anywhere within the state of Texas even when NOEX is used.

2.1.4b OFFENSES IN THE WANTED PERSON FILE

Minor misdemeanor traffic warrants, such as those for running stop signs, speeding, insurance violations, and similar charges may not be entered into TCIC/NCIC 2000. Offenses that carry a class B misdemeanor or higher charge are eligible for entry into TCIC/NCIC 2000. Capias pro fine is a procedure for collecting outstanding fines and is indicative of a minor misdemeanor; therefore, a person wanted only for capias pro fine cannot be entered into TCIC/NCIC 2000.

Revised May, 2002 3 Version 1.1

2.2 MODIFY (MW, MT)

2.2.1 EXAMPLE OF MODIFICATION MESSAGE (MW)

MW MODIFY WANTED PERSON RECORD INTO TCIC AND NCIC - PAGE ONE ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ ENTER NEW INFORMATION BELOW. USE '*' TO DELETE OPTIONAL FIELDS. MKE: E ___ CMC: __ ORI: TX _______ NAM: ______________________________ SEX: _ RAC _ POB __ DOB: MMDDYYYY DOE: MMDDYYYY HGT ___ WGT ___ EYE ___ HAI ___FBI: _________ SKN: ___ SMT: __________ FPC: ____________________ MNU: PI - 12345678____ SOC: _________ OLN 12121212____________ OLS TX OLY: 2008OFF: ________________________ OOC: ____ DOW: MMDDYYYY OCA: ____________________WNO: _______________ CTI: _________ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

MW2 MODIFY WANTED PERSON RECORD INTO TCIC AND NCIC - PAGE TWO MIS: PROBATION VIOLATION / ORIGINAL CHARGE THEFT $750-$20000 / SID/TX12345678____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ VLN: ______________________________ CONTROL FIELD: __________

2.2.2 EXAMPLE OF MODIFICATION MESSAGE (MT)

MT MODIFY TEMPORARY FELONY WANT RECORD - PAGE ONE ORI: TX DPS0000 NAM: RECORD,IMA TEST_______________ OCA: OCA TEST____________ ENTER NEW INFORMATION BELOW. USE '*' TO DELETE OPTIONAL FIELDS. MKE: E ___ CMC: __ ORI: TX _______ NAM: ______________________________ SEX: _ RAC: _ POB: __ DOB: MMDDYYYY HGT: ___ WGT: ___ EYE: ___ HAI: ___ FBI: _________ SKN: ___ SMT: __________ FPC: ____________________ MNU: PI – 22222222____ SOC: _________ OLN ____________________ OLS __ OLY: YYYYOFF: 2606____________________ OOC: ____ DOW: MMDDYYYY OCA: ____________________WNO: _______________ CTI: _________ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

MT2 MODIFY TEMPORARY FELONY WANT RECORD - PAGE TWO

Revised May, 2002 4 Version 1.1

MIS: THEFT BY CHECK $200-$750__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ VLN: ______________________________ CONTROL FIELD: __________

2.2.3 VALIDATION GUIDELINES FOR NCIC/TCIC 2000 MODIFICATION

For NCIC/TCIC 2000 validation, a Name of Validator (VLN) may be added to a wanted person record to indicate that the record has met the criteria for validation. When the VLN is entered, TCIC 2000 and NCIC 2000 store the current date in the record as the Date of Last Validation (VLD). If the user attempts to delete or modify the VLN to all blanks, the message will be rejected. The acknowledgment for the modification message containing the VLN will indicate the record has been validated. The VLN can be in any form that will uniquely identify the individual responsible for the validation of the record, e.g., name, user ID, employee number, etc. The NCIC 2000 policy requiring "on-line" validation has been suspended until further notice.

2.3 CANCEL (XW, XT)

2.3.1 EXAMPLE OF CANCELLATION MESSAGE (XW)

XW CANCEL WANTED PERSON RECORD ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ RPS: WARRANT DISMISSED____ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CW' IF PERSON WAS APPREHENDED.

2.3.2 EXAMPLE OF CANCELLATION MESSAGE (XT)

Revised May, 2002 5 Version 1.1

XT CANCEL TEMPORARY WANTED PERSON RECORD ORI: TX DPS0000 NAM: RECORD,IMA TEST_______________ OCA: OCA TEST____________ RPS: NOT WANTED___________ CONTROL FIELD: __________ USE THIS FORMAT TO REMOVE INVALID RECORD. USE 'CT' IF PERSON WAS APPREHENDED.

2.4 INQUIRY (QW)

2.4.1 EXAMPLE OF INQUIRY MESSAGE

QW PERSONS INQUIRY MKE: QW- _ ORI: TX DPS0000 NAM: TEST,RECORD___________________ SEX: M RAC: U DOB: 02221962 FBI: _________ SOC: _________ OLN: ____________________ MNU: __ - ____________LIC: __________ LIS: __ VIN: ____________________ VMA: ________________________OCA: ____________________ NIC: __________ RELATED SEARCH HIT: _ EXPANDED NAME SEARCH: Y REGIONAL: ___ REGIONAL 2: ___ CONTROL FIELD: __________ THIS FORMAT FOR INVESTIGATIVE INQUIRY. USE 'ZW' FOR ADMIN/TEST INQUIRY.

2.4.2 ADDITIONAL GUIDELINES FOR INQUIRY

2.4.2a QW-X INQUIRIES

TCIC 2000 Wanted Person inquiries use the New York State Identification and Intelligence System (NYSIIS), like NCIC 2000, to match a name in an inquiry with a name in a record on file. TCIC 2000 inquiries containing DOB search exactly as NCIC 2000. If the MKE: "QW-X" is used, TCIC 2000 searches the exact match of the date of birth only.

2.4.2b QW-T INQUIRIES

Revised May, 2002 6 Version 1.1

Wanted Person file inquiries using MKE: "QW-T" will search TCIC 2000 only. An NCIC 2000 search will not be performed.

2.4.2c WANTED PERSON INQUIRIES

The TLETS Persons inquiry format (transaction code "QW" or "ZW") allows an inquiry to be made by: 5. NAM and one, more than one, or all of the following alphanumeric identifiers:

DOB (including month, day, year), FBI, SOC, OLN, and MNU.6. Vehicle data (LIC/LIS or VIN/VMA).7. NAM and OCA only (exact spelling of the name contained in the record is required).8. NIC only.

This means that an inquiry can be made on multiple identifiers in one format.

2.4.2d CROSS SEARCH

The "QW" format cross-searches the following TCIC/NCIC 2000 files: Wanted Person, Missing Person, Protective Order, Foreign Fugitive, Deported Felon, Sex Offender, U.S. Secret Service Protection file, Canadian Warrants, Violent Gang and Terrorist Organization, Convicted Person on Supervised Release, Officer Threat, Individual Identity and the Texas Concealed Handgun License file. If vehicle identifiers are included in the inquiry, the Vehicle, Boat, Vehicle/Boat Part, and License Plate files will be searched.

2.5 LOCATE (LW, LT)

2.5.1 EXAMPLE OF LOCATE MESSAGE (LW)

LW LOCATE WANTED PERSON RECORD APPREHENDING AGENCY'S ORI: TX 0000000 NAM: TEST,RECORD___________________ OCA IN THE RECORD: TEST OCA____________ DATE OF APPREHENSION: 03122002 APPREHENDING AGENCY'S OCA: LW OCA______________EXTRADITION ('EXTR' OR 'NOEX'): EXTR RPS: HIT STATE 20020312___ PAR: _ HIT: __ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________

2.5.2 EXAMPLE OF LOCATE MESSAGE (LT)

Revised May, 2002 7 Version 1.1

LT LOCATE TEMPORARY WANTED PERSON RECORD APPREHENDING AGENCY'S ORI: TX 0000000 NAM: RECORD,IMA TEST_______________ OCA IN THE RECORD: OCA TEST____________ DATE OF APPREHENSION: 03072002 APPREHENDING AGENCY'S OCA: LT TEST_____________EXTRADITION ('EXTR' OR 'NOEX'): EXTR RPS: HIT LOCAL 20020307___ PAR: _ HIT: __ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________

2.6 CLEAR (CW, CT)

2.6.1 EXAMPLE OF CLEAR MESSAGE (CW)

CW CLEAR WANTED PERSON RECORD ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ DATE OF APPREHENSION: 03122002 IF PERSON WAS APPREHENDED BY AN AGENCY OTHER THAN ENTERING AGENCY, AND THE APPREHENDING AGENCY HAS NOT PLACED A LOCATE ON THE RECORD: APPREHENDING AGENCY ORI _________ APPREHENDING AGENCY OCA ___________________RPS: HIT STATE 20020312___ PAR: _ HIT: __ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF PERSON APPREHENDED. USE 'XW' TO CANCEL INVALID RECORD.

2.6.2 EXAMPLE OF CLEAR MESSAGE (CT)

CT CLEAR TEMPORARY WANTED PERSON RECORD ORI: TX DPS0000 NAM: RECORD,IMA TEST_______________ OCA: OCA TEST____________ DATE OF APPREHENSION: 03072002 IF PERSON WAS APPREHENDED BY AN AGENCY OTHER THAN ENTERING AGENCY, AND THE APPREHENDING AGENCY HAS NOT PLACED A LOCATE ON THE RECORD: APPREHENDING AGENCY ORI _________ APPREHENDING AGENCY OCA ____________________RPS: HIT LOCAL 20020307___ PAR: _ HIT: __ NPA: ___ NPF: ____________________ VNP: ________ VOR: ________ VRC: ________ CONTROL FIELD: __________ USE THIS FORMAT IF PERSON APPREHENDED. USE 'XT' TO CANCEL INVALID RECORD.

3. TCIC 2000 ONLY WANTED PERSON TRANSACTIONS

Revised May, 2002 8 Version 1.1

3.1 INTRODUCTION

For TCIC 2000 purposes, a wanted person may be entered only if a warrant for the person’s arrest is on file and accessible for immediate confirmation. A record entered with Message Key "EE" will be on file in TCIC 2000 only. Although Texas only wanted person entries are allowed, Texas agencies are encouraged to enter wanted person records into both TCIC 2000 and NCIC 2000 (transaction code "EW") even if the agency is unwilling to extradite. This entry into both databases increases officer and public safety.

3.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE’s for TCIC 2000 Only Wanted Person records:

MKE FORMATEE ENTER WANTED PERSON INTO TCIC ONLY

MW MODIFY WANTED PERSON RECORDLW LOCATE WANTED PERSON RECORDCW CLEAR WANTED PERSON RECORDXW CANCEL WANTED PERSON RECORDQW PERSONS INQUIRY (INVESTIGATIVE PURPOSES)ZW PERSONS INQUIRY (ADMINISTRATIVE/TEST PURPOSES)

3.3 CRITERIA FOR ENTRY

The transaction code "EE" is for the TCIC 2000 Only Wanted Person file entry. Individuals may be entered into this file provided that a warrant has been obtained for a criminal charge for a felony or Class A or B misdemeanor, and that the originating agency is willing to transport the subject from any location in Texas. If these criteria are not met, the subject cannot be entered.

The "EE" format is identical to the "EW" format, except for the MKE and transaction code. Any inquiry, modify, cancel, locate or clear transaction pertaining to a TCIC 2000 Only record is identical to that of the "EW" Wanted Person file.

3.4 RECORD RETENTION

TCIC 2000 Only Wanted Person records are automatically purged from the file two (2) years from the date of entry. Agencies will be mailed lists of their purged "EE" records.

3.5 ENTRY (EE)

Revised May, 2002 9 Version 1.1

3.5.1 EXAMPLE OF ENTRY MESSAGE

EE ENTER WANTED PERSON RECORD INTO TCIC ONLY - PAGE ONE MKE: EE- _ CMC: __ ORI: TX DPS0000 NAM: RECORD,TEST___________________ SEX: M RAC: W POB: TX DOB: 01011961 HGT: 511 WGT: 150 EYE: BLU HAI: BRO FBI: _________ SKN: MED SMT: TAT L LEG_ FPC: ____________________ MNU: PI - 12345678____ SOC: 111111111 OLN 01234567____________ OLS TX OLY: 2008OFF: 3599____________________ OOC: ____ DOW: 03072002 OCA: OCA TEST____________WNO: 22222__________ CTI: _________ LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ LKI: _________ LKA: ____________________ NOA: _

EE2 ENTER WANTED PERSON RECORD INTO TCIC ONLY - PAGE TWO MIS: TEST MISCELLANEOUS FIELD______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________ CONTROL FIELD: __________ ENTER STOLEN/FRAUDULENT IDENTIFIERS BELOW: NAM: ______________________________ DOB: MMDDYYYY SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY

3.5.2 ADDITIONAL GUIDELINES FOR ENTRY

3.5.2a NONEXTRADITABLE WARRANTS

Nonextraditable warrants may be entered into TCIC/NCIC 2000 in situations where an agency is absolutely certain that the wanted person will not be extradited by placing NOEX as the first four characters of the (MIS) field. Texas agencies must be willing to transport from anywhere with the state of Texas when NOEX is used.

3.5.2b OFFENSES IN THE WANTED PERSON FILE

Minor misdemeanor traffic warrants, such as those for running stop signs, speeding, insurance violations, and similar charges may not be entered into TCIC/NCIC 2000. Offenses that carry a class B misdemeanor or higher charge are eligible for entry into TCIC/NCIC 2000. Capias pro fine is a procedure for collecting outstanding fines and is indicative of a minor misdemeanor; therefore, a person wanted only for capias pro fine cannot be entered into TCIC/NCIC 2000.

4. SUPPLEMENTAL DATA TRANSACTIONS

Revised May, 2002 10 Version 1.1

4.1 INTRODUCTION

Texas TLETS direct users must add supplemental data to a wanted person record using transaction codes "EN1", "EN2", and "ENS" depending upon the type of additional identifier being added. Before a supplemental field may be entered, data must exist in that field of the existing base record. If that field was not filled upon entry, a modification message (transaction code "MW" or "MT") must be used to add that field information to the base record before supplemental data can be added. Supplemental data cannot be modified. If there is an error in the supplemental data added to a base record, the supplemental data must be canceled and re-entered. Texas TLETS direct users cancel supplemental data using transaction codes "XN" and "XNS" depending upon the type of additional identifier being removed.

4.2 MESSAGE KEY (MKE) CODES

The following are applicable MKE's for Supplemental Data transactions in the Wanted Person File:

MKE FORMATEN1 ENTER SUPPLEMENTAL AKA/DOB INFORMATIONEN2 ENTER SUPPLEMENTAL DATA RECORD

(SMT, SOC, MNU, OLN, LIC, VIN, CMC)ENS ENTER SUPPLEMENTAL STOLEN/FRAUDULENT IDENTIFIERS XN CANCEL SUPPLEMENTAL DATA

XNS CANCEL SUPPLEMENTAL STOLEN/FRAUDULENT IDENTIFIERS

4.3 ENTRY (EN1, EN2, ENS)

4.3.1 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (EN1)

EN1 ENTER SUPPLEMENTAL AKA/DOB INFORMATION—WANTED PERSON FILE MKE: EN ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ ENTER MULTIPLE AKA AND/OR DOB DATA BELOW: AKA: RECORD,TEST__________________ AKA: ______________________________ AKA: ________________________________ AKA: ______________________________ AKA: ________________________________ AKA: ______________________________ DOB: 01011961 DOB: MMDDYYYY DOB: MMDDYYYY CONTROL FIELD: __________

4.3.2 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (EN2)

EN2 ENTER SUPPLEMENTAL DATA RECORD--WANTED PERSON FILE

Revised May, 2002 11 Version 1.1

MKE: EN ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ ENTER SUPPLEMENTAL DATA BELOW: SMT: TAT BACK__ SMT: TAT L SHLD SMT: __________ SOC: 010123234 SOC: _________ MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: __________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ CONTROL FIELD: __________

4.3.3 EXAMPLE OF SUPPLEMENTAL DATA TRANSACTION (ENS)

ENS ENTER SUPPLEMENTAL STOLEN/FRAUDULENT IDENTIFIERS MKE: ENS ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ ENTER MULTIPLE STOLEN/FRAUDULENT IDENTIFIERS BELOW: NAM: SMITH,TEST___________________ DOB: 05191966 SOC: _________ NAM: _______________________________ DOB: MMDDYYYY SOC: _________ NAM: _______________________________ DOB: MMDDYYYY SOC: _________ MNU: __ - ____________ OLN: _________ OLS: __ OLY: YYYY MNU: __ - ____________ OLN: _________ OLS: __ OLY: YYYY MNU: __ - ____________ OLN: _________ OLS: __ OLY: YYYY CONTROL FIELD: _________

4.4 CANCEL (XN, XNS)

4.4.1 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XN)

XN CANCEL SUPPLEMENTAL DATA--WANTED PERSON FILE MKE: XN ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ ENTER DATA TO BE CANCELED BELOW: AKA: RECORD,TEST___________________ DOB: MMDDYYYY SMT: TAT L SHLD SOC _________MNU: __ - ____________ OLN: ____________________ OLS: __ OLY: YYYY LIC: ________ LIS: __ LIY: YYYY LIT: __ VIN: ____________________ VYR: YYYY VMA: ________________________ VMO: ___ VST: __ VCO: _______ CMC: __ CONTROL FIELD: __________

4.4.2 EXAMPLE OF CANCEL SUPPLEMENTAL DATA TRANSACTION (XNS)

Revised May, 2002 12 Version 1.1

XNS CANCEL SUPPLEMENTAL STOLEN/FRAUDULENT IDENTIFIERS MKE: XNS ORI: TX DPS0000 NAM: TEST,RECORD___________________ OCA: TEST OCA____________ ENTER MULTIPLE STOLEN/FRAUDULENT IDENTIFIERS BELOW: NAM: SMITH,TEST____________________ DOB: 05191966 SOC: _________ NAM: ______________________________ DOB: MMDDYYYY SOC: _________ NAM: ______________________________ DOB: MMDDYYYY SOC: _________ MNU: __ - ____________ OLN: _________ OLS: __ OLY: YYYY MNU: __ - ____________ OLN: _________ OLS: __ OLY: YYYY MNU: __ - ____________ OLN: _________ OLS: __ OLY: YYYY CONTROL FIELD: __________

Revised May, 2002 13 Version 1.1

Revised May, 2002 1 Version 1.1