Table of Contents SECTION 01: I. II. III. IV. V. INTRODUCTION ..................................................................................

3

PURPOSE OF THE VIOLENT PERSON FILE .................................................................... 3 CRITERIA FOR ENTRY IN THE VIOLENT PERSON FILE ..................................................... 3 RETENTION PERIOD FOR VIOLENT PERSON FILE .......................................................... 3 AUTOMATIC RETIREMENT.......................................................................................... 3 VALIDATION............................................................................................................. 4

SECTION 02: I. II.

MESSAGE KEYS, FIELD CODES, AND EDITS.................................. 5

MESSAGE KEY (MKE) CODES FOR VIOLENT PERSON FILE .............................................. 5 MESSAGE FIELD CODES AND EDITS ............................................................................ 5

SECTION 03: I. II. III. IV.

INQUIRY TRANSACTIONS ............................................................... 12

MESSAGE FIELD CODES FOR VIOLENT PERSON INQUIRY ............................................. 12 GUIDELINES FOR VIOLENT PERSON INQUIRY ............................................................. 13 REQUIREMENTS FOR VIOLENT PERSON INQUIRY ........................................................ 14 EXAMPLE OF VIOLENT PERSON INQUIRY RESPONSE ................................................... 14

SECTION 04: I. II. III. IV. V.

ENTRY TRANSACTIONS .................................................................. 17

MESSAGE FIELD CODES FOR VIOLENT PERSON ENTRY ............................................... 17 GUIDELINES FOR VIOLENT PERSON ENTRY................................................................ 18 REQUIREMENTS FOR VIOLENT PERSON ENTRY .......................................................... 19 EXAMPLE OF VIOLENT PERSON ENTRY ..................................................................... 19 EXAMPLE OF VIOLENT PERSON ENTRY ACKNOWLEDGMENT ........................................ 19

SECTION 05: I. II. III. IV.

MODIFY TRANSACTIONS ................................................................ 20

MESSAGE FIELD CODES FOR VIOLENT PERSON MODIFICATION .................................... 20 GUIDELINES FOR VIOLENT PERSON MODIFICATION..................................................... 20 REQUIREMENTS FOR VIOLENT PERSON MODIFICATION ............................................... 21 EXAMPLE OF VIOLENT PERSON MODIFICATION ACKNOWLEDGMENT ............................. 21

SECTION 06: I. II. III. IV.

SUPPLEMENTAL TRANSACTIONS ................................................. 22

MESSAGE FIELD CODES FOR VIOLENT PERSON SUPPLEMENTAL .................................. 22

.................................................. 23 REQUIREMENTS FOR VIOLENT PERSON SUPPLEMENTAL ............................................. 24 EXAMPLE OF VIOLENT PERSON SUPPLEMENTAL ACKNOWLEDGMENT ........................... 25
GUIDELINES FOR VIOLENT PERSON SUPPLEMENTAL

SECTION 07: I. II. III. IV.

CANCEL SUPPLEMENTAL TRANSACTIONS ................................. 26

MESSAGE FIELD CODES FOR VIOLENT PERSON CANCEL SUPPLEMENTAL ...................... 26 GUIDELINES FOR VIOLENT PERSON CANCEL SUPPLEMENTAL ...................................... 27 REQUIREMENTS FOR VIOLENT PERSON CANCEL SUPPLEMENTAL................................. 28 EXAMPLE OF VIOLENT PERSON CANCEL SUPPLEMENTAL ACKNOWLEDGMENT ............... 29

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-1

SECTION 08: I. II. III. IV.

CANCEL TRANSACTIONS ............................................................... 30

MESSAGE FIELD CODES FOR VIOLENT PERSON CANCEL ............................................. 30 GUIDELINES FOR VIOLENT PERSON CANCEL .............................................................. 30 REQUIREMENTS FOR VIOLENT PERSON CANCEL ........................................................ 30 EXAMPLE OF VIOLENT PERSON CANCEL ACKNOWLEDGMENT ...................................... 31

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-2

CHAPTER 29: SECTION 01: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.01.000

VIOLENT PERSON FILE INTRODUCTION Effective Date: See Also: CALEA: February 1, 2013

PURPOSE OF THE VIOLENT PERSON FILE A. The Violent Person File (VPF) was designed to alert law enforcement officers that an individual they are encountering may have the propensity for violence against law enforcement. It is for information only. WACIC does not contain VPF information. All VPF transactions are forwarded to NCIC. An entry into the VPF should be made when at least one of the following criteria has been met: 1. Offender has been convicted for assault or murder/homicide of a law enforcement officer, fleeing, resisting arrest, or any such statute which involves violence against law enforcement. Offender has been convicted of a violent offense against a person to include homicide and attempted homicide. Offender has been convicted of a violent offense against a person where a firearm or weapon was used. A law enforcement agency, based on its official investigatory duties, reasonably believes that the individual has seriously expressed his or her intent to commit an act of unlawful violence against a member of the law enforcement or criminal justice community.

B. II.

CRITERIA FOR ENTRY IN THE VIOLENT PERSON FILE A.

2. 3. 4.

III.

RETENTION PERIOD FOR VIOLENT PERSON FILE A. VPF records have an unlimited retention period. A VPF record will remain on file indefinitely or until action is taken by the entering agency to cancel the record. Other exceptions to the record retention periods will occur in the event a serious error is detected in the record on file. Data in the License Plate Number (LIC), License Plate Year of Expiration (LIY), and License Plate Type (LIT) Fields will remain in a VPF record or supplemental record for the year of entry plus 4 years, provided the license information has expired. Entering agencies are not notified of records from which expired license data are retired. If the expired license
Violent Person File Chapter 29-3

B. IV.

AUTOMATIC RETIREMENT A.

ACCESS Operations Manual Revised May 2013

plate is the only searchable identifier in the VPF record, the entire record will be retired, and the originating agency will not be notified. B. A non-expiring license plate (LIY/NX) contained in a VPF record will remain on file until action is taken by the originating agency to remove the license data or cancel the entire record. Violent Person File records are validated monthly. Each record entered will be subject to validation three months after entry and annually thereafter.

V.

VALIDATION A.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-4

CHAPTER 29: SECTION 02: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.02.000

VIOLENT PERSON FILE MESSAGE KEYS, FIELD CODES, AND EDITS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE KEY (MKE) CODES FOR VIOLENT PERSON FILE Inquiry QW

Entry Modify Locate Clear Cancel Violent Person *EVP MVP N/A N/A XVP Entry Cancel Supplemental ENVP XNVP *Fourth character "C" may be added to the entry MKE to indicate caution. When used, the reason for caution must be explained in the Cautions and Medical Conditions (CMC) Field, and if necessary, further explained in the Miscellaneous Field (MIS). II. MESSAGE FIELD CODES AND EDITS Field Alias Edits May include alphabetics, numerics, a comma, hyphens, and spaces. The comma must follow the last name. There can be no more than one space after the comma. The hyphen cannot be in the first position or directly precede the comma. Information on coding instructions can be found in the Personal Descriptors Section of the NCIC Code Manual. This field may contain the first initial and last name of the person requesting the information. Must be a valid code as listed in the Personal Descriptors Section of the NCIC Code Manual. Must contain a two character alphabetic country code form the State and Country Data Codes of the NCIC Code Manual. A 250 character free text field that explains the location of the DNA sample, contact information, ORI, type of DNA sample available, and the CODIS number. If the DNA field is N or defaulted to N, then the DLO field must be blank. Must be either a Y or N. N is the default value. If Y is entered then the DLO field must be filled. Must be eight numbers representing year, month, and day in that order (YYYYMMDD). The numbers in the month positions cannot exceed 12. The numbers in the day positions cannot exceed the
Violent Person File Chapter 29-5

Code AKA

ATN CMC CTZ

Attention Cautions and Medical Conditions Citizenship

DLO

DNA Location

DNA DOB

DNA Profile Indicator Date of Birth

ACCESS Operations Manual Revised May 2013

DOC ENS ETN EYE FBI

Date of Cancellation Expanded Name Search Ethnicity Eye Color FBI Number

number of days in the month indicated. The month and date cannot exceed the date entered and cannot be ----0229 when the year is not a leap year. Must be a valid Gregorian date (YYYYMMDD) equal to current date or current date minus one. Must be Y or N. Must be a valid code as listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be a valid code as listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. The field may be one to nine characters. It may be up to seven numbers; or one to six numbers followed by a letter A through H; or one to six numbers followed by a letter J through Z, followed by one or two check digits; or one to six numbers followed by two letters followed by one check digit. If the number contains one letter (J-Z), the check digit(s) will be 1-11. If the number contains two letters, the first cannot be B, G, I, O, Q, S, U, Y, or Z; the second must be A, B, or C; and the check digit will be 0 to 9. The letters I and O are always invalid. Must be 20 numbers and/or characters, which are listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. Codes 00 and 50 may not be used. Must be a valid code as listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be three numbers, with the first number representing feet and the second and third representing inches. The second character must be 0 or 1. If the second character is 1, the third must be 0 or 1. It must indicate a minimum of 400 and a maximum of 711. A self-checking number automatically assigned by NCIC to each accepted image record and consists of the alphabetic character I followed by nine numeric characters. Must have valid check digit. Must be a valid code as listed in the Other Transactions Codes Section of the NCIC 2000 Code Manual. Must be Y or N. Must be INV or ALL. Contains a maximum of ten alpha-numeric characters. It must not be the letters UNK, UNKN, UNKNOWN. If the VMA is AERO, LIS is US and LIT is PP or NP, the first character in the LIC field must be the letter

FPC

Fingerprint Classification

HAI HGT

Hair Color Height

IMN

Image NCIC Number

IMT

Image Type

IND INV LIC

Image Indicator Investigation Field License Plate Number

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-6

LIS

License Plate State

LIT

License Plate Type

LIY

License Plate Year

LKA

Linkage Case Number

N. If the license plate number exceeds eight characters, only the last eight should be entered. The full plate number must be shown in the MIS Field. If LIC is entered, then LIS, LIY, and LIT must be entered. Must be a valid code as listed in State and Country Codes of the NCIC 2000 Code Manual. It must be entered if LIC Field is filled. Must be a valid code as listed in the Vehicle Data Codes Section of the NCIC 2000 Code Manual. It must be entered if LIC Field is filled. Must be four numbers representing current year, minus one, or later than current year; or the letters NX to represent a non-expiring registration. It must be entered if LIC Field is filled. Contains a maximum of 20 alphanumeric characters. It must not contain a single zero only, a run of zeros only, a single alphabetic only or the word NONE. The first seven characters of the LKA cannot equal the first seven characters of the LKI. The only valid special character is the hyphen. The LKA must be valid for the LKI. There must be an ORI and matching OCA in the system. The Linkage ORI and OCA Fields are provided as separate fields to associate incidents that are handled by multiple departments. An agency entering a record which shares the same incident of a record entered by a different ORI and/or OCA can link the records by entering the associated ORI and OCA in the linkage fields (LKI and LKA). In the entry message the LKI and LKA Fields immediately follow the OCA Field entry. The message will be rejected if the first seven characters of the LKA are the same as the first seven characters of the LKI. Must be a valid ORI. The LKI and LKA cannot be identical to the ORI and OCA. For further explanation, see LKA above. Free text. It may contain a maximum of 500 characters. Must contain a statement describing the reason a subject is considered dangerous to the criminal justice community. Must be a valid message key. The first two characters must be a valid code as listed in Personal Descriptors, NCIC 2000 Code Manual. The third character must be a hyphen. Entry of one zero only or a run of zeros only is prohibited in positions 4 through 15. An originating
Violent Person File Chapter 29-7

LKI

Linkage Agency Identifier Miscellaneous

MIS

MKE MNU

Message Key Miscellaneous Number

ACCESS Operations Manual Revised May 2013

NAM

Name

NIC

NCIC Number

OCA

Originating Agency Case Number

agency police or identification number in MNU cannot be the only numeric identifier in the record. If the MNU exceeds 15 characters, the first 15 characters should be entered in the MNU Field. The full MNU should be entered in the MIS Field. The name may include alphabetics, numerics, a comma, hyphens, and spaces; the comma must follow the last name; there can be no more than one space after the comma. The hyphen cannot be in the first position or directly precede the comma. Information on coding instructions can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual. A self-checking number automatically assigned by NCIC 2000 to each accepted record and consists of an alphabetic character (L in the Violent Person File) followed by nine numeric characters. Must have valid check digits when used to identify record in a subsequent transaction. The entering agency should ensure the OCA is a unique number assigned to the case within the agency. Must not contain a single zero only, a run of zeros only, the word NONE, or a single alphabetic only. The first seven characters of the OCA cannot equal the first seven characters of the ORI. The only valid special character is the hyphen. Must not be one zero only or a run of zeros only. Omit any spaces, hyphens, or symbols (i.e. DOE**JJ12345 is entered DOEJJ12345). If OLN is entered, then OLS and OLY must be entered. More information can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be a valid code as listed in State and Country Codes Section of the NCIC 2000 Code Manual. It must be entered if OLN Field is filled. More information can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must represent the year the license expires (XXXX), the alphabetics NX to represent non-expiring, or the code UNKN for unknown. It must be entered if OLN Field is filled. More information can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be a valid ORI.

OLN

Operator’s License Number

OLS

Operator’s License State

OLY

Operator’s License Year

ORI

Originating Agency Identifier

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-8

POB

Place of Birth

RAC RNG

Race Range

RSH SEX SKN SMT

Related Search Hit Sex Skin Tone Scars, Marks, Tattoos, and Other Characteristics Social Security Number

Must be a valid code as listed in State and Country Codes Section of the NCIC 2000 Code Manual. More information can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be a valid code as listed in Personal Descriptors Section of the NCIC 2000 Code Manual. RNG will provide a specific response or a range of responses related to the inquiry. Must be a specific number, range of numbers, or ALL. Must be Y or N. Must be a valid code as listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be a valid code as listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be a valid code as listed in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must not be less than 001010001. Invalid and/or nonissue numbers are accepted but result in a SOC attention message. More information can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual. Must be valid code as listed in Vehicle Data Codes Section of the NCIC 2000 Code Manual representing the first or only color of the vehicle. If two colors codes are used, they must be separated by a slash (/) or entered in the VCOS Field. For Omnixx users: Must be valid code as listed in Vehicle Data Codes Section of the NCIC 2000 Code Manual representing the second color of the vehicle. If entered, the VCO must also be entered. Single zero only, run of zeros only, single alphabetic only, all alphabetics only, or spaces cannot be used. The Vehicle File has additional edits on the VIN Field. If state-assigned or nonconforming 17character VIN, SVIN must be entered in the first four characters of the MIS Field. If the VIN exceeds 20 characters, only the last 20 characters should be entered in the VIN Field. The full VIN must then be shown in the MIS Field. If VIN is entered, then VCO, VMA, VMO, VST, and VYR must be entered. Contains a maximum of 24 characters. The first four characters must be a valid code. If the VMA code is less than four characters and data are included in positions 5 through 24 (or in the VMAD Field), positions 3 and/or 4 should be blanks. Characters 524, or VMAD, are free text and must contain the name of the manufacturer when the VMA is AERO, ATV, COEQ, CYCL, FARM, SNOW, SPEC, TRLR, or TRUK.
Violent Person File Chapter 29-9

SOC

VCO

Vehicle Color

VCOS*

Vehicle Color Second

VIN

Vehicle Identification Number

VMA

Vehicle Make

ACCESS Operations Manual Revised May 2013

If the VMO is other than TL, the VMA code must be a valid code as listed in Vehicle Data Codes, NCIC 2000 Code Manual. If the VMO is TL, the VMA code must not be the characters: ASM, ASMB, ASSE, ASSM, MB, MC, MK, MP, MS, NA, TK, TL, UNK, UNKN, XX, XXX, XXXX, YY, YYY, YYYY, ZZ, ZZZ, or ZZZZ. For every assembled vehicle that does not have manufacturer's assigned VIN, the VMA code must be ASVE. (Jeep) If the VMA code is JEP, the VYR must be 1969 or earlier. If the VMA code is AMER, the VYR must be 1988 or earlier. If the VMA code is JEEP, the VYR must be 1989 or later. If VST is 1J, 2J, 3J, MJ, 1P, 2P, 3P, MP, BP, HP, or SA, the VMA code must be AERO. If VST is EB, EN, or OP, the VMA code must be SPEC, ATV, SNOW, CYCL, or one of the approved VMA codes for snowmobiles or motorcycles listed in Vehicular Data Codes Section of the NCIC 2000 Code Manual. If VST is MV, the VMA code must be SPEC, ATV, CYL, or one of the approved VMA codes for snowmobiles or motorcycles listed in Vehicular Data Codes Section of the NCIC 2000 Code Manual. If VMA code is ATV or SPEC the VST must be EB, EN, MV, or OP, and the name of the manufacturer must be entered in the MIS Field. It must be entered if VIN Field is filled. For Omnixx users: If the VMA is AERO, ATV, COEQ, CYL, FARM, SNOW, SPEC, TRLR, or TRUK, then the VMAD must contain the name of the manufacturer. If entered, the VMA must also be entered. Spaces cannot be skipped. Hyphens or symbols should be used. More information can be found in Vehicular Data Codes Section of the NCIC 2000 Code Manual. The only valid VMO codes for vehicles with VST codes EB, EN, MV, or OP, are (blank), ATV, CYCL, DUN, GOF, GRT, SKT, SKW, TOY, TRA, TRW, or WHE. If the first four characters of the VMA are ASVE, the VMO must be AV or REP.
Violent Person File Chapter 29-10

(Aircraft)

(All-terrain vehicle, dune buggy, go-cart, golf cart, and snowmobile)

VMAD*

Vehicle Make Description

VMO

Vehicle Model

(Assembled automobile)
ACCESS Operations Manual Revised May 2013

(Construction equipment) (Farm and garden equipment) (Motorcycle)

If the first four characters of the VMA are COEQ, the VMO must be CE. If the first four characters of the VMA are FARM, the VMO must be FE. If the VST is MB, MC, MD, MK, MS, or MY, the VMO required is CYCL. If the first four characters of the VMA are SNOW or one of the valid snowmobile manufacturer's codes listed in Vehicular Data Codes, NCIC 2000 Code Manual, the VMO must be SKT, SKW, TRA, TRW, or WHE. If the first four characters of the VMA are TRLR or HMDE, the VMO must be TL. If the first four characters of the VMA are TRUK, the VMO must be TK. It must be entered if VIN Field is filled. Must be a numeric 1, 2, 3, or 4 to indicate which criteria code justifies entry into the file, as listed below: 1 – Assault on law enforcement 2 – Violent crime homicide/attempted homicide 3 – Violent crime with weapon 4 – Threat to law enforcement Must be a valid code as listed in the Vehicular Data Codes Section of the NCIC 2000 Code Manual. It must be entered if VIN Field is filled. Must represent the production (model) year during which the vehicle was manufactured (YYYY). Year cannot be more than 1 year beyond the current year. For entries of model year 1981 or later, when the VIN is 17 characters, the tenth position (vehicle year) of a VIN must represent the VYR. It must be entered if VIN Field is filled. Minimum of 050 and maximum of 499. More information can be found in the Personal Descriptors Section of the NCIC 2000 Code Manual.

(Snowmobile)

(Trailer)

(Truck)

VPC

Violent Person Criteria

VST

Vehicle Style

VYR

Vehicle Year

WGT

Weight

*Omnixx only

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-11

CHAPTER 29: SECTION 03: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.03.000

VIOLENT PERSON FILE INQUIRY TRANSACTIONS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE FIELD CODES FOR VIOLENT PERSON INQUIRY Field Name Required? Mandatory Mandatory Mandatory Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Optional Message Field Code HDR MKE ORI NAM DOB SEX RAC SOC FBI MNU SID OLN LIC LIS VIN OCA NIC INV Field Length 9-19 2-4 9-9 3-30 8-8 1-1 1-1 9-9 9-9 4-15 10-10 1-20 1-10 2-2 1-20 1-20 10-10 3-3 Data Type Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Numeric Alphabetic Alphabetic Numeric Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic, numeric Alphabetic, numeric Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic

Header Message Key Originating Agency Identifier Name Date of Birth Sex Race Social Security Number FBI Number Miscellaneous Number State Identification Number Operator’s License Number License Plate Number License Plate State Vehicle Identification Number Originating Agency Case Number NCIC Number Investigation Field

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-12

Attention Field Image Indicator Related Search Hit Expanded Name Search II.

Optional Optional Optional Optional

ATN IND RSH ENS

1-30 1-1 1-1 1-1

Alphabetic, numeric, special characters Alphabetic Alphabetic Alphabetic

GUIDELINES FOR VIOLENT PERSON INQUIRY A. Inquiries made with the NAM, SEX, RAC, and DOB are MFC driven and immediately follow the ORI in the inquiry. Inquiries using other numerical identifiers (SOC, OLN, MNU, NIC, etc.) must have the MFCs preceding those identifiers. An inquiry may be made by one, more than one, or all of the following identifiers: DOB, SOC, FBI, MNU, SID, and OLN. Additionally, inquiries may be made using LIC, LIS, and/or VIN, NAM and OCA, or NIC only. If DOB, SEX, RAC, SOC, FBI, MNU, or OCA is entered, NAM is required. If a positive response (hit) includes vehicle or license plate data, the Vehicle File should be queried to ascertain if the vehicle and/or license plate is stolen. The INV, ATN, IND, RSH, ENS, and RNG Fields are optional and can be added to the end of each inquiry. 1. If used, INV must be INV or ALL. a. INV/INV should be used if the inquiry is a non-field contact (i.e., office, squad room). This prevents a notice from being sent to a Department of Corrections supervising officer if the inquiry retrieves a record on the subject from the Supervised Persons File. If INV/ALL is used, then all exact match and near-hit records will return.

B.

C.

D.

b. 2.

The information entered into the optional ATN will be furnished to the Department of Corrections supervising officer when the inquiry retrieves a record from the Supervised Persons File. Inquiries may also contain an IND. If the image indicator is Y, image data related to each primary hit response will be returned. Inquiries may also contain a RSH Field. If RSH is Y, secondary hit responses will be returned for all linked records. a. The system links records when: (1) ORI/OCA matches the primary hit response and the dates of entry for those records are within 30 days of each other and The LKI/LKA are the same as ORI/OCA contained in the primary hit response.

3. 4.

(2) 5.

If the inquiry includes the ENS/Y, then additional searches are generated by using each input name part as a last name, interchanging the remaining name parts as given names.
Violent Person File Chapter 29-13

ACCESS Operations Manual Revised May 2013

a.

Example: Bryan, Morgan Lee; Bryan, Lee Morgan; Morgan, Lee Bryan; Morgan, Bryan Lee; Lee, Morgan Bryan; and Lee, Bryan Morgan

6.

Using the RNG Field will provide a specific response or a range of responses related to the inquiry. a. If RNG is used and is one number then only return the response in the record list that matches that number. For example, RNG/4 will return record response number 4. If two numbers are entered as RNG, then only return the candidates that match the two numbers and that are between the two numbers in the candidate list. For example, RNG/13-17 will return record responses 13 through 17. If RNG/ALL is used, then all exact match and near-hit records will return.

b.

c. III.

REQUIREMENTS FOR VIOLENT PERSON INQUIRY A. Inquiries can be made by: 1. NAM and at least one of the following: DOB with optional SEX and RAC, SOC, FBI, MNU, OLN, LIC with optional LIS, VIN, and/or OCA a. Example: W;QW..NAM/TEST, SUBJECT ONE.DOB/19040101. SEX/M.RAC/W W;QW..NAM/TEST, SUBJECT ONE.SOC/123223210 W;QW..NAM/TEST, SUBJECT ONE.DOB/19040101. OLN/TESTOLN171QB.LIC/123TEST.LIS/WA W;QW..NAM/TEST, SUBJECT ONE.DOB/19040101. VIN/12345678901234567890 2. NAM and DOB (or other field, like SOC, MNU, etc.) and optional fields INV, ATN, IND, RSH, ENS, and RNG a. Example: W;QW..NAM/TEST, SUBJECT ONE.DOB/19040101. INV/INV.ATN/OFFICER JON JONES.RSH/Y.ENS/Y Example: W;QW..SID/WA10150089 Inquiries made by NIC only receive a NCIC response for an exact match. Example: W;QW..NIC/L146203706

3.

SID a.

4.

NIC a. b.

IV.

EXAMPLE OF VIOLENT PERSON INQUIRY RESPONSE A. NCIC No Record Response
Violent Person File Chapter 29-14

ACCESS Operations Manual Revised May 2013

NO NCIC WANT NAM/SMITH, JOHN J DOB/19511012 SEX/M RAC/W NO RECORD VIN/ABC123DEF45678901 ***VERIFY VIN/ABC123DEF45678901; IT DOES NOT CONFORM TO VIN STANDARDS FOR 1981 AND LATER VEHICLES. ***MESSAGE KEY QW SEARCHES WANTED PERSON FILE FELONY RECORDS REGARDLESS OF EXTRADITION AND MISDEMEANOR RECORDS INDICATING POSSIBLE INTERSTATE EXTRADITION FROM THE INQUIRING AGENCY'S LOCATION. ALL OTHER NCIC PERSONS FILES ARE SEARCHED WITHOUT LIMITATIONS. B. NCIC Positive (Hit) Response NCIC TIME: 1105 DATE: 041013 TO: SP8H WAWSP0007 WARNING-A SUBJECT IN THIS RESPONSE HAS BEEN IDENTIFIED AS A VIOLENT OFFENDER OR A SERIOUS THREAT TO LAW ENFORCEMENT OFFICERS. REVIEW THIS RESPONSE IN ITS ENTIRETY TO OBTAIN ADDITIONAL INFORMATION ON THIS SUBJECT. USE EXTREME CAUTION IN APPROACHING THIS INDIVIDUAL. ***MESSAGE KEY QW SEARCHES WANTED PERSON FILE FELONY RECORDS REGARDLESS OF EXTRADITION AND MISDEMEANOR RECORDS INDICATING POSSIBLE INTERSTATE EXTRADITION FROM THE INQUIRING AGENCY'S LOCATION. ALL OTHER NCIC PERSONS FILES ARE SEARCHED WITHOUT LIMITATIONS. WARNING-THE SUBJECT IN THIS RECORD HAS BEEN DEEMED A SERIOUS THREAT TO LAW ENFORCEMENT OFFICERS. USE CAUTION IN APPROACHING THIS INDIVIDUAL. DO NOT ARREST OR DETAIN BASED SOLELY ON THIS INFORMATION. MKE/VIOLENT PERSON CMC/00 - ARMED AND DANGEROUS ORI/WAWSP0007 NAM/TEST, SUBJECT 0NE SEX/M RAC/W ETN/N POB/WA DOB/19180108 HGT/510 WGT/175 EYE/BR0 HAI/BR0 CTZ/US SKN/DRK SMT/SC R HND FPC/01120112011201120112 MNU/PI-MNU12345 SOC/204111111 OLN/TESTYKL171QB OLS/WA OLY/2016 VPC/4 - THREAT TO LAW ENFORCEMENT OCA/TEST007 MIS/SUBJECT CHARGED DEPUTY DURING TRAFFIC ST0P AND PUNCHED HIM MULTIPLE TIMES MIS/BEF0RE BEING RESTRAINED VERIFY 360 555 1212 LIC/ABC123 LIS/MD LIY/2014 LIT/PC DNA/N ORI IS WASHINGTON STATE PATROL OLYMPIA 360 705-5999
ACCESS Operations Manual Revised May 2013 Violent Person File Chapter 29-15

NIC/L740000187 DTE/20130410 1404 EDT DLU/20130410 1404 EDT

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-16

CHAPTER 29: SECTION 04: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.04.000

VIOLENT PERSON FILE ENTRY TRANSACTIONS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE FIELD CODES FOR VIOLENT PERSON ENTRY Field Name Required? Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Optional Optional Conditional Mandatory Mandatory Mandatory Mandatory Conditional Optional Optional Optional Conditional Conditional Conditional Conditional Message Field Code HDR MKE ORI NAM SEX RAC POB CTZ DOB HGT WGT EYE HAI FBI SKN SMT FPC MNU SOC OLN OLS Field Length 9-19 3-4 9-9 3-30 1-1 1-1 2-2 2-2 8-8 3-3 3-3 3-3 3-3 1-9 3-3 3-10 20-20 4-15 9-9 1-20 2-2 Data Type Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic Alphabetic Alphabetic Alphabetic Numeric Numeric Numeric Alphabetic Alphabetic Alphabetic, numeric Alphabetic Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Numeric Alphabetic, numeric Alphabetic
Chapter 29-17

Header Message Key Originating Agency Identifier Name Sex Race Place of Birth Citizenship Date of Birth Height Weight Eye Hair FBI Number Skin Tone Scars, Marks, Tattoos, and Other Characteristics Fingerprint Classification Miscellaneous Number Social Security Number Operator’s License Number Operator’s License State
ACCESS Operations Manual Revised May 2013

Violent Person File

Operator’s License Year of Expiration Originating Agency Case Number Linkage Agency Identifier Linkage Case Number DNA Profile Indicator DNA Location Caution and Medical Conditions License Plate Number License Plate State License Plate Year License Plate Type Vehicle Identification Number Vehicle Year Vehicle Make Vehicle Make Description* Vehicle Model Vehicle Style Vehicle Color Vehicle Color Second* Miscellaneous Ethnicity Violent Person Code *Omnixx only II.

Conditional Mandatory Optional Conditional Optional Conditional Optional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Optional Conditional Optional Conditional Optional Optional Mandatory

OLY OCA LKI LKA DNA DLO CMC LIC LIS LIY LIT VIN VYR VMA VMAD VMO VST VCO VCOS MIS ETN VPC

2-4 1-20 9-9 1-20 1-1 1-250 2-2 1-10 2-2 2-4 2-2 1-20 4-4 2-24 1-20 2-3 2-2 3-3 or 7-7 7-7 1-500 1-1 1-1

Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric, special characters Numeric Alphabetic, numeric Alphabetic Alphabetic, numeric Alphabetic Alphabetic, numeric Numeric Alphabetic Alphabetic Alphabetic, numeric Alphabetic, numeric Alphabetic Alphabetic Alphabetic, numeric, special characters Alphabetic Numeric

GUIDELINES FOR VIOLENT PERSON ENTRY A. The originating agency must account for all fields in the violent person record. All available data called for by the record format must be entered when the original entry is made. Missing data obtained at a later time should be promptly added through the use of a modify message. A 24/7 hit confirmation phone number must be placed in the MIS Field. The MIS Field must contain a brief description of why the subject is entered into the Violent Person File.

B. C.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-18

1.

Example: SUBJECT CHARGED DEPUTY DURING TRAFFIC STOP AND PUNCHED HIM MULTIPLE TIMES BEFORE BEING RESTRAINED VERIFY 360 555 1212

III.

REQUIREMENTS FOR VIOLENT PERSON ENTRY A. The following fields are mandatory for acceptance of a violent person entry in NCIC: 1. HDR, MKE, ORI, NAM, SEX, RAC, HGT, WGT, EYE, HAI, OCA, VPC, and at least one of the following numeric identifiers: DOB; FBI; MNU; SOC; OLN with OLS and OLY; LIC with LIS, LIY, and LIT; VIN with VYR, VMA, and VST.

B. IV. A.

The entry will be rejected if one of the mandatory fields is left unfilled. Violent Person Entry N;EVP.WAWSP0007.TEST, SUBJECT ONE.M.W.WA.US. 19180108.510.175.BRO.BRO..DRK.SC R HND. 01120112011201120112.PI-MNU12345.204111111. TESTYKL171QB.WA.2016.TEST007...N..00.ABC123.MD.2014.PC. ......SUBJECT CHARGED DEPUTY DURING TRAFFIC STOP AND PUNCHED HIM MULTIPLE TIMES BEFORE BEING RESTRAINED VERIFY 360 555 1212.N.4

EXAMPLE OF VIOLENT PERSON ENTRY

V.

EXAMPLE OF VIOLENT PERSON ENTRY ACKNOWLEDGMENT A. NCIC Acknowledgment NCIC TIME: 0852 DATE: 041013 TO: SP8H WAWSP0007 NAM/TEST, SUBJECT 0NE NIC/L520000259 OCA/TEST007

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-19

CHAPTER 29: SECTION 05: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.05.000

VIOLENT PERSON FILE MODIFY TRANSACTIONS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE FIELD CODES FOR VIOLENT PERSON MODIFICATION Field Name Required? Mandatory Mandatory Mandatory Conditional Conditional Conditional Message Field Code HDR MKE ORI NAM NIC OCA Field Length 9-19 3-3 9-9 3-30 10-10 1-20 Data Type Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic, numeric, special characters

Header Message Key Originating Agency Identifier Name NCIC Number Originating Agency Case Number Any field(s) from entry transaction II.

GUIDELINES FOR VIOLENT PERSON MODIFICATION A. 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 a violent person record. A modification message to the base record to delete information in a field will cause the same data in the supplemental record to move up to the base record, except for vehicle and license data. Required fields can be modified; however, they cannot be deleted by the use of a modify entry. When modifying the MIS Field, all the information you desire to be shown in the MIS Field must be entered (additional information cannot be added on to what is already contained in the MIS Field). To delete information from a field, use the MFC followed by a period (e.g., SMT/.). You cannot delete data from a required field.

B.

C. D.

E.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-20

1.

To remove all operator license data a modification message must be sent with the MFCs. This will remove the OLN, OLY, and OLS Fields. a. Example: OLN/.OLY/.OLS.

2.

To remove all license plate data a modification message must be sent with the MFCs. This will remove the LIC, LIS, LIY, and LIT Fields. a. Example: LIC/.LIS/.LIY/.LIT/.

3.

To remove all vehicle data a modification message must be sent with the MFCs. This will remove the VIN, VYR, VMA/VMAD, VMO, VST, and VCO/VCOS. a. Example: VIN/.VYR/.VMA/.VMO/.VST/.VCO/.

4. III.

To remove both the LIC and VIN sets, a modification message must be sent with MFC “LIC-VCO/.”

REQUIREMENTS FOR VIOLENT PERSON MODIFICATION A. The modify transaction consists of the message key, ORI, two record identifiers, and the fields being modified. The fields being modified must be identified by their appropriate Message Field Codes. Modifications on a violent person can be made by: 1. NAM and OCA a. Example: N;MVP.WAWSP0007.NAM/TEST, SUBJECT ONE. OCA/TEST007.SMT/SC L ARM Example: N;MVP.WAWSP0007.NAM/TEST, SUBJECT ONE. NIC/L520000259.SMT/SC L ARM Example: N;MVP.WAWSP0007.NIC/L520000259.OCA/TEST007. SMT/SC L ARM

B.

2.

NAM and NIC a.

3.

NIC and OCA a.

IV.

EXAMPLE OF VIOLENT PERSON MODIFICATION ACKNOWLEDGMENT A. NCIC Acknowledgment NCIC TIME: 0955 DATE: 041013 TO: SP8H WAWSP0007 MODIFY NAM/TEST, SUBJECT 0NE OCA/TEST007

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-21

CHAPTER 29: SECTION 06: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.06.000

VIOLENT PERSON FILE SUPPLEMENTAL TRANSACTIONS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE FIELD CODES FOR VIOLENT PERSON SUPPLEMENTAL Field Name Required? Mandatory Mandatory Mandatory Conditional Conditional Conditional Optional Optional Optional Optional Optional Optional Conditional Conditional Optional Conditional Conditional Conditional Message Field Code HDR MKE ORI NAM NIC OCA AKA DOB SMT MNU SOC OLN OLS OLY LIC LIS LIY LIT Field Length 9-19 4-4 9-9 3-30 10-10 1-20 3-30 8-8 3-10 4-15 9-9 1-20 2-2 4-4 1-10 2-2 4-4 2-2 Data Type Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric, special characters Numeric Alphabetic Alphabetic, numeric, special characters Numeric Alphabetic, numeric Alphabetic Alphabetic, numeric Alphabetic, numeric Alphabetic Alphabetic, numeric Alphabetic
Chapter 29-22

Header Message Key Originating Agency Identifier Name NCIC Number Originating Agency Case Number Alias Date of Birth Scars, Marks, Tattoos, and Other Characteristics Miscellaneous Number Social Security Number Operator’s License Number Operator’s License State Operator’s License Year of Expiration License Plate Number License Plate State License Plate Year License Plate Type
ACCESS Operations Manual Revised May 2013

Violent Person File

Vehicle Identification Number Vehicle Year Vehicle Make Vehicle Make Description* Vehicle Model Vehicle Style Vehicle Color Vehicle Color Second* Caution and Medical Conditions Citizenship Image NCIC Number Image Type *Omnixx only II.

Optional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Optional Optional Optional Conditional

VIN VYR VMA VMAD VMO VST VCO VCOS CMC CTZ IMN IMT

1-20 4-4 2-24 1-20 2-3 2-2 3-3 or 7-7 7-7 2-2 2-2 1-10 1-1

Alphabetic, numeric Numeric Alphabetic Alphabetic Alphabetic, numeric Alphabetic, numeric Alphabetic Alphabetic Numeric Alphabetic Alphabetic, numeric Alphabetic

GUIDELINES FOR VIOLENT PERSON SUPPLEMENTAL A. A supplemental entry is utilized when additional identifiers, such as an alias or scars, marks, tattoos, and other characteristics etc., need to be added to a person record. To enter information into a supplemental record, that field must first be filled in the base record. That is, if an attempt is made to enter a SOC as a supplemental data entry, a reject will occur if no SOC exists in the base record. The following is a list of fields that can be appended to a record on file and the maximum number that can be added to a record. A maximum of nine additional identifiers can be added with each supplemental data entry message. Field MFC AKA DOB SMT MNU SOC CMC CTZ OLN LIC Max Number 99 9 9 9 9 9 9 9 9

B.

C.

Alias Date of Birth Scars, Marks, Tattoos, and Other Characteristics Miscellaneous Number Social Security Number Caution and Medical Conditions Citizenship Operator’s License Number, State, and Year of Expiration (Entered as a Set) License Plate Number, State, Year of Expiration, and Type (Entered as a Set)

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-23

Vehicle Identification Number, Year, Make, Model, Style, and Color (Entered as a Set) Image NCIC Number and Image Type (Entered as a Set) D.

VIN IMN

9 1

Supplemental entries on AKA, DOB, SMT, MNU, SOC, CMC, and CTZ must be identified only one time in each supplemental entry. 1. Example: AKA/SMITH, JOHN J.JOHNSON, JOHN J DOB/19490804.19510101 Example: LIC/ABC123.WA.1986.PC.LIC/XYZ123.WA.1989.PC VIN/12345678901234567890.2000.ACUR.INT.2D.BLK/RED. VIN/32165498703216549870.2012.HOND.ACC.4D.BLU OLN/ABD15577AB.WA.2012.OLN/NEWOLN1554.CA.2011

E.

Items which are entered as a set must be identified before each set. 1.

F.

When entering sets of information, all fields must be accounted for. If a field is not available or unknown, then no information can be entered for that set. A field separator (.) must be used to identify the missing field. A maximum of nine additional identifiers of various kinds may be entered in one supplemental entry message. Additional messages are required if more identifiers are to be entered. Each AKA, DOB, SMT, MNU, SOC, CTZ, or CMC is counted as one identifier. Each set of data relating to an OLN, LIC, VIN, or IMN is likewise counted as one identifier. The supplemental entry may be made only by the agency that entered the person record. Supplemental images must be entered using the Enter Image (EIM) transaction. Please refer to the Image File for more information. The supplemental transaction consists of the message key, ORI, two record identifiers, and the fields being supplemented. The fields being supplemented must be identified by their appropriate Message Field Codes. Supplemental transactions on a violent person can be made by: 1. NAM and OCA a. Example: N;ENVP.WAWSP0007.NAM/TEST,SUBJECT ONE. OCA/TEST007.DOB/19440101.19400804. VIN/32132132104567891230.2004.TOYT.AVA.2D.SIL

G.

H. I. III.

REQUIREMENTS FOR VIOLENT PERSON SUPPLEMENTAL A.

B.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-24

2.

NAM and NIC a. Example: N;ENVP.WAWSP0007.NAM/TEST,SUBJECT ONE. NIC/L520000259.DOB/19440105.19400805. VIN/92132132104567891230.2004.TOYT.AVA.2D.SIL Example: N;ENVP.WAWSP0007.NIC/L520000259.OCA/TEST007. DOB/19440106.19400806.VIN/72132132104567891230. 2004.TOYT.AVA.2D.SIL

3.

NIC and OCA a.

IV.

EXAMPLE OF VIOLENT PERSON SUPPLEMENTAL ACKNOWLEDGMENT A. NCIC Acknowledgment NCIC TIME: 1032 DATE: 041013 TO: SP8H WAWSP0007 SUPP NIC/L520000259 OCA/TEST007

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-25

CHAPTER 29: SECTION 07: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.07.000

VIOLENT PERSON FILE CANCEL SUPPLEMENTAL TRANSACTIONS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE FIELD CODES FOR VIOLENT PERSON CANCEL SUPPLEMENTAL Field Name Required? Mandatory Mandatory Mandatory Conditional Conditional Conditional Conditional Mandatory Optional Optional Optional Optional Conditional Conditional Optional Conditional Conditional Conditional Message Field Code HDR MKE ORI NAM OCA NIC AKA DOB SMT MNU SOC OLN OLS OLY LIC LIS LIY LIT Field Length 9-19 4-4 9-9 3-30 1-20 10-10 3-30 8-8 3-10 4-15 9-9 1-20 2-2 4-4 1-10 2-2 4-4 2-2 Data Type Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic, numeric, special characters Numeric Alphabetic Alphabetic, numeric, special characters Numeric Alphabetic, numeric Alphabetic Alphabetic, numeric Alphabetic, numeric Alphabetic Alphabetic, numeric Alphabetic
Chapter 29-26

Header Message Key Originating Agency Identifier Name Originating Agency Case Number NCIC Number Alias Date of Birth Scars, Marks, Tattoos, and Other Characteristics Miscellaneous Number Social Security Number Operator’s License Number Operator’s License State Operator’s License Year of Expiration License Plate Number License Plate State License Plate Year License Plate Type
ACCESS Operations Manual Revised May 2013

Violent Person File

Vehicle Identification Number Vehicle Year Vehicle Make Vehicle Make Description* Vehicle Model Vehicle Style Vehicle Color Vehicle Color Second* Caution and Medical Conditions Citizenship *Omnixx only II.

Optional Conditional Conditional Conditional Conditional Conditional Conditional Conditional Optional Optional

VIN VYR VMA VMAD VMO VST VCO VCOS CMC CTZ

1-20 4-4 2-24 1-20 2-3 2-2 3-3 or 7-7 7-7 2-2 2-2

Alphabetic, numeric Numeric Alphabetic Alphabetic Alphabetic, numeric Alphabetic, numeric Alphabetic Alphabetic Numeric Alphabetic

GUIDELINES FOR VIOLENT PERSON CANCEL SUPPLEMENTAL A. A cancel supplemental is utilized when additional identifiers that were added using a supplemental transaction, such as an alias or scars, marks, tattoos, and other characteristics etc., need to be removed from a person record. To remove information from a supplemental record, that field must first be filled in the base record. That is, if an attempt is made to remove a SOC as a supplemental data entry, a reject will occur if no SOC exists in the supplemental record. The following is a list of fields that can be removed from a supplemental record on file and the maximum number that can be removed from a record. A maximum of nine additional identifiers can be removed with each cancel supplemental message. Field MFC AKA DOB SMT MNU SOC CMC CTZ OLN LIC VIN Max Number 99 9 9 9 9 9 9 9 9 9

B.

C.

Alias Date of Birth Scars, Marks, Tattoos, and Other Characteristics Miscellaneous Number Social Security Number Caution and Medical Conditions Citizenship Operator’s License Number, State, and Year of Expiration (Entered as a Set) License Plate Number, State, Year of Expiration, and Type (Entered as a Set) Vehicle Identification Number, Year, Make, Model, Style, and Color (Entered as a Set)
ACCESS Operations Manual Revised May 2013 Violent Person File

Chapter 29-27

Image NCIC Number and Image Type (Entered as a Set) D.

IMN

1

Each set of operator's license or license plate data (multiple data element fields) must be preceded by OLN/ or LIC/, respectively, and all data elements of the set must appear exactly as they appear in the supplemental record on file. 1. Example: LIC/ABC123.WA.1986.PC VIN/12345678901234567890.2000.ACUR.INT.2D.BLK/RED

E.

When canceling vehicular data, only the VIN and VMA are required following VIN/, with a period to account for the intervening VYR. 1. Example: VIN/1L69X6JO23456..CHEV

F.

A maximum of nine identifiers of various kinds can be cancelled in one message. Additional messages are required if more than nine identifiers are to be cancelled. Each AKA, DOB, SMT, MNU, CTZ, or SOC is counted as one identifier. Each set of OLN, LIC, VIN, or IMN (multiple data element fields) is counted as one identifier. The cancel supplemental transaction may be made only by the agency that entered the person record. The cancel supplemental transaction consists of the message key, ORI, two record identifiers, and the fields being cancelled. The fields being cancelled must be identified by their appropriate Message Field Codes. Cancel supplemental transactions on a violent person can be made by: 1. NAM and OCA a. Example: N;XNVP.WAWSP0007.NAM/TEST,SUBJECT ONE. OCA/TEST007.DOB/19440101.19400804. VIN/32132132104567891230.2004.TOYT.AVA.2D.SIL Example: N;XNVP.WAWSP0007.NAM/TEST,SUBJECT ONE. NIC/L520000259.DOB/19440105.19400805. VIN/92132132104567891230.2004.TOYT.AVA.2D.SIL

G. III.

REQUIREMENTS FOR VIOLENT PERSON CANCEL SUPPLEMENTAL A.

B.

2.

NAM and NIC a.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-28

3.

NIC and OCA a. Example: N;XNVP.WAWSP0007.NIC/L520000259.OCA/TEST007. DOB/19440106.19400806.VIN/72132132104567891230. 2004.TOYT.AVA.2D.SIL

IV.

EXAMPLE OF VIOLENT PERSON CANCEL SUPPLEMENTAL ACKNOWLEDGMENT A. NCIC Acknowledgment NCIC TIME: 1045 DATE: 041013 TO: SP8H WAWSP0007 CANCEL SUPP NAM/TEST,SUBJECT 0NE OCA/TEST007 DOB/19440101 DOB/19400804 VIN/32132132104567891230.2004.T0YT.AVA.2D.SIL.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-29

CHAPTER 29: SECTION 08: Procedure #: Supersedes: Applies To: I. All ACCESS Users 29.08.000

VIOLENT PERSON FILE CANCEL TRANSACTIONS Effective Date: See Also: CALEA: February 1, 2013

MESSAGE FIELD CODES FOR VIOLENT PERSON CANCEL Field Name Required? Mandatory Mandatory Mandatory Conditional Conditional Conditional Mandatory Message Field Code HDR MKE ORI NAM NIC OCA DOC Field Length 9-19 3-3 9-9 3-30 10-10 1-20 8-8 Data Type Alphabetic, numeric, special characters Alphabetic Alphabetic, numeric Alphabetic, numeric, special characters Alphabetic, numeric Alphabetic, numeric, special characters Numeric

Header Message Key Originating Agency Identifier Name NCIC Number Originating Agency Case Number Date of Cancellation II.

GUIDELINES FOR VIOLENT PERSON CANCEL A. Cancellation of a record is restricted to the agency that entered the record. A cancellation message is used when the entering agency determines that the record is invalid or the entering agency determines the subject no longer poses a threat to law enforcement officers. The cancel transaction consists of the message key, ORI, two record identifiers, and the date of cancel. Cancellation can be made by: 1. NAM and OCA a. Example: N;XVP.WAWSP0007.NAM/TEST,SUBJECT ONE. OCA/TEST007.20130410

III.

REQUIREMENTS FOR VIOLENT PERSON CANCEL A. B.

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-30

2.

NAM and NIC a. Example: N;XVP.WAWSP0007.NAM/TEST,SUBJECT ONE. NIC/L420000353.20130410 Example: N;XVP.WAWSP0007.NIC/L320000243.OCA/TEST007. 20130410

3.

NIC and OCA a.

IV.

EXAMPLE OF VIOLENT PERSON CANCEL ACKNOWLEDGMENT A. NCIC Acknowledgment NCIC TIME: 1053 DATE: 041013 TO: SP8H WAWSP0007 CANCEL NAM/TEST,SUBJECT 0NE OCA/TEST007

ACCESS Operations Manual Revised May 2013

Violent Person File

Chapter 29-31

Sign up to vote on this title
UsefulNot useful