chapter 18 gang

7/27/2019 Chapter 18 Gang

1/50

Chapter 18

Gang File

WACIC Manual Chapter #18-1Revised 10/2010

SECTION 01: INTRODUCTION 4I. DEFINITIONS 4

A. PURPOSE 4B. SECURITY 4C. DEFINITION OF GANG FILE 5SECTION 02: INQUIRIES 6I. PROCEDURE 6

A. SYNTAX 6B. GUIDELINES FOR INQUIRIES 6C. OPERATIONAL INQUIRIES 6SECTION 03: GRC FIELDS AND EDITS 8I. DEFINITIONS 8

A. GRCMESSAGE KEYS 8B. GRCMESSAGE KEYS 8SECTION 04: ENTRY 11I. PROCEDURE 11

A.

GANG GROUP RECORD ENTRY MASK 11

B. EXAMPLE OF ENTRIES 11C. PRIMARY ORIENTRY 12D. SUBSEQUENT ENTRY 12E. ENTRYACKNOWLEDGEMENTS 12SECTION 05: MODIFY TRANSACTIONS 14I. DEFINITIONS 14

A. AGENCY MODIFICATION 14II. PROCEDURE 14

A. SYNTAX 14B. GRCMODIFY FIELD EDITS 15C. EXAMPLE OF MGGTRANSACTION: 15SECTION 06: LOCATE TRANSACTIONS 17I. PROCEDURE 17

A. LOCATES 17


2/50

Chapter 18 Gang File


SECTION 07: CLEAR TRANSACTIONS 18I. PROCEDURE 18

A. CLEARS 18SECTION 08: CANCEL TRANSACTIONS 19I. PROCEDURE 19

A. WHEN TO USE A CANCELLATION MESSAGE 19B. SYNTAX 19C. MODIFY FIELD EDITS 20D. EXAMPLE OF GRCCANCELLATION 20E. GRCACKNOWLEDGEMENT 20SECTION 09: SUPPLEMENTAL TRANSACTIONS 21I. DEFINITIONS 21

A. ENTRY 21II. PROCEDURE 21

A. SYNTAX 21B. EXAMPLE OF GRCSUPPLEMENTAL ENTRY 21C. GRCSUPPLEMENTALACKNOWLEDGEMENT 22D. SUPPLEMENTAL DATA CANCELLATION 22F. GRCSUPPLEMENTAL MODIFICATION 22G. ACKNOWLEDGMENT 22H. ADDITIONAL GUIDELINE FOR GRCSUPPLEMENTAL DATA 23SECTION 10: GROUP MEMBER CAPABILITY 24I. DEFINITIONS 24

A. GROUP MEMBER CAPABILITY (GMC) 24B. GMCCRITERIA FOR ENTRY 25C. RETENTION PERIOD 26D. GMCVALIDATION 27SECTION 11: GMC INQUIRY 28I. PROCEDURE 28

A. INQUIRY SYNTAX 28B. GUIDELINES FOR INQUIRIES 28C. OPERATIONAL INQUIRY 29D. GMCMESSAGE KEYS 30SECTION 12: GMC ENTRY 39


3/50


4/50

Chapter 18

Gang File


CHAPTER 18: The Gang FileSECTION 01: Introduction

Procedure #: 18.01.000

Special Order:

Supersedes: WACIC Manual 2009 Edition

Applies to:ACCESS Users

Effective Date: October 1, 2009

See Also:

CALEA:

I. DEFINITIONS

A. Purpose

1. The Gang File is designed to provide identifying information about violentcriminal gangs and members of those gangs to law enforcement personnel.This information serves to warn law enforcement officers of the potentialdanger posed by violent individuals and to promote the exchange ofinformation about gangs and members to facilitate criminal investigations.

Because the Gang File information is based, in part, on investigativeinformation not previously subject to independent judicial review, strict

adherence to policy on the security, use, and dissemination of Gang Fileinformation is necessary.

B. Security

1. Gang File information is exclusively for the use of criminal justice agencies forcriminal justice purposes. In no case shou ld Gang Fi le informat ion b edisseminated to any n on-cr iminal just ice agency o r subject of a hi t .(See 28 Code of Federal Regulations 20.3 for the definition of a criminal

justice agency.)

2. The security measures to be accorded criminal history record information, asset out in the CJIS Security Policy, should be followed with respect to theGang File and the information contained therein.


5/50



C. Definition of Gang File

1. Essentially, those criminal activities which affirm entry as a gang, such asmurder, extortion, firearms, or explosive offenses, assault, and burglary. For

purposes of entry in the Group Reference Capability (GRC), a gang mustmeet the following definition:

a. The group must be an ongoing organization, association, or group of threeor more people; and

b. The group must have a common interest and/or activity characterized bythe commission of or involvement in a pattern of criminal activity ordelinquent conduct.

(1) Criminal or delinquent conduct includes narcotics distribution, firearms,

or explosives violations, murder, extortion, obstruction of justice(including witness intimidation and/or tampering), and any other violentoffenses such as assault, threats, burglary, and or carjacking.

(2) Delinquent conduct as with the Wanted Person File is conduct of ajuvenile which would be a crime if committed by an adult.

(3) Criminal conduct includes acts committed during incarceration whichare often labeled disruptive and which could be punished as crimes.

2. The Gang File resides only in the NCIC system; there is no corresponding filein the WACIC system. All Gang File transactions, although sent using theWACIC transaction code "W," are routed by the ACCESS system to NCIC

only.

3. The Group Member Capability (GMC) provides information, in a format similarto Wanted Person File records, about individual members of gangs. Thiscapability is accessed with every (QW) inquiry (or any related transactionsuch as an entry, which acts as an inquiry), and/or by an off-line searchtransaction.

4. Entry of a gang member in the Group Member Capability (discussed inSection 3) is predicated on the entry or preexistence of a GRC record for thegroup to which that member belongs.


6/50



CHAPTER 18: Gang FileSECTION 02: Inquiries


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. Syntax

Field ExampleHeader W;Message Key QGGOriginating Agency Identifier WA0340500GROUP NAME HELLS ANGELSSUBGROUP NAME NOMADSEnd of Text (Send)

B. Guidelines for Inquiries

1. The QGG inquiry is directed to the gang/terrorist reference data file only. TheGRC can be queried using GNG only, SGP only, or GNG and SGP, using theQGG transaction. Multiple records may be returned if only GNG or SGP areutilized.

2. It is possible that an inquiry based solely on GNG or a SGP alone may returna large number of records (for example, "CRIPS-LRWA") which may prove tobe of little value because of that number and variety. Care should be used inutilizing a QGG transaction based solely on the GNG or SGP. The NCICCode Manual should be consulted for the appropriate GNG and SGP name tobe used in any query.

C. Operational Inquiries

1. With Group and SubGroup

W;QGG.WA0380900.GNG/CRIPS-LRWA.SGP/MAIN ST-LRWA(Send)


7/50



2. With Group Only

W;QGG.WA0380900.GNG/CRIPS-LRWA(Send)

3. With Subgroup Only

W;QGG.WA0380900.SGP/MAIN ST-LRWA(Send)

D. Response

NCIC TIME: 1341 DATE: 110197 TO: LITPDWA0380900

MKE/CRIMINAL GANGGNG/CRIPS-LRWA SGP/MAIN ST-LRWACONTACT AGENCIES:CA1012705 SGT JACOBS, GANG UNIT 814-743-2355CAFBILA00 SA L PEREZ - 814-783-2122MD1012600 GANG UNIT - 301-856-0017DATE FIRST ENTRY/101097TTO/TAT R CHK DAGGERTTO/TAT L CHK TEARDROPDRS/BRITISH KNIGHTS SNEAKERSDRS/BLACK CHISOX CAPDRS/BLUE BANDANNAHND/CIRCLED THUMB & RING FNGRGTI/BKGTI/50SMIS/PROFESS TO ATTACK POLICE ON ANY CONTACTCONTACT AGENCIES LISTED FOR FURTHER INFORMATION ON THIS GANG


8/50



CHAPTER 18: WACIC Gang FileSECTION 03: GRC Fields and Edits


Special Order:




See Also:

CALEA:

I. DEFINITIONS

A. GRC Message Keys

Entry Modify CancelCriminal Gang EGG MGG XGGSupplemental Data EGGN XGGN

1. All transactions, subsequent to an entry, are based on the type of group firstentered (e.g., EGG), and the translation will appear based on that originalMKE. Because entry is based on approved group/subgroup names, theclassification of that group/subgroup in the NCIC Code Manual will

predetermine the MKE used for entry.

B. GRC Message Keys


9/50



Required: Y Yes Data Type: A Alphabetic

N No N Numeric

C Conditional S Special Characters

1. MKE (Message Key)

a. The MKE field must be a valid message key.

2. ORI (Originating Agency Identifier)

a. The ORI field must be a valid NCIC-assigned ORI. The first twocharacters must be alphabetic.

3. GNG (Group Name)

a. The GNG field must be a valid NCIC-assigned group name code.

4. SGP (Subgroup Name)

a. The SGP field must be a valid NCIC-assigned subgroup name code oruse NONE KNOWN.

5. POC (Agency Point of Contact)

a. The POC field must contain a name and phone number of contact withinthe agency responsible for the entry.

Field Name MFC Length Required Data Type

Header HDR 19 Y A,N,S

Message Key MKE 4 Y A

Originating AgencyIdentifier ORI 9 Y A,N

Group Name GNG 22 Y A,N,S

Sub Group Name SGP 35 Y A,N,S

Point of Contact POC 50 Y A,N,S

Identifying Tattoos TTO 35 N A,N,S

Identifying Dress DRS 25 N A,N,S

Identifying Hand Signals HND 25 N A,N,S

Identifying Graffiti GTI 25 N A,N,S

Miscellaneous MIS 250 N A,N,S


10/50



6. TTO (Identifying Tattoos)

a. The first ten characters of the TTO field must conform to a valid SMT codeas listed in Personal Descriptors, NCIC 2000 Code Manual.

7. DRS (Identifying Dress)

a. The DRS field must contain specific clothing worn by members of group.

8. HND (Identifying Hand Signals)

a. The HND field must contain hand gestures members of groups use toacknowledge each other and communicate silently.

9. GTI (Identifying Graffiti)

a. The GTI field must contain a description of graffiti used by group.

10.MIS (Miscellaneous)

a. The MIS field should be used to describe reasons for caution and furtherinformation about the group.


11/50


12/50



2. A subsequent agency cannot enter or modify any field in the record other thanits own ORI or Point of Contact (POC) fields.

C. Primary ORI Entry

W;EGG.WA0340500.CRIPS*LRWA.MAIN ST*LRWA.SGT JOHN DOE GANGUNIT 360/555-1111.TAT L CHK DAGGER OR TEARDROPS.BLUEBANDANA.CIRCLED THUMB & RING FNGR.BK 50S.PROFESS TO

ATTACK POLICE ON ANY CONTACT(Send)

1. This example includes the transaction code (W), message key (EGG), ORI ofthe entering agency (WA0340500), group name (CRIPS-LRWA), subgroupname (MAIN ST-LRWA), agency contact point (SGT ABNER DOUBLEDAY),a tattoo description (TAT L CHK DAGGER OR TEARDROPS), a dress/garbdescription (BLUE BANDANA), a hand sign description (CIRCLED THUMB &RING FNGR), a graffiti description (BK 50S), and a miscellaneous entry

(PROFESS TO ATTACK POLICE ON ANY CONTACT).

D. Subsequent Entry

W;EGG.WA0340300.CRIPS*LRWA.MAIN ST*LRWA.GANG UNIT, SGTJOHN DOE 360-555-1212(Send)

E. Entry Acknowledgements

1. Primary ORI Acknowledgement

1L01HEADERMD1012600MKE/CRIMINAL GANGGNG/CRIPS*WADC SGP/ROLLING 50SCONTACT AGENCIES:MD1012600 SGT ABNER DOUBLEDAY GANG UNIT 908 555 1111DATE FIRST ENTRY/20070107 1300 ESTTTO/TAT L CHK DAGGER OR TEARDROPSDRS/BLUE BANDANNAHND/CIR THUMB AND RING FNGRGTI/BK 50SMIS/PROFESS TO ATTACK POLICE ON ANY CONTACTCONTACT AGENCIES LISTED FOR FURTHER INFORMATIONNIC/Z000893451


13/50



2. Subsequent ORI Acknowledgement

1L01HEADERWA0340500

MKE/CRIMINAL GANGGNG/CRIPS-LRWA SGP/MAIN ST-LRWACONTACT AGENCIES:WA0340500 SGT JOHN DOE GANG UNIT 360/555-1212WA0340700 GANG UNIT, SGT JOHN JOHNSON 360-555-2222DATE FIRST ENTRY/19971025TTO/TAT L CHK DAGGER OR TEARDROPSDRS/BLUE BANDANNAHND/CIRCLED THUMB & RING FNGRMIS/PROFESS TO ATTACK POLICE ON ANY CONTACTCONTACT ORIS LISTED FOR FURTHER INFORMATION ON THIS GANG

a. This acknowledgment message would be the same even if the entryexample above (by WA0340300) had included TTO, DRS, HND, GTI,and/or MIS information. In that case, those fields would be automaticallyeliminated, leaving the ORI and POC fields appended to the record.


14/50



CHAPTER 18: Gang FileSECTION 05: Modify Transactions


Special Order:




See Also:

CALEA:

I. DEFINITIONS

A. Agency Modification

1. Modification of a GRC record, other than ORI/ POC data, can only be done bythe primary ORI. Records to be modified must include the GNG and SGP asit appears in the original record. Any agency with pertinent informationconcerning the TTO, DRS, HND, GTI, or MIS Fields should contact theprimary ORI/POC to request a modification of the GRC record informationwhen appropriate. Any ORI can modify its own ORI/POC data fields of aGRC record.

II. PROCEDURE

A. Syntax

Field ExampleHeader W;Message Key MGGOriginating Agency Identifier WA0340500GNG HELLS ANGELSSGP NOMADSEnd of Text (Send)

1. The modify transaction consists of the message key, ORI, two recordidentifiers, and the fields being modified. Permissible record identifiers are

GNG and SGP. The fields being modified must be identified by theirappropriate MFC.


15/50



B. GRC Modify Field Edits

Field Edits

MKEMust be a valid message key:MGG Modify GRC record

ORI Must be a valid ORI and match the ORI in the record beingmodified.

1st Record IdentifierThe first of two identifiers to identify the record to bemodified. Must be GNG.

2nd Record IdentifierThe second of two identifiers to identify the record to bemodified. Must be SGP.

Modified Field(s)The field(s) in the record to be modified. Each must beidentified by its MFC.

C. Example of MGG Transaction:

W;MGG.WA0340500.GNG/CRIPS*LRWA.SGP/MAINST*LRWA.

TTO/TAT R CHK DAGGER.MIS/COMMONLY USE MINORS UNDER 21(Send)

1. This transaction includes the transaction code (W), modification message key(MGG), ORI, Group name (CRIPS-LRWA), Subgroup name (MAIN ST-LRWA), Tattoo information (TAT R CHK DAGGER), and Miscellaneousinformation (COMMONLY USE MINORS UNDER 21 YO).

2. The record would now have only the TAT R CHK in the TTO field and"COMMONLY USE MINORS UNDER 21 YO" in the MIS field.

D. Modify Acknowledgements

1. Primary ORI modification


MODIFY GNG/CRIPS*LRWA SGP/MAIN ST*LRWA

a. If an agency other than the primary ORI attempts to modify any field otherthan that agency's own ORI and POC information, the transaction will berejected as follows:


REJECT - TTO/DRS/HND/GTIMIS/MAY BE MODIFIED ONLY BY PRIMARY ORI


16/50



b. Secondary Agency Modify Transaction

W;MGG.WA0340300.GNG/CRIPS*LRWA.SGP/MAIN ST*LRWA.POC/VGTF LT JOHN DOE, 360-555-1212(Send)

c. Secondary Agency Modify Acknowledgement

NCIC TIME: 1341 DATE: 110197 TO: ABCPDWA0340500

MODIFY GNG/CRIPS*LRWA SGP/MAIN ST*LRWA


17/50



CHAPTER 18: Gang FileSECTION 06: Locate Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. Locates

1. There are no locate procedures for the Gang File.


18/50



CHAPTER 18: Gang FileSECTION 07: Clear Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. Clears

1. There are no clear procedures for the Gang File.


19/50



CHAPTER 18: Gang FileSECTION 08: Cancel Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. When to Use a Cancellation Message

1. When an originating agency no longer has an interest in a GCR record, or therecord has been entered in error, the originating agency may cancel therecord.

2. If the oldest agency (primary ORI) cancels the record, that agencys ORIand POC are removed. If there are no other agencies associated to therecord, the entire record is cancelled. If there are other agencies associatedto the record, ownership of the GRC record is transferred to the next oldestagency which then becomes the Primary ORI. Cancellation by any agencyother than the primary ORI simply removes that agencys ORI and POC fromthe record.

B. Syntax

Field ExampleHeader W;Message Key XGGOriginating Agency Identifier WA0340500GNG HELLS ANGELSSGP NOMADSEnd of Text (Send)

1. The cancel transaction consists of the message key, ORI, two recordidentifiers, and the date of cancel. Permissible record identifiers are GNGand SGP.


20/50



C. Modify Field Edits

Field Edits

MKEMust be a valid message key:XGG Cancel GRC record

ORI Must be a valid ORI and match the ORI in the record beingcancelled.

1st Record IdentifierThe first of two identifiers to identify the record to becancelled. Must be GNG.

2nd Record IdentifierThe second of two identifiers to identify the record to becancelled. Must be SGP.

Date of CancelRequired by NCIC. Must be a valid date in the formatYYYYMMDD. Must be the current date or the current dateminus one day.

D. Example of GRC Cancellation

W;XGG.WA0340500.GNG/CRIPS*LRWA.SGP/MAIN ST*LRWA.010694(Send)

E. GRC Acknowledgement

1. Single-Interest Record Acknowledgement


CANCEL GNG/CRIPS*LRWA SGP/MAIN ST*LRWA

2. Multiple-Interest Record Acknowledgement


CANCEL - ORI AND POC HAVE BEEN DELETED FROM THIS RECORD

a. When the ORI/POC of the primary ORI are cancelled, such a responsewill also generate the following message to the new primary ORI and allother agencies listed by ORI in the record:

$.G.WA0340500.AGENCY WA0340500 HAS REMOVED ITS INTEREST INGNG/CRIPS*LRWA SGP/MAIN ST*LRWA.ORI WA0340500 IS NOWPRIMARY ORI FOR PURPOSES OF MODIFICATION ORSUPPLEMENTATION.


21/50



CHAPTER 18: Gang FileSECTION 09: Supplemental Transactions


Special Order:




See Also:

CALEA:

I. DEFINITIONS

A. Entry

1. Supplemental record entry can be accomplished only by the primary ORI.Any subsequent agency with an interest should contact the primary ORI torequest supplemental information when appropriate.

2. Multiple entries in the TTO, DRS, HND, and GTI fields, up to nine, areallowed via the EGGN transaction provided information exists in thecorresponding record field of the base record.

II. PROCEDURE

A. Syntax

Field ExampleHeader W;Message Key EGGNOriginating Agency Identifier WA0340500GNG HELLS ANGELSSGP NOMADSSupplemental Field(s) TTO/TAT R CHK DAGGEREnd of Text (Send)

B. Example of GRC Supplemental Entry

W;EGGN.WA0340500.GNG/CRIPS*LRWA.SGP/MAIN ST*LRWA.DRS/BLACK CHISOX CAP.BRITISH KNIGHTS SNEAKERS(Send)


22/50



1. This supplemental entry contains a transaction code (S), message key(EGGN), ORI (WA0340500), group name( CRIPS*LRWA), subgroup name(MAIN ST*LRWA), and two descriptions of dress (BLACK CHISOX CAP andBRITISH KNIGHTS SNEAKERS).

C. GRC Supplemental Acknowledgement


SUPP GNG/CRIPSLRWA SGP/MAIN STLRWA

1. You cannot modify a field in a supplemental record. The incorrect field mustbe cancelled and reentered.

D. Supplemental Data Cancellation

W;XGGN.WA0340500.GNG/CRIPS*LRWA.SGP/MAIN ST*LRWA.DRS/BRITISH KNIGHTS SNEAKERS(Send)

E. Acknowledgement to Supplemental Data Cancellation


CANCEL SUPP GNG/CRIPS*LRWA SGP/MAIN ST*LRWADRS/BRITISH KNIGHTS SNEAKERS

F. GRC Supplemental Modification

1. You cannot modify a field in a supplemental record. The incorrect field mustbe cancelled and re-entered. Here is an example of SupplementalCancellation.

W;XGGN.WA0340500.GNG/CRIPS*WADC.SGP/ROARING50S*WADC.DRS/BRITISH KNIGHTS SNEAKERS

G. Acknowledgment

NCIC TIME: 1341 DATE: 032506 TO: ABCPDWA0340500CANCEL SUPP GNG/CRIPS*WADC.SGP/ROARING 50S*WADCDRS/BRITISH KNIGHTS SNEAKERS


23/50



1. The GRC base record must be identified by GNG and SGP, in that order, witheach data element preceded by the proper MFC.

H. Additional Guideline for GRC Supplemental Data

1. A maximum of nine additional identifiers of any allowable type may beentered in one supplemental record entry message. Additional messages arerequired if more identifiers need to be entered.


24/50



CHAPTER 18: Gang FileSECTION 10: Group Member Capability


Special Order:




See Also:

CALEA:

I. DEFINITIONS

A. Group Member Capability (GMC)

1. The GMC will enable on-line entry and retrieval of information about qualifyinggang or terrorist organization members using name and/or numeric identifiersor vehicle information. The formats for both entry and inquiry are intended tobe similar to existing Wanted Person File or Vehicle File formats.

2. The GMC has two major functions: street officer protection and promoting theexchange of information about specific gangsters or terrorists.

3. The first function is accomplished by the automatic cross-search of the GangFile with all QW and QV inquiries, resulting in early notification and warningthat a subject encountered by an officer may be a potentially violent gangmember.

4. The second function is accomplished by reference to the ORI and OCA of therecord-entering agency allowing further, more extensive contact between theagencies. This feature is augmented by use of the GRC to obtain additionalinformation about the particular Gang Organization and subgroup listed in theGMC record.

5. Entry of a gang member in the GMC is predicated on the entry or pre-existence of a GRC record for the group to which that member belongs.

6. Unlike a GRC record, in which multiple agencies can express interest in asingle record, GMC records are individually entered by each agency. This willenable each agency to place any identifying information it has, which maydiffer between agencies, in its own record. Under this system, multiplerecords on one subject may be returned to an inquiring agency.


25/50



7. Like all NCIC records, probable cause to search or seize is not established bythe GMC record standing alone. In any case, arrest of a GMC record subjectwould not be appropriate based on his/her group affiliation. A caveat withevery GMC record warns against search or seizure established solely on thehit. This does not mean that a GMC record has no relevance to either

reasonable suspicion to detain a record subject (and perform anaccompanying field interrogation pursuant to such a detention), or to arrest arecord subject based on probable cause, or to search premises or vehiclesbased on probable cause.

B. GMC Criteria for Entry

1. The criteria identified to support entry should be documented for purposes ofvalidation and audit. Additionally, each GMC record must include a notationin the Criteria for Entry (ECR) Field. The following criteria must exist withrespect to any individual to be entered in the GMC:

a. Must be a member of a gang and subgroup thereof which meets thecriteria for and is entered in the GRC ; and

b. Has admitted membership in that gang or terrorist organization (andsubgroup) at the time of his/her arrest or incarceration; or meets any twoof the following:

(1) Has been identified by an individual of proven reliability as a groupmember.

(2) Has been identified by an individual of unknown reliability as a groupmember and that information has been corroborated in significantrespects.

(3) Has been observed by members of the entering agency to frequent aknown group's area, associate with known group members, and/oraffect that group's style of dress, tattoos, hand signals or symbols.

(4) Has been arrested on more than one occasion with known groupmembers for offenses consistent with group activity.

(5) Has admitted membership in the identified group at any time other thanarrest or incarceration.


26/50



2. GMC Criteria for Entry Relationship to GRC

a. As stated above, the first and overriding criteria for entry of a GMC recordis that the GNG and SGP must match a gang or terrorist organizationalready entered in the GRC. A GRC record must specifically be Gang

Organization. The GMC record must follow this existing designation. Forexample, for the group GNG/CRIPS and subgroup SGP/roaring 50Sentered in the GRC as a Gang by the EGG message key; any individualentered in the GMC with that identical GNG and SGP must be entered asa Gang Member (EGM). An attempt to enter that person as a TerroristOrganization Member through the EGMT transaction would be rejected,producing the following message: REJECT MESSGE KEY ERROR

b. It is not necessary that an agency wishing to enter a GMC record enter oralready have on file a GRC record corresponding to the group/subgroup tobe entered in the GMC record. It is only necessary that some agency

enter such record on file in the GRC. At any time such GRC record is fullycancelled, all corresponding GMC records with that group/subgroup will bepurged.

c. There is also no requirement that three or more GMC records for agroup/subgroup exist to predicate either a GRC or GMC record. GRCcriteria require only that the group/subgroup identified be of that size. Anagency may wish to express interest and/or caution only as to a singlemember of that group/subgroup, and not enter records as to all membersof that group/subgroup.

d. It is expected that record recipients will treat every Gang record subjectwith appropriate caution. As entry is based on violent conduct by thatidentified group.

C. Retention Period

1. A GMC record will remain active until it is cancelled by the entering agency oruntil the Date of Purge (DOP) is equal to the current date. When the DOP isreached, a $.P. administrative message will be sent to the originating agency.The maximum retention period for a GMC record is 5 years unless entered bya corrections agency. In such case, the 5-year maximum runs from the date

that the DOP Field is altered to show release of the record subject fromincarceration.

2. A GMC record with a GNG of UNLISTED GROUP will be retired 96 hoursafter entry. The originating agency will not be notified.


27/50



3. GMC records are retired when a GRC record is fully cancelled. Theoriginating agency is notified via a $.P. administrative message during thenext purge cycle.

4. It is noted that multiple agencies may have GMC records for a gang/subgroup

based on a single-interest GRC record for that gang/subgroup. Because allagency GMC records would be purged on cancellation of the GRC record, anagency wishing to reenter its GMC records would be required to enter a GRCrecord for that gang/subgroup. If an agency does not want its GMC recordsretired in the event a GRC is canceled; it should enter an interest for thatGRC record. This ensures the GRC record is not completely cancelled.

5. Data in the LIC, LIY, and LIT Fields in a GMC record or supplemental recordwill be purged one year after the license plate expires as indicated in the LIYField. If the expired license plate is the only searchable identifier in the GMCrecord, the entire record will be retired and the originating agency will not be

notified.

D. GMC Validation

1. GMC records will be validated according to the same schedule and in thesame manner as Wanted Person file records except that the 60-90 dayvalidation will not be requested. Essentially, all records will be validatedyearly for accuracy and completeness as to the descriptive informationcontained therein, and most importantly, as to the validity of continuing thedesignation of the record subject as a gang or terrorist organization member.If the ORI determines that the designation was inaccurate or that the record

subject is no longer an active member of the group/subgroup, the recordshould not be validated and should be canceled.


28/50



CHAPTER 18: Gang FileSECTION 11: GMC Inquiry


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. Inquiry Syntax

Header W;Message Key QGMOriginating Agency Identifier WA0340500NAME NAM/DOE, JOHN JDATE OF BIRTH DOB/19500101SEX SEX/MOTHER IDENTIFIERS SOC, OLN, ETCRelated Search Hits RSH/YExpanded Name Search ENS/YExpanded Date of Birth Search EBS/YEND OF TEXT (send)

B. Guidelines for Inquiries

1. On-line queries to the GMC are possible in two ways:

a. Automatic cross-search as part of the QW/QV transaction; or

b. Use of the Gang - only QGM transaction.

2. In either case, the query must include NAM and one of the following numericidentifiers: DOB, SOC, MNU, OLN, VIN, LIC, or OCA.

3. In addition, an inquiry without a NAM using LIC, VIN, and/or NIC number ispermitted. Please keep in mind that when doing an inquiry using an LIC, anyrecord containing that plate number will be returned in your response. Tonarrow the scope of the search, you should include a LIS.


29/50



4. When the inquiry contains a NAM and complete DOB as the only numericidentifier, the date of birth in the inquiry must match the date of birth in arecord plus or minus one year on the year of birth before a record will beretrieved. When the subject of the inquiry uses more than one DOB, the

persons name should be checked using each available birth date. NCIC willsearch for all matching records that contain the same DOB plus or minus oneyear on the year of birth and a surname that is a New York State Identificationand Intelligence System (NYSIIS) match to the surname in the inquiry.

5. When the inquiry contains a name and an alphanumeric identifier other thanDOB, i.e. the SOC, FBI, MNU, or OLN, a name search is not generated. Inthis situation, only the alphanumeric identifier is searched.

6. Because multiple records from several files are available when the QWtransaction is used, multiple records concerning one individual may appear in

any response. Additionally, because different agencies may enter Gang Filerecords about the same individual, multiple Gang File records are possible inany response.

C. Operational Inquiry

1. A QGM transaction searches only the Gang File GMC.

W;QGM.WA0340500.NAM/DOE, JOHN J.DOB/19501010.SEX/M.VIN/987654321AB987654(Send)

2. GMC Negative Response

NO NCIC VGTOF RECORD DOB/010150 NAM/DOE, JOHN J SEX/M

NO NCIC VGTOF RECORD VIN/ 987654321AB987654

a. For the automated cross-search through the QW/QV transaction, anegative search will not produce a negative Gang File response (whetheror not a positive or negative response from other files is generated).

3. GMC GMC Positive Response


WARNING - STANDING ALONE, NCIC VIOLENT GANG AND TERRORISTORGANIZATIONS FILE INFORMATION DOES NOT FURNISH GROUNDS FOR THESEARCH AND SEIZURE OF ANY INDIVIDUAL, VEHICLE OR DWELLING


30/50



MKE/VIOLENT GANG MEMBER - CAUTIONORI/WA0340500 NAM/DOE, JOHN J SEX/M RAC/W POB/MD DOB/19500101HGT/511 WGT/200 EYE/BRO HAI/BRO FBI/123456ASKN/FARSMT/SC R SHLD

FPC/X0PM14AA53DIPOCM07XX MNU/MD-614 SOC/123456789OLN/98765432 OLS/MD OLY/1995GNG/CRIPS-*WADC SGP/ROARING 50S*WADCECR/BD DOP/20000115 OCA/TEST123MIS/KNOWN TO CARRY TEC 9, TTO IS TEARDROPLIC/ABC123 LIS/WA LIY/2000LIT/PCVIN/987654321AB987654VYR/1986VMA/TOYT VMO/CST VST/2D VCO/SILORI IS ANYTOWN PD WA360 555-1212DOB/19550515AKA/BEBETOAKA/LEON, JOSEAKA/JONES, JOHNNIC/T123456789 DTE/19990914 1400 ESTNO NCIC VGTOF RECORD VIN/987654321AB987654

D. GMC Message Keys

Entry Modify Cancel

GMC EGGM MGGM XGGMSupplemental Data EGMN XGMN

E. GMC Record Fields and Edits


Header 19 Y A,N,S

Message Key MKE 4 Y A

Originating AgencyIdentifier

ORI 9 Y A,N

Name NAM 30 Y A, N,S

Sex SEX 1 Y A

Race RAC 1 Y A

Place of Birth POB 2 N A

Date of Birth DOB 8 C NDate of Emancipation DOE 8 Y* N

Height HGT 3 N N

Weight WGT 3 N N

Eye Color EYE 3 N A


31/50




Hair Color HAI 3 N A

FBI Number FBI 9 C A,N

Skin Tone SKN 3 N A

Scars, Marks, Tattoos,and Other Characteristics

SMT 10 N A,N,S

Fingerprint Classification FPC 20 N A,N

Miscellaneous Number MNU 15 N A,N,S

Social Security Number SOC 9 N N

Operators LicenseNumber

OLN 20 C A,N

Operators License State OLS 2 C A

Operators License Year

of Expiration

OLY 4 C A,N

Gang Name GNG 22 Y A,N,S

Subgroup Name SGP 35 Y A,N,S

Criteria for Entry ECR 2 Y A

Date of Purge DOP 8 N N

Originating Case AgencyNumber

OCA 20 C A,N

Miscellaneous MIS 121 N A,N,S

Notify Originating Agency NOA 1 N A

License Plate Number LIC 8 C A,NLicense Plate State LIS 2 C A

License Plate Year ofExpiration

LIY 4 C A,N

License Plate Type LIT 2 C A

Vehicle IdentificationNumber

VIN 20 C A,N

Vehicle Year VYR 4 C N

Vehicle Make VMA 24 C A

Vehicle Model VMO 3 C A,N

Vehicle Style VST 2 C A

Vehicle Color VCO 3 C A

Caution and MedicalConditions

CMC 2 NN

DNA Profile Indicator DNA 1 N ADNA Location DLO 250 N A, N, S


32/50



*Mandatory Blank

Required: Y Yes Data Type: A Alphabetic

N No N Numeric

C Conditional S SpecialCharacters

1. MKE (Message Key)

a. The MKE field must be a valid message key.

2. ORI (Originating Agency Identifier)

a. The ORI field must be a valid NCIC assigned ORI. The first twocharacters must be alphabetic.

3. NAM (Name)

a. The name may include alphabetics, numerics, a comma, hyphen(s), andspaces. The comma must follow the last name and there can be no morethan one space after the comma. The hyphen cannot be in the firstposition or directly precede the comma. Coding instructions can be foundin Personal Descriptors, NCIC 2000 Code Manual.

4. SEX (Sex)

a. The SEX field must be a valid NCIC assigned code as listed in PersonalDescriptors, NCIC 2000 Code Manual.

5. RAC (Race)

a. The RAC field must be a valid NCIC assigned code as listed in PersonalDescriptors, NCIC 2000 Code Manual

6. POB (Place of Birth)

a. The POB field must be a valid NCIC assigned code as listed in State and

Country Codes, NCIC 2000 Code Manual.

7. DOB (Date of Birth)

a. The DOB field must be eight numbers representing year, month, and dayin that order (YYYYMMDD). The numbers in the month positions cannotexceed 12. The numbers in the day positions cannot exceed the number


33/50



of days in the month indicated. The month and date cannot exceed thedate entered and cannot be ----0229 when the year is not a leap year. If aNAM is entered, a DOB must be entered or one other numerical identifier.

8. DOE (Date of Emancipation)

a. The DOE field must be blank.

9. HGT (Height)

a. The first character of the HGT field represents feet and the second andthird represents inches. It must be a minimum of 400 but not more than amaximum of 711.

10.WGT (Weight)

a. The WGT field must contain a minimum of 050 and maximum of 499.

11.EYE (Eye Color)

(1) The EYE field must be a valid NCIC assigned code as listed inPersonal Descriptors, NCIC 2000 Code Manual.

12.HAI (Hair Color)

a. The HAI field must be a valid NCIC assigned code as listed in PersonalDescriptors, NCIC 2000 Code Manual.

13.FBI (FBI Number)

a. The FBI field must contain one to nine characters. It may be up to sevennumeric or one to six numeric followed by an alphabetic character Athrough H; or one to six numerics followed by an alphabetic character Jthrough Z followed by one or two check digits; or one to six numericsfollowed by alphabetic characters followed by one check digit. If thenumber contains one alphabetic character (J-Z), the check digit will be 1 to11. If the number contains two alphabetic characters, the first alphabeticcannot be B, G, I, O, Q, S, U, Y, or Z.

b. The second alphabetic must be A, B, or C, and the check digit will be 0 to9. The alphabetic characters I and ) are always invalid.


34/50



14.SKN (Skin Tone)

a. The SKN field must be a valid NCIC assigned code as listed in PersonalDescriptors, NCIC 2000 Code Manual.

15.SMT (Scars, Marks, Tattoos, and Other Characteristics

a. The SMT field must be a valid NCIC assigned code as listed in PersonalDescriptors, NCIC 2000 Code Manual.

16.FPC (Fingerprint Classification)

a. The FPC field must be a valid NCIC assigned code as listed in PersonalDescriptors, NCIC 2000 Code Manual. If the first character of any fingeris numeric, the second character must also be numeric. Codes 00 and 50may not be used.

17.MNU (Miscellaneous Number)

a. The first two characters must be a valid NCIC assigned code as listed inPersonal Descriptors, NCIC 2000 Code Manual. The third charactermust be a hyphen. Entry of one zero only or a runoff of zeros is prohibitedin positions 4 through 15. An originating agency police or identificationnumber (prefix code OA) in MNU cannot be the only numeric identifier inthe record. If the MNU exceeds 15 characters, the first five charactersshould be entered in the MNU Field. The full MNU should be entered inthe MIS Field.

18.SOC (Social Security Number)

a. The SOC field must not be less than 001010001 or have a value of 8 or 9in the first position or have a value of 00 in the fourth and fifth position.Invalid and/or non-issue numbers are accepted but cause a SOC attentionmessage.

19.OLN (Operators License Number)

a. The OLN field must contain one zero only or a run of zeros only indicating

a license is unknown may not be used.

20.OLS (Operators License State)

a. The OLS field must be a valid NCIC assigned code as listed in State andcountry Codes, NCIC 2000 Code Manual.


35/50



21.OLY (Operators License Year of Expiration)

a. The OLY field must represent the year the license expires (YYYY) or thealphabetics NX to represent a non-expiring license.

22.GNG (Group Name)

a. The GNG field must be the GNG of an active GRC record.

23.SGP (Subgroup)

a. The SGP field must be the SGP name of an active GRC record.

24.ECR (Criteria for Entry)

a. The ECR field must have one of the following designations: A, AB, AC,

AD, AE, BC, BD, BE, BF, CD, CE, CF, DE, DF, or EF.

(1) Self-admitted group membership at time of arrest or incarceration.

(2) Identified as a group member by a reliable informant or individual.

(3) Corroborated identification as a group member by an informant orindividual of unknown reliability.

(4) Frequents a documented group's area, associated with known groupmembers, and/or affects group dress, hand signals, tattoos, or

symbols.

(5) Has been arrested with known group members for offenses consistentwith group activity.

(6) Self-admitted group membership (at any time other than arrest orincarceration).

25.DOP (Date of Purge)

a. There must be eight numbers representing year, month, and day in that

order (YYYYMMDD). The date must be greater than the current date butnot more than 5 years greater. If the DOP is equal to YYYYYYYY orXXXXXXXX, the originating agency must be a corrections agency. TheDOP is optional. If not entered, NCIC will set the DOP to the current dateplus five years.


36/50



b. Only an ORI ending in C (corrections) is permitted to enter XXXXXXXX onthe date of incarceration. This entry will stop the running of the system-created automatic purge date.

26.OCA (Originating Case Agency Number)

a. The OCA may contain alphabetics, numerics, and a hyphen. It must notcontain a single zero only, a run of zeros only, the word NONE, or the firstseven characters of the ORI Field.

27.MIS (Miscellaneous)

a. Vehicular data, date of births, social security numbers, and operatorslicense numbers should not be entered in the MIS Field. All additionalsearchable data should be entered as a supplemental record, as thisprocedure increases the chances of a hit on the record. Nicknames

(monikers) are to be entered in the MIS Field, not the AKA Field of theGMC record. Information in the MIS Field is not searchable.

28.NOA (Notify Originating Agency)

a. If an entering agency believes notification each time its record is hit willprovide investigative leads, regardless of whether the location of theproperty or person is known, enter Y in the NOA field. If this field is leftblank, it defaults to N for no.

29.LIC (License Plate Number)

a. The LIC field must not be characters UNK, UNKN, or UNKNOWN. If VMAis AERO, LIS is US, and LIT is PP or NP, the first character in the LICField must be the alphabetic N. If the license plate number exceeds eightcharacters, only the last eight should be entered in the LIC with the fullplate number shown in the MIS Field.

30.LIS (License Plate State)

a. The LIS field must be a valid NCIC assigned code as listed in State andCountry Data Codes, NCIC 2000 Code Manual.

31.LIY (License Plate Year of Expiration)

a. The LIY field must represent the highest year in which the license plate isvalid (YYYY). The value can be current year, current year minus one, orlater than current year; or the alphabetics, NX, to represent a non-expiringregistration.


37/50



32.LIT (License Plate Type)

a. Must be a valid NCIC assigned code as listed in Vehicular Data Codes,NCIC 2000 Code Manual.

33.VIN (Vehicle Identification Number)

a. Single zero only, run of zeros only, single alphabetic only, all alphabeticsonly, or spaces cannot be used. The Vehicle File chapter has additionaledits on the VIN Field. If there is a state assigned or nonconforming 17-character VIN, SVIN must be entered as the first characters of the MISField. If the VIN exceeds 20 characters, only the last 20 characters shouldbe entered in the VIN Field. The full VIN must then be shown in the MISField.

34.VYR (Vehicle Year)

a. The VYR field must represent the model year during which the vehiclewas manufactured (YYYY). Year cannot be more than one year beyondthe current model year. For entries of model year 1981 or later and whenthe VIN is 17 characters; the tenth position represents the vehicle year.

35.VMA (Vehicle Make)

a. Must be a valid NCIC assigned code as listed in the Vehicular DataCodes, NCIC 2000 Code Manual.

36.VMO (Vehicle Model)

a. Spaces cannot be skipped. Hyphens or symbols must be used. Moreinformation can be found in the Vehicular Data codes, NCIC 2000 CodeManual.

37.VST (Vehicle Style)

a. Must be a valid code listed in Vehicular Data Codes, NCIC 2000 CodeManual.

38.VCO (Vehicle Color)

a. Must be a valid NCIC assigned code as listed in Vehicular Data Codes,NCIC 2000 Code Manual. If two color codes are used, they must beseparated by a slash (/).


38/50



39.CMC (Caution and Medical Conditions)

a. The CMC field must be a valid NCIC assigned code as listed in thePersonal Descriptors Section of the NCIC Code Manual. If the cautionindicator is added to the entry message key (MKE), this field must contain

the reason for the caution.

40.DNA (DNA Profile Indicator)

a. The DNA field must contain a Y or N. It defaults to N. If an agency entersY, then the DLO field must be filled.

41.DLO (DNA Location)

a. The DLO field contains a 250 character free text field to explain thelocation of the DNA sample and contact information. If the DNA field is N

or defaulted to N, the DLO field must be left blank.


39/50



CHAPTER 18: Gang FileSECTION 12: GMC Entry


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. GMC Entry with Mask

F:EGGM(send)

MKE/____ ORI/ _________ NAM/______________________________SEX/_ RAC/_ POB/ __ DOB/ ________ DOE/ ________ HGT/ ___WGT/ ___ EYE/ ___ HAI/ ___ FBI/ _________ SKN/ ___ SMT/ __________FPC/ ____________________ MNU/ _______________ SOC/ _________OLN/ ____________________ OLS/ __ OLY/ ____GNG/______________________ SGP/___________________________________ECR/__ DOP/ ________ OCA/____________________MIS/ ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

______________________________________________________________________________________________________________________________________________________________________________________________________________________________NOA/ _ LIC/ __________ LIS/ __ LIY/ ____ LIT/ __VIN/ ____________________ VYR/ ____ VMA/ ________________________VMO/ ___ VST/ __ VCO/ _______ CMC/ __DNA/ _ DLO/ __________________________________________________________________________________________________________________________________________________________________________________________________________________

_____ REQUIRED FIELD

ENTER GANG MEMBER FORMAT

MUST HAVE ONE: DOB,FBI,MNU,SOC, OLN-OLS-OLY, LIC-LIS-LIY-LIT,or VIN-VYR-VMA-VST


40/50



1. Example of Entry

W;EGGM.WA0340500.DOE, JOHN J.M.W.MD 19500101..511.200.BRO.BRO..FAR.TAT R SHLD.XOPM14AA53DIPOCM07XX.TEST123.123456789.987654321AB987654.WA.2000.CRIPS*WADCROARING50S

*WADC.A.2002010194161242.ARMED WITH TEC 9, TATTOO ISTEARDROP.Y.WGS532. MD.1999.PC.ABC123.L38106924.1986.TOYT.CST.2D.SIL (Send)

2. Acknowledgement


NAM/DOE, JOHN J NIC/T123456789

3. Additional Guidelines for GMC Entry

a. The entering agency must account for all fields in the GMC record format.In the original entry, all available data called for in the record must beentered. Missing data obtained at a later time should be promptly addedthrough the use of a modify message.

b. All numerical identifiers except the ORI and MNU are to be enteredomitting spaces, hyphens, and symbols. A hyphen may be used in theOCA, and a hyphen is used to separate the first two alphabetics from thenumber itself in the MNU Field. If the MNU exceeds 15 characters, the

first 15 characters should be entered in the MNU Field. The full MNUshould be entered in the MIS Field.

c. A GMC record entered with GNG/UNLISTED GROUP will only be retainedfor 96 hours regardless of what the DOP is set to.

4. Additional Vehicular Data

a. Information may be entered in a Group Member record about vehiclessubject to the following criteria:

(1) The vehicle must have been observed to be in the possession of ordriven by a specific record subject, or some group member who wouldseparately meet the criteria for entry in the GMC.

(2) Vehicle information about a single, particular vehicle may be entered inmore than one GMC record by the same agency. Vehicle informationwhich is part of a GMC record will be searched by any Vehicle File


41/50



inquiry (QV, QW, RV, DW, QGM), assuming that either the LIC (andaccompanying fields) or the VIN is entered in the record.

(3) Entry with VYR, VMA, VMO, VST, and/or VCO, without either LIC orVIN is permitted. Though not searchable on-line without LIC or VIN,

this information will be returned as part of a response to a QW or QGMinquiry.

(4) *Please note: Since the Gang file is in NCIC only and routine inquirieson Washington license plates (V, QV, RV) are not forwarded to NCIC,an inquiry on a Washington license plate will not retrieve a Gang Filerecord with that plate included. A specific Gang File inquiry (QGM)with a Washington license plate will be forwarded to NCIC and retrieveany matching Gang File record.


42/50



CHAPTER 18: Gang FileSECTION 13: Modify Transactions


Special Order:




See Also:

CALEA:

I. DEFINITIONS

A. GMC Modify

1. Modification of a record is restricted to the agency that entered the record andis used to add, delete, or change data in the base record. Use of thismessage is mandatory by a C ORI (corrections agency) on release of arecord subject from incarceration if XXXXXXXX was originally entered in theDOP Field.

5. With respect to all data in the record except for name and vehicle-relatedinformation, deletion of data will cause the same data in the supplementalrecord to become part of the base record.

II. PROCEDURE

A. Syntax

Header W;Message Key MGGMOriginating Agency Identifier WA0340500NAME DOE, JOHN JNCIC NUMBER T123457896MODIFY FIELD DOB/19500531END OF TEXT (Send)

1. The modify transaction consists of the message key, ORI, two recordidentifiers, and the fields being modified. Permissible record identifiers areNAM and OCA, NIC and OCA, or NAM and NIC. The fields being modifiedmust be identified by their appropriate MFC.


43/50



B. GMC Modify Field Edits

Field Edits

MKEMust be a valid message key:MGGM Modify GMC Member

ORI Must be a valid ORI and match the ORI in the record beingmodified.

1st Record IdentifierThe first of two identifiers to identify the record to bemodified. Can be NAM or NIC.

2nd Record IdentifierThe second of two identifiers to identify the record to bemodified. Can be OCA or NIC.

Modified Field(s)The field(s) in the record to be modified. Each must beidentified by its MFC.

C. Examples of GMC Modify

W;MGGM.WA0340500.NAM/DOE, JOHN J. NIC/T123456789.MIS/.(Send)

W;MGM.WA0340500.NAM/DOE, JOHN J. NIC/T123456789.DOB/19500101.(Send)

D. Acknowledgment


MODIFY NAM/DOE, JOHN J.NIC/T123456789


44/50



CHAPTER 18: Gang FileSECTION 14: GMC locate Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. GMC Locate

1. There are no locate procedures for the Violent Gang and TerroristOrganization File.


45/50



CHAPTER 18: Gang FileSECTION 15: GMC Clear Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. GMC Clear

1. There are no clear procedures for the Gang File.


46/50



CHAPTER 18: Gang FileSECTION 16: GMC Cancel Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. GMC Cancel

1. Cancellation of a GMC record is restricted to the ORI that entered the record.A cancellation message is utilized when the entering agency determines thatthe record is invalid.

B. Syntax of GMC Cancel Transaction

Header W;Message Key XGGMOriginating Agency Identifier WA0340500NAME DOE, JOHN J

Date of Cancellation 19990612End of Text (Send)

1. The cancel transaction consists of the message key, ORI, two recordidentifiers, and the date of cancel. Permissible record identifiers are NAMand OCA, NIC and OCA, or NAM and NIC.


47/50



C. GMC Cancel Field Edits

Field EditsMKE The message key for all GMC cancels is XGGM.

ORIMust be a valid ORI and match the ORI in the record being

cancelled.1st Record Identifier

The first of two identifiers to identify the record to becancelled. Can be NAM or NIC.

2nd

Record IdentifierThe second of two identifiers to identify the record to becleared. Can be OCA or NIC.

Date of CancelRequired by NCIC. Must be a valid date in the formatYYYYMMDD. Must be the current date or the current dateminus one day.

1. Example of GMC Cancellation

W;XGM.WA0340500.NAM/DOE, JOHN J.NIC/ T123456789.20060326(Send)

a. This message contains the transaction code (W), cancellation messagekey (XGM), ORI, record name (NAM/DOE, JOHN J), NCIC number(NIC/T639123105), and date of cancellation (011595) as entered by theagency.

2. Acknowledgment


CANCEL NAM/DOE, JOHN J NIC/T123456789

D. Additional Guidelines for GMC Cancellation

1. All information about the record subject, including any supplementalinformation, is canceled when the XGM transaction is used.


48/50



CHAPTER 18: WACIC Violent Gang and Terrorist FileSECTION 17: GMC Supplemental Transactions


Special Order:




See Also:

CALEA:

I. PROCEDURE

A. GMC Supplemental Record

1. Only the agency that entered the original record may add additional identifiersto a record. The supplemental record entry transaction (EGMN) is availableto add identifiers to either Gang member records.

B. Syntax of GMC Supplemental Transaction

Header W;Message Key EGMNOriginating Agency Identifier WA0340500NAME DOE, JOHN J

NCIC Number T123456789Supplemental Fields AKA/SMITH, JOHN J

End of Text (Send)


49/50



C. Number of Additional Identifiers in GMC Supplemental Entry

MFC Field Edits

AKA Alias Names including nicknames 99

DOB Date of Birth 9.SOC Social Security Number 9MNU Miscellaneous Number 9.OLN Operator's License Number 9SMT Scars, Marks, and Tattoos 9LIC License Plate, State, Year of

Expiration, Type (entered as set)9

VIN Vehicle Identification Number,Year, Make, Model, Style, Color(entered as set; model and colornot required for entry, but shouldbe entered if known

9

CMC Cautions and Medical Conditions 9

IMN Image NIC (IMN)and Type (IMT)(entered as set)

12

D. Example of GMC Entry

W;EGMN.WA0340500.NAM/DOE, JOHN J.NIC/T123456789.AKA/SMITH, JOHNJ. JOHNSON, JOHN J.DOB/19501010.19490804.LIC/ABC123.DC.1995.PC.SMT/TAT R SHLD.(Send)

1. The above entry example contains: message key (EGMN); OriginatingAgency Identifier(WA0340500); two record identifiers (NAM/DOE, JOHN J

and NIC/T123456789);Two additional AKAs (AKA/SMITH, JOHN J andJOHNSON, JOHN J); two additional dates of birth (DOB/19500101 and19490804); one set of license plate data 9LIC/ABC123.DC.1995.PC); onescars, marks, and tattoos (SMT/TAT R SHLD).

E. Acknowledgment


SUPP NAM/DOE, JOHN J NIC/T123456789


50/50


F. Modification of GMC Supplemental Data

1. No one-step procedure is available to modify an alias or other identifier in aGMC supplemental record.

2. To modify the incorrect AKA or other identifiers, the record should becancelled and reentered.

G. Cancellation of GMC Supplemental Data

1. Example

W;XGMN.WA0340500.NAM/DOE, JOHN J NIC/T123456789AKA/SMITH, JOHN J. JOHNSON, JOHN J.DOB/19501010.19490804(Send)

H. Response

NCIC TIME; 1341 DATE: 110197 TO; ABCPDWA0340500CANCEL SUPP NAM/DOE, JOHN J NIC/T123456789AKA/SMITH, JOHN JAKA/JOHNSON, JOHN JDOB/19500101DOB/19490804

I. Additional Guidelines for GMC Supplemental Data Cancellation

1. AKAs; DOBs; SMTs; MNUs; and/or SOCs to be cancelled are to be set out inthe cancellation message in the same manner as in a supplemental recordentry. That is, more than one identifier of the same type may follow the MFCwithout repetition of the MFC. However, character for character, eachidentifier to be cancelled must be set out exactly as it appears in thesupplemental record on file.

2. Each set of operators license or license plate data (multiple data elementfields) must be preceded by OLN/ or LIC/, respectively, and all data elementsof the set must appear exactly as they appear in the supplemental record on

file. When cancelling vehicle data, only the vehicle identification number andmake are required following the VIN/ with periods accounting for theintervening VYR Field. For example:

VIN/1L69X6J023456..CHEV

chapter 18 gang

Documents

choose a style › pim_docs › docs › step_assets_pdf ›...

per chapter 18 - conclusion › ... › 418754 ›...

chapter 10 96 my holidays 10...chapter 10 my holidays 97...

colloidal lithography chapter 1 ye yu and gang...

multnomah county comprehensive gang...

classification chapter 18 review classification chapter 18...

chapter 18 chapter 18 the evolution of populations

the 2008 ngcrc 111h international gang specialist training...

chapter 18 chapter 18 chemistry of the environment

gang-gang -...

gang 2007 - hastings gang show

chapter 6 gang organization, offending, and victimization

gang saw gang - auburn university

gang-related violence and gang-related drug dealing - a...

gang gang 9844 2749 - warrandytehigh.vic.edu.au

c2000 gang programmer (c2000-gang) (rev. c) · c2000 gang...

gang-gang august 2007

gang tidur, mhcu, gang makan fix

depl evolution series def - scameonline [en] - … or/gold...

che1102, chapter 18 learn, 1 chapter 18 thermodynamics