Section 27: National Insurance Crime Bureau and National Vehicle Services and Locator

From Nlets Wiki
Jump to: navigation, search

Contents

National Insurance Crime Bureau and National Vehicle Services

This section describes how agencies may utilize resources for Insurance Crime. The Query and Response message formats (NIQ/NIR and NAQ/NAR) are included following a description of the NICB and NVS services.

Background of NICB

The National Insurance Crime Bureau (NICB), formerly NATB, is a crime prevention organization assisting law enforcement in the prevention, detection, and prosecution of the financial crimes of theft, fraud, and arson relating to personal property.

NICB maintains Divisional Offices in Atlanta, Chicago, Dallas, New York City and Los Angeles. Branch offices are located in Boston, Detroit and Houston. Each office can be reached directly via Nlets. The Eastern and Western Division Offices are open 24 hours a day, 7 days a week for urgent inquiries.

NICB resources include a staff of strategically located special agents available to assist law enforcement in matters related to theft, fraud, and arson.

  • Each special agent is always on call to provide assistance to law enforcement in the identification of vehicles under investigation.
  • Special agents are highly qualified investigators and experts in identifying vehicles on which identifying numbers have been removed, changed, altered, or obliterated.
  • Special agents participate in training programs for law enforcement officers charged with the responsibility of theft, fraud, and arson investigations.

NICB publishes manuals and software for assisting law enforcement in the investigation of the financial crimes of theft, fraud, and arson.

VINASSIST is a personal computer based software package that assists VIN users in detecting and correcting VIN errors. Once a VIN has been corrected with VINASSIST, checking NICB's assembly and shipping records can verify it for accuracy. VINASSIST is available free of charge via directed requests over Nlets to NICB's Information Systems Division.

NCIB manuals include the following:

Manual Description
Passenger Vehicle Identification Manual

Furnishes identification techniques for motor
vehicles, engines, and transmissions, in
addition to a brief summary of vehicle and
marine laws and regulations.

Commercial Vehicle Identification
Manual

Covers truck tractors, light-duty trucks, diesel
engines, commercial trailer, recreational
vehicles, farm, construction, and off-road
equipment.

VIN Location Pocket Guide A quick reference to be carried by field
personnel.
NICB Annual Report Monitors trends in vehicle theft and fraud.

Each publication is available free of charge to law enforcement agencies. For more information direct requests via Nlets to your local NICB region Office or contact:

Dan Abbott
National Insurance Crime Bureau
Phone: (708) 237-4410
Fax: (708) 430-2446
E-mail: dabbott@nicb.org
ORI: ILNATBC00

NICB maintains a rapidly expanding national and international index of more than 250 million records related to vehicles including manufacturer's shipping and assembly, vehicles imported and exported, thefts, impounds, salvage, auction, pre-inspection, vehicle claim, rental, theft, theft (recovery) and NCIC/CPIC cancels.

To track a motor vehicle's complete life cycle from birth to death, the database is designed to include vehicle liability, physical damage, and related homeowner claims. NICB files include data on passenger vehicles, multipurpose vehicles, trucks, trailers, motorcycles, snowmobiles, construction and farm equipment, boats, and uniquely identifiable parts.

Background of NVS

NVS is an Illinois not-for-profit 501 (c) (4) tax exempt corporation that is the only worldwide organization providing unique vehicle related theft/fraud and vehicle related data and technological assistance free to the law enforcement community and for a reasonable fee to vehicle finance, insurance and rental car companies.

NVS aspires is to be widely recognized as the world leader in providing unique vehicle theft and fraud solutions to the law enforcement community, vehicle finance, insurance and rental car industries and other vehicle related organizations.

We also offer vehicle impound, lien, online auction (E-Bay), OCRA (Mexican Stolens), Private LPR and Junk and Salvage data at no costs to LEAs.

NVS Main contact is Kevin Spiller, COO, kevinsspiller@yahoo.com 708-642-2300

NVS contact information:
email: n.v.s@att.net
Phone: 708-429-0123
Web Address: www.nvsliens.org

NVS Recoveri Microdot Data

Recoveri.net is a Global Organization that provides Vehicle Component Parts Marking to Vehicle Manufacturers and After Market Vehicle Dealers Worldwide. NVS is the Central Repository for Microdot Data for Law Enforcement access Globally.

Micro Dots are Microscopic Unique Data Codes that are crossed reference to a Vehicle’s VIN to which the Dots are applied. Subsequently, if a Micro Dot Unique Code is found and queried (NAQ) the Vehicle VIN will be returned with other Vehicle Identifiers. If a VIN is queried (NAQ) and a Micro Dot Code was applied to the Vehicle the Micro Code will be returned with other Identifiers.

If additional assistance is required, Recoveri may be contacted via email for additional assistance at: philip@recoveri.net or rphillips@recoveri.ca.

Data Format to be supplied to NVS, NFPC

Header: MicrodotNumber, VIN, EngineNumber, Make, Model, Colour, Model, Year

Data: USCORDV001009878, AAVZZZ6RZHU062610, CJZD57913, VOLKSWAGEN, POLO GP 1.2 CL MAN 66K, REFLEX SILVER, 2017

Data Fields (CamelCase)
"MicrodotNumber" Alpha Numeric Max 17 Characters, No Minimum
"VIN" Alpha Numeric Max 17 Characters, No Minimum
"EngineNumber" Alpha Numeric Max 17 Characters, No Minimum
"Make" Alpha Max 20 Characters, No Min
"Model" Alpha Numeric Max 50 Characters, No Minimum
"Colour" Alpha Max 20 Characters, No Minimum
"ModelYear" Numeric Max 4

Microdot Decoding: Each set of Microdots has a unique PIN number

Country, State Example
Example Number: USCORDV00252198
Country Code US (United States)
State Code CO (Colorado)
Microdot Manufacturer RD (Recoveri Dot)
Asset Class V (Vehicle)
Unique Number 00252198


Country Example
Example Number ZARDV00252198
Country Code ZA (South Africa)
Microdot Manufacturer RD (Recoveri Dot)
Asset Class V (Vehicle)
Unique Number 00252198

File Sample

Format A comma-separated values (CSV) file stores tabular data (numbers and text) in plain text. Each line of the file is a data record. Each record consists of one or more fields, separated by commas. The use of the comma as a field separator is the source of the name for this file format.

Locator Technologies LLC

Locator Technologies LLC offers a database identifying the legal owner of more than 36 million vehicles. Participants in Locator's lien database include most major captive auto finance companies, including Toyota, Ford, and many others, and most major banks, including Chase, Wells Fargo, and many others. Altogether, more than 3,000 lenders and many insurers participate in Locator's lien database. Locator does not charge law enforcement for access to the database. Query is by a NAQ VIN request on the Nlets system. A query returns the name and contact information of the legal owner of the vehicle associated with the input VIN.

In addition, Locator operates the eimpound.com website. Over a thousand tow yards, municipalities, and other operators of impound lots enter the VINs of vehicles stored on their lots into the eimpound.com website in order to identify the legal owner of those vehicles. Locator makes the eimpound.com database of impounds available for search at no charge to law enforcement. Query is by VIN on the Nlets system. A query returns the name and contact information of the impound lot holding the vehicle associated with the input VIN.

Locator Technologies, via its’ eImpound application, will provide a NAR and NIR response message that will include impound and seizure data from throughout Mexico. The new Mexico impound and seizure data creates a true North American impound database for all approved LEAs to use, via Nlets.

NICB and NCIC Stolen Vehicle Entries

NICB has a mirror image of NCIC's stolen vehicle file. Every stolen vehicle entered on NCIC will be passed to NICB by NCIC. NICB will enter this record on their file and interrogate Impound (last 60 days entries), Export, Auction and International Index Files.

NICB Query / Response

NICB provides automated access to twelve different files:

Impound file Pre-Inspection File
Export File Vehicle Claim File
Manufacturer's Shipping File Rental File
Salvage File Theft File
International Index File Theft (recovery) File
Auction File NCIC/CPIC Canceled File

These files may be accessed via two distinct types of inquiries.

  • One will access only the Impound and Export files (NIQ). (Note: Export files returned are historic files prior to August 2016).
  • The other will access the other ten files listed above (NAQ).

Impound/Export File Query (NIQ)

This transaction interrogates the NICB Impound and Export Files only.

Impound responses indicate that the vehicle has been impounded, but does not tell whether or not the vehicle was claimed or remains on the lot.

Section27-NIQ1.jpg

An Export File response indicates that a vehicle has been exported out of the country, but it does not indicate if the vehicle has been returned to the country.

Section27-NIQ2.jpg

Impound / Export File Query Requirements (NIQ)

  • Destination ORI for NICB queries is "NA".
  • Impound records will only be returned on an "NIQ" if the date of impound is less than 60 days from the date of the inquiry.
  • Access to these files is for investigative purposes only.
  • Users should not program their computers to automatically send inquiries to these files whenever an inquiry is sent to either the NCIC stolen vehicle file or state vehicle registration files.
  • If no information is found on any of the twelve NICB files the following message will be displayed: NO RECORD NICB.

Data Codes / Field Requirements

This transaction interrogates the NICB Impound and Export files only. Impound records will only be returned on an "NIQ" if the date of impound is less than 60 days from the date of the inquiry.

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleID>
VIN/ Max.
20
Alphanumeric VIN for vehicle (no period after
last field in Native inquiry)

All Files Inquiry (NAQ)

This transaction interrogates all available NICB, NVS and OCRA (Mexican Stolens) files with one exception:

  • If only a partial VIN is available the user may submit the last 8 characters of the VIN. In order to identify the VIN as partial to NICB the user MUST preface the partial VIN by the word "PARTIAL".
  • For example a partial VIN with the year 1990 would look like this: VIN/PARTIAL24657490. Note that there is no space or separator between the word "PARTIAL" and the eight character VIN.
  • When a partial VIN search is requested only the Manufacturers Shipping File will be searched.

The possible queries/responses (NAQ/NAR)are described below. If NICB has no information for a particular field, the field header will not appear on the response.

Manufacturer's Shipping File Query / Response (NAQ)

Shipping responses indicate to whom, when, and where a vehicle has been shipped.

Section27-NAQ1.jpg
Salvage File Query / Response (NAQ/NAR)

Salvage responses indicate that the vehicle has been damaged (cause of loss) and what the cash value was of the vehicle prior to the loss, the received value, and the appraised value.

Section27-NAQ2.jpg
International Index Salvage Query / Response (NAQ/NAR)

NICB maintains records of stolen or salvaged vehicles for Canada, Germany, France and Sweden. NAQ queries will check this index and return any hits. Users should contact NICB if a hit is obtained on these records.

Section27-NAQ3.jpg
Auction File Query / Response (NAQ/NAR)

Auction responses include those records that are processed through auction houses prior to the sale and sent to NICB.

Section27-NAQ4.jpg
Pre-Inspection File Query / Response (NAQ/NAR)

Pre-inspection responses occur when vehicles are run through an authorized inspection center in several states and pictures are taken of the vehicle including the VIN plate. The photos are then sent to a specific company for examination and then run through NICB's VINASSIST program. If they do not pass this edit, these records are put into the NICB system.

Section27-NAQ5.jpg
Vehicle Claims File Query / Response (NAQ/NAR)

Vehicle claim responses contain information on physical damage to a vehicle. After the insurance adjuster or appraiser files his report, he sends a copy to a vendor used specifically for physical damage estimates. They in turn process the claim and forward it to NICB. By doing this, it will raise a red flag to the appraiser if a claim has been duplicated.

Section27-NAQ6.jpg
Rental File Query / Response (NAQ/NAR)

Several rental car agencies provide and maintain a complete inventory on the NICB system. When an impound or export is processed, it is automatically checked against this file. To qualify for entry on the NICB file, the vehicle must be added to a fleet, missing, never returned, located or taken out of a fleet.

Section27-NAQ7.jpg
NICB Theft Record / Recovery Query / Response (NAQ/NAR)

NICB receives approximately 400,000 theft records from its member companies. While NCIC and CPIC active thefts are not available to law enforcement through NICB, member company thefts, both active and inactive, are displayed when querying NICB by VIN. This allows an agency to deal directly with the member company when appropriate.

The recovery information mirrors the theft record except that vehicle recovery information is also displayed.

Section27-NAQ8.jpg
NICB Lien record Query / Response (NAQ/NAR)

The NICB Lien record indicates that a finance company that is an Associate Member of NICB has an interest in a VIN. The Lien record will return a match containing the name of the lienholder that has an active lien on record with NICB.

  • LIEN RECORD INDICATOR*

LIEN HOLDER/ALLY FINANCIAL, INC

FOR ANY QUESTIONS PLEASE CONTACT NICB 847-544-7002
Section27-NAQ009.jpg
NICB Key Code / Response (NAQ/NAR)

The NICB Key Code record will return a match in which a key code and/or an immobilizer reset has been requested of the vehicle manufacturer, by a registered locksmith (Non-OEM) or dealer service center (OEM). The NICB Key Code Record match will contain the date of occurrence, OEM type (OEM or Non-OEM), and a transaction type. The 3 transaction types are: Key Code Request, Immobilizer Reset Request, or Key Code and Immobilizer Reset Request. Non-OEM transactions will also contain a Transaction ID number and a Locksmith ID number.

  • VEHICLE KEY CODE REQUEST*

DATE/ 01/04/2018 NON-OEM/KEY CODE AND IMMOBILIZER RESET REQUEST
TRANSID/GM-18003003707 LSID/43Y22RNZ

FOR ANY QUESTIONS PLEASE CONTACT NICB 847-544-7002
Section27-NAQ010.jpg
NCIC / CPIC Canceled Record Query / Response (NAQ/NAR)

NICB maintains NCIC canceled records online dating back to 1972. Rather than asking for an off-line search of NCIC records, a query to NICB provides an immediate response.

Canadian Police Information Centre (CPIC) canceled records date back to 1996. Both NCIC and CPIC have authorized the release of canceled records by NICB.

Help File

NICB maintains a HELP file. It may be accessed by sending an "AM" message to NAADMHELP.

More information on help files can be located in Help File Transactions.

Query Field Requirements

The following are used to inquire upon the vehicle identification number.

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<n2:NLETSInquiryData>
  <nc:Vehicle>
    <nc:VehicleIdentification>
      <nc:IdentificationID>
VIN/ Max.
20
Alphanumeric

VIN for vehicle identification
number (no period after last
field in Native query).

Responses to NICB Queries

Since NICB will be interrogating ten different files, responses will vary based on the hits that were made.

Status Fields

Some manufacturers provide NICB with the status of vehicles which have special circumstances pertaining to them. NICB then places a status condition into the status field. NICB may or may not have additional information regarding a status condition. Therefore, if a vehicle has a status condition, NICB should be contacted. Below is a list of status conditions and their definitions:

CONDITION DEFINITION
UNDEFINED The situation about the vehicle or VIN plate is not clearly
defined.
UNUSED The VIN plate and its embossed or stamped number will not be
installed or assigned to a vehicle.
STOLEN FROM LOT The vehicle was stolen from a factory or dealer lot.
DESTROYED The vehicle has been completely destroyed.
SCRAPPED The vehicle is unusable.
INCORRECT The VIN number found on the vehicle is incorrect. This number
does not conform to the Federal Motor Vehicle Standard.
STAMPING ERROR

Hidden numbers found on the vehicle, i.e., engine, transmission
and/or chassis numbers are not correct. This situation relates to
domestic built vehicles which denote a VIN derivative stamped,
embossed, or labeled on component parts.

STOLEN PLATE Manufacturer advises that only the VIN plate was stolen.
FLOOD DAMAGED The vehicle has had water damage and is not to be sold.
UNSCRAPPED The vehicle previously reported as a scrapped vehicle has been
repaired and is being sold.
FIRE DAMAGED The vehicle is reported as having fire damage and is not to be
sold.
REPLACEMENT

Replacement VIN plate - The vehicle's original VIN plate was
damaged or is missing and a replacement plate was issued by
the manufacturer.
Replacement Parts - The vehicle's component part has been
replaced and the part has a new number.

DONATED VEHICLE The vehicle was donated and removed from commerce.
TEST VEHICLE The vehicle is used for testing purposes and is not to be sold.
DATE The date in which the vehicle was shipped (ccyy-mm-dd).
DEALER NAME The name of the dealership that the vehicle was shipped to.
DEALER CODE The dealer code supplied by the dealer.
DEALER CITY, STATE The city and state where the dealer is located.
PHONE The phone number for the dealer.

If NICB has no information for a particular field, the field header will not appear on the response.

Salvage File Response

Salvage responses indicate that the vehicle has been damaged (cause of loss) and what the cash value is of the vehicle prior to the loss, the received value and the appraised value.

Explanation of Fields:

Legacy Code Translation
VYR/ The last two digits of the model year of the vehicle.
VMA/ The vehicle make as encoded in NCIC supplied tables.
DATE OF SALVAGE/ Date of salvage (ccyy-mm-dd)
CAUSE OF CLAIM/LOSS/ Cause of claim or loss.
INSURANCE COMPANY/ Name of insurance company.
INSURANCE COMPANY ADDRESS/ City and state where insurance company is
located.
INSURANCE COMPANY PHONE/ Phone number of insurance company.
CLAIM NUMBER/ Claim number of insurance company.
ACTUAL CASH VALUE/ Actual cash value prior to loss.
RECEIVED VALUE/ Dollar amount insured received for loss.
APPRAISED VALUE/ Appraised value at the time of loss.

Impound File Response

Impound records will only be returned on an "NIQ" if the date of impound is less than 60 days from the date of the inquiry.

Impound responses indicate that the vehicle has been impounded, but does not tell whether or not the vehicle was claimed or remains in the lot.

Explanation of Fields:

Entry Translation
ORI OF IMPOUNDING AGENCY/ The nine digit identifier for the place of recovery or
impound.
CASE NUMBER/ Case number assigned by the law enforcement agency
that holds the theft report.
DATE OF IMPOUND/ Date of recovery/impound (ccyy-mm-dd).
POUND/ Name of impounding lot.
VMA/ The vehicle make as encoded in NCIC supplied tables.
VMO/ The vehicle model of impounded vehicle.
VYR/ Last two or four digits of the model year of the vehicle.
VST/ The vehicle type as encoded in NICB tables.
LIC/ License number of impounded vehicle.
LIS/ The state in which the vehicle is licensed.
LIY/ The license year.
LIT/ The type of license issued.
MISC/ Miscellaneous information.
POUND INV #/ Invoice number assigned by the impounding agency.
POUND PHONE/ The phone number of the impounding lot.
NY DERELICT/ Indicates whether or not the vehicle was impounded
under the New York Derelict program.

Export File Response

Export responses indicate that the vehicle has been exported out of the country, but does not indicate if the vehicle has been returned to the country.

Explanation of Fields:

Entry Translation
VYR/ Four digits of the model year of the vehicle
VMA/ The vehicle make as encoded in NCIC supplied tables
DATE OF EXPORT/ Date of export (ccyy-mm-dd)
DESTINATION/ Destination of export

International Index Response

The NICB maintains records of stolen or salvaged vehicles for Canada, Germany, France and Sweden. NAQ inquiries will also check this index and return any hits.

Entry Translation
VYR/ Last two or four digits of the model year of the vehicle
VMA/ The vehicle make as encoded in NCIC supplied tables
DATE OF EXPORT/ Date of export (ccyy-mm-dd)
DATE OF SALVAGE/ ccyy-mm-dd
FILNR/ Unique file number of record owner.
OWNER/ Owner of record.

Users should contact NICB if a hit is obtained on these records.

Auction File Response

Auction response includes those records that are processed through auction houses prior to the sale and sent to NICB.

Entry Translation
AUCTION COMP/ The name of the Auction Company in possession of the
vehicle
AUCTION REFERENCE/ The number assigned to the vehicle by the Auction Company
DATE OF AUCTION/ The day the vehicle is scheduled for auction
(ccyy-mm-dd)
VYR/ The last two or four-digit model year of the vehicle
VMA/ The vehicle make as encoded in NCIC supplied tables
VMO/ The vehicle model as encoded in the NCIC tables
ODOMETER/ Odometer reading as reported by the Auction Company

If NICB has no information for a particular field, the field header will not appear on the response.

Pre-Inspection File Response

Pre-Inspection responses occur when vehicles are run through an authorized inspection center in several states and pictures are taken of the vehicle including the VIN plate. The photos are then sent to a specific company for examination and then run through the NICB's VINASSIST program. If they do not pass this edit, these records are put into the NICB system.

Explanation of Fields:

Entry Translation
PRE-INSP COMP/ The name of the company responsible for the pre-inspection.
INSP DATE/ The date of the pre-inspection (ccyy-mm-dd)
INSP REPT #/ Inspection company file #
ODOMETER/ Odometer reading at time of inspection

Vehicle Claims File Response

Vehicle Claim responses contain information on physical damage to a vehicle. After the insurance adjuster or appraiser files his report, he sends a copy to a vendor used specifically for physical damage estimates. They in turn process the claim and forward it to NICB. By doing this, it will raise a red flag to the appraiser if a claim has been duplicated.

Explanation of field entries:

Entry Translation
MEMBER COMPANY/ The name of the company that reported the claim.
CLAIM NUMBER/ The number assigned by the insurance company.
INS PHONE/ The telephone number of the filing insurance company
office.
IMPACT POINT/ The initial impact point of the vehicle according to the
filed claim.
MILEAGE/ The mileage at the time of the accident.

Rental File Response

Several rental car agencies provide and maintain a complete inventory on the NICB system. When an impound or export is processed, it is automatically checked against this file. To qualify for entry on the NICB file the vehicle must be:

  • added to fleet
  • missing
  • never returned
  • located
  • taken out of fleet

Explanation of field entries:

Legacy Code Translation
RENTAL COMP/ The name of the rental company
RENTAL REFERENCE #/ The rental company's file #
ACTIVITY DATE/ The date last action was taken on vehicle (ccyy-mm-dd)
ACTIVITY REASON/ The reason the vehicle is on file.
NAME/ The name of the customer that rented the vehicle
ADDR/ The address of the customer
VYR/ Vehicle year (4 characters)
VMA/ The vehicle make as encoded in NCIC supplied tables
VST/ The vehicle style
ODOMETER/ The odometer reading at time of activity.

NICB Theft Response

NICB receives approximately 400,000 theft records from its member companies. While NCIC and CPIC active thefts are not available to law enforcement through NICB, member company thefts, both active and inactive, are displayed when querying NICB by VIN. This allows your agency to deal directly with the Member Company when appropriate.

NICB Theft / Recovery Response

Explanation of Fields:

Legacy Code Translation
CONDITION OF RECOVERY/ Condition of vehicle at time of recovery
RECOVERING ORI/ The 9 digit identifier of the recovering agency.
REPORTING ORI/ The 9 digit identifier of the reporting agency.

NICB Canceled Records

NICB maintains NCIC canceled records online dating back to 1972. Rather than asking for an off-line search of NCIC records, a query to NICB provides an immediate response. Canadian Police Information Centre (CPIC) canceled records date back to 1996. Both NCIC and CPIC have authorized the release of canceled records by NICB.

NICB Impound Program Adds, Cancels and Modifies

States may enter impound records into the NICB Impound file via Nlets using the fixed format below (NEI).

At NICB, in addition to being added to their Impound file, the VIN will also be compared to the NICB theft file. If a matching record is found, the hit is forwarded to the proper NICB division for processing. The entering agency will be contacted.

All new thefts are also checked against the Impound file when entered. The impound records will be maintained and returned by NICB for a period of 60 days from the date received.

There may be occasions where the VIN does not pass the NICB edits. In these cases quality control at NICB will review these and attempt to correct them. They will notify the sender of any corrections to the VIN. Moreover, if they are not able to correct them the entering agency will be notified.

States also have the capability to cancel or modify their existing record.

  • The modify transaction is normally used if a mistake was made in the entry process.
  • The cancel transaction is used when the agency wishes to remove the record from the impound file.

Formats for these messages, along with NICB acknowledgment messages may be found below.

Add Impound Record

This transaction adds a record to the NICB impound file.

When the impound record is successfully entered you will receive an acknowledgment message from NICB.

If an error is made NICB will return an error message and the complete text of the entry.

If there is a duplicate record on file you will receive a message from NICB noting the duplicate.

The required fields are described below. The optional entries follow the required entries.

XML Tag: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleID>
VIN/ Max.
20
Alphanumeric VIN for vehicle.
<j:OrganizationORIID>
ORI/ 9 Alphanumeric

ORI of
impounding
agency.

<n:CaseID>
OCA/ 20 Alphanumeric

Case # (no
special
characters).

<n:ImpoundDate>
DOI/ 8 ccyy-mm-dd Date vehicle was
impounded.
<j:ContactOrganzationName>
PND/ 24 See NCIC Manual Name of Pound
holding vehicle.
Optional Entries
<j:VehicleMakeCode>
VMA/ 2-4 See NCIC Manual Vehicle Make
<j:VehicleModelCode>
VMO/ 4 See NCIC Manual Vehicle Model
<j:VehicleModelYearDate>
VYR/ 4 ccyy Vehicle Year
<j:VehicleStyleCode>
VST/ 2 See NCIC Manual Vehicle Style
<j:VehicleLicensePlateID>
LIC/ 1-10 See NCIC Manual License #
<j:IDIssuingAuthorityText
LIS/ 2 See NCIC Manual License State
<j:IDExpirationDate
LIY/ 4 See NCIC Manual License Year
<j:VehicleRegistrationPlateTypeCode>
LIT/ 2 See NCIC Manual License Type
<n:Miscellaneous>
MSC/ 42 Free format

Free format
miscellaneous
field

<n:PoundInventoryID>
INV/ 12 Alphanumeric Pounds
Inventory #
<j:ContactTelephoneNumber>
PHO/ 10 Numeric Phone # of
Pound
<n:NewYorkDerelict>
DER/ 1 Y

Fixed field of "Y"
if a New York
Derelict.
(Note: Last field
in Legacy message
must not be
followed by a
period.)

Modify Impound Record

To modify a field(s) in an existing impound record the user must include the NICB file number and the impound ORI on the record. If either of these don't match, the update will be rejected.

  • To add a field, place the new data in the field after the prefix identifier.
  • To delete a field place an asterisk after the field prefix.

When the impound record is successfully modified you will receive an acknowledgment message from NICB with a unique message key. Below is the format for the Modify Impound Record transaction.

The unique NICB impound record number ("FIL") and the impounding agency ORI ("ORI") fields are required and may not be updated in any way.

XML Tag: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:PropertyFederalID>
FIL/ 11 See NCIC manual

Unique NICB
impound record
number

<j:OrganizationORIID>
ORI/ 9 Alpha/numeric ORI of impounding
agency

These data fields are required but may be modified:

XML Tag: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<n:CaseID>
OCA/ 20 See NCIC Manual. Case # (no special
characters).
<n:ImpoundDate>
DOI/ 8 ccyy-mm-dd Date vehicle was
impounded.
<j:ContactOrganzationName>
PND/ 24 See NCIC Manual. Name of Pound
holding vehicle

These fields may be modified, added or deleted:

XML Tag: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleMakeCode>
VMA/ 2-4 See NCIC Manual. Vehicle Make
<j:VehicleModelCode>
VMO/ 3 See NCIC Manual. Vehicle Model
<j:VehicleModelYearDate>
VYR/ 4 See NCIC Manual. Vehicle Year
<j:VehicleStyleCode>
VST/ 2 See NCIC Manual. Vehicle Style
<j:VehicleLicensePlateID>
<j:ID>
LIC/ 1-10 Alphanumeric License #
<j:IDIssuingAuthorityText>
LIS/ 2 See NCIC Manual. License State
<j:IDExpirationDate>
LIY/ 4 See NCIC Manual. License Year
<j:VehicleRegistrationPlateTypeCode>
LIT/ 2 See NCIC Manual. License Type
<n:Miscellaneous>
MSC/ 42 Free text Free format
miscellaneous field
<n:PoundInventoryID>
INV/ 12 See NCIC Manual. Pounds Inventory #
<j:ContactTelephoneNumber>
PHO/ 10 Numeric Phone # of Pound
<n:NewYorkDerelict>
DER/ 1 Y

Fixed field of "Y" if
a New York Derelict
(Note: last field
must not be
followed by a
period)

Cancel Impound Record

This transaction will cancel an impound record on the NICB Impound file.

When the impound record has been successfully canceled you will receive an acknowledgment message from NICB with a unique message key.

IMPOUND RECORD CANCELED

Below is the format for the cancel impound transaction.

XML Tag: Legacy
Entry:
Field
Size:
Data
Requirements:
Translation:
<j:VehicleID>
VIN/ Max.
20
Alphanumeric VIN for vehicle
<j:PropertyFederalID>
FIL/ 11 Numeric

NICB file number
assigned to each
impound record.

Top

GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

National Insurance Crime Bureau, National Vehicle Services and Locator NIEM Specifications

This section provides Native format specifications and examples for Nlets user access to the Commercial Vehicle Information System (CVIS).

This section describes how agencies may utilize the resources of the National Insurance Crime Bureau and National Vehicle Services. All NICB, NVS and Locator queries should be sent to the destination code NA. Nlets will forward all transactions to NICB, NVS and Locator.

NICB provides automated access to twelve different files:

Impound file Pre-Inspection File
Export File Vehicle Claim File
Manufacturer's Shipping File Rental File
Salvage File Theft File
International Index File Theft (recovery) File
Auction File NCIC/CPIC Canceled File

NVS provides access to lien holder and auction data.

Nlets now provides information on active stolen vehicles in Mexico obtained from the Mexican office for insured risks known as OCRA, short for Oficina Coordinadora de Riesgos Asegurados S.C. Nlets users will be able to query this information by VIN through an SVQ query, and when available, this data will also be returned in NAR responses. A hit will return the stolen status of the vehicle and contact information for an OCRA representative who can verify the stolen status and provide additional relevant information.

Many vehicles are stolen from the US and taken to Mexico. Sometimes the reverse happens. In fact, hundreds of vehicles stolen in Mexico end up in the US every year. This new data file will enable US law enforcement officers to identify vehicles stolen in Mexico that have entered the United States. Some of these vehicles end up being sold to unsuspecting innocent purchasers. Others are connected to ongoing organized crime activities occurring on both sides of the border.

OCRA only has information on vehicles insured in Mexico. An uninsured vehicle not in the OCRA database may still be an active stolen vehicle in Mexico

These files may be accessed via two distinct types of inquiries. One will access only the Impound and Export files (NIQ). The other will access all files listed above (NAQ).

Access to these files is for investigative purposes only.

Users should not program their computers to automatically send inquiries to these files whenever an inquiry is sent to either the NCIC stolen vehicle file or state vehicle registration files.

NICB has a mirror image of NCIC's stolen vehicle file. Every stolen vehicle entered on NCIC will be passed to NICB by NCIC. NICB will enter this record on their file and interrogate Impound (last 60 days entries), Export, Auction and International Index Files.

All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.

Element Dictionary

Transaction types detailed below include: Query for Impound/Export Information (NIQ), Query of All Files (NAQ), Entry to Impound File (NEI), Modification to Impound File (NUI), Cancellation of Impound File (NCI), Response to Impound/Export Query (NIR) and Response from All Files (NAR).

Query Formats

Query for Impound/Export Information (NIQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried.

Query of all files (NAQ)

n2:NLETSInquiryData
This element will contain all elements specific to this transaction.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried. If only a partial VIN is available the user may submit the last 8
      characters of The VIN. In order to identify the VIN as partial to NICB the user MUSTpreface the partial VIN by the
      word "PARTIAL". For example a partial VIN with the year 1990 would look like this:
      <nc:VehicleIdentification><nc:IdentificationID>PARTIAL24657468</nc:IdentificationID></nc:VehicleIdentification>.
      Note that there is no space or Separator between the word "PARTIAL" and the six character VIN. When a partial
      VIN search is requested only the Manufacturers Shipping File will be searched.

Entry Formats

Entry to Impound File (NEI)

n2:NLETSUpdateData

  n2:LawEnforcementAgency

    j:OrganizationAugmentation
    Additional information about an organization.

      j:OrganizationORIIdentification
      A unique identifier assigned to a justice-related organization by the federal government.

        nc:IdentificationID
        A value that identifies something.
        This element will contain the ORI of the impounding agency.

  nc:Incident
  An occurrence or an event that may require a response.

    nc:ActivityIdentification
    An identification that references an activity.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the case number.

  n2:ImpoundActivity
  Details about a impound action associated with a vehicle.

    nc:ActivityIdentification
    An identification that references an activity.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the inventory number of the pound.

    nc:ActivityDate
    A date of an activity.

      nc:Date
      A full date.
      This optional element will contain the date the vehicle was impounded. The value should be in the format
      ccyy-mm-dd.

  n2:ImpoundOrganization
  Describes the entity that has impounded a vehicle.

    nc:OrganizationName
    A name of an organization.
    This element contains the name of the pound.

    nc:OrganizationPrimaryContactInformation
    A preferred means of contacting an organization.

      nc:ContactTelephoneNumber
      A telephone number for a telecommunication device by which a person or organization may be contacted.

        nc:FullTelephoneNumber
        A full telephone number.

          nc:TelephoneNumberFullID
          A complete telephone number.
          Telephone number for this location of the pound. The actual value (all numeric, no dashes) should be contained
          in the subelement.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried.

    nc:VehicleMakeCode
    A manufacturer of a vehicle.
    This optional element will contain the make of the vehicle being added. Allowable values come from the NCIC VMA
    code table.

    nc:VehicleModelCode
    A specific design or class of vehicle made by a manufacturer.
    This optional element will contain the model of the vehicle being added. Allowable values come from the NCIC VMO
    code table.

    nc:ConveyanceRegistrationPlateIdentification
    An identification on a metal plate fixed to a conveyance.

      nc:IdentificationID
      A value that identifies something.
      This optional element will contain the license plate number to be queried.

      nc:IdentificationCategoryText
      A kind of identification.
      This optional element should contain the type of license plate being queried. Allowable values come from the
      NCIC LIT code table.

      nc:IdentificationExpirationDate
      A date after which an identification is no longer valid.

        nc:Date
        A full date.
        This optional element's value should be the expiration date of the license plate. Data should be formatted
        yyyy-mm-dd.

      nc:IdentificationJurisdictionText
      An area, region, or unit in which a unique identification is issued.
      This optional element's value should be the issuing state of the license plate.

    nc:ItemModelYearDate
    A year in which an item was manufactured or produced.
    This optional element will contain the year of the vehicle. Data should be formatted YYYY.

    nc:VehicleStyleCode
    A style of a vehicle.
    This optional element will contain the style of the vehicle being added. Allowable values come from the NCIC VST
    code table.

  n2:NewYorkDerelictIndicator
  Optional element containing a Y if the vehicle is New York derelict.
  Optional element containing a Y if the vehicle is New York derelict.

  n2:MiscellaneousUpdateText
  Optional Miscellaneous Field. Free text format.
  Optional Miscellaneous Field. Free format.

Update Formats

Modification to Impound File (NUI)

n2:NICBImpoundRecordIdentification
This element will contain the NICB number being queried. The actual value is contained in nc:IdentificationID.

  nc:IdentificationID
  A value that identifies something.
  This element will contain the actual NICB number being queried.

n2:LawEnforcementAgency

  j:OrganizationAugmentation
  Additional information about an organization.

    j:OrganizationORIIdentification
    A unique identifier assigned to a justice-related organization by the federal government.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the ORI of the impounding agency.

nc:Incident
An occurrence or an event that may require a response.

  nc:ActivityIdentification
  An identification that references an activity.

    nc:IdentificationID
    A value that identifies something.
    This element will contain the case number.

n2:ImpoundActivity
Details about a impound action associated with a vehicle.

  nc:ActivityIdentification
  An identification that references an activity.

    nc:IdentificationID
    A value that identifies something.
    This optional element will contain the inventory number of the pound.

  nc:ActivityDate
  A date of an activity.

    nc:Date
    A full date.
    This optional element will contain the date the vehicle was impounded. The value should be in the format
    ccyy-mm-dd.

n2:ImpoundOrganization
Describes the entity that has impounded a vehicle.

  nc:OrganizationName
  A name of an organization.
  This element contains the name of the pound.

  nc:OrganizationPrimaryContactInformation
  A preferred means of contacting an organization.

    nc:ContactTelephoneNumber
    A telephone number for a telecommunication device by which a person or organization may be contacted.

      nc:FullTelephoneNumber
      A full telephone number.

        nc:TelephoneNumberFullID
        A complete telephone number.
        Telephone number for this location of the pound. The actual value (all numeric, no dashes) should be contained
        in the subelement.

nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

  nc:VehicleIdentification
  A unique combination of alphanumeric characters that identifies a specific vehicle.

    nc:IdentificationID
    A value that identifies something.
    This element will contain the VIN to be queried.

  nc:VehicleMakeCode
  A manufacturer of a vehicle.
  This optional element will contain the make of the vehicle being added. Allowable values come from the NCIC VMA
  code table.

  nc:VehicleModelCode
  A specific design or class of vehicle made by a manufacturer.
  This optional element will contain the model of the vehicle being added. Allowable values come from the NCIC VMO
  code table.

  nc:ConveyanceRegistrationPlateIdentification
  An identification on a metal plate fixed to a conveyance.

    nc:IdentificationID
    A value that identifies something.
    This optional element will contain the license plate number to be queried.

    nc:IdentificationCategoryText
    A kind of identification.
    This optional element should contain the type of license plate being queried. Allowable values come from the NCIC
    LIT code table.

    nc:IdentificationExpirationDate
    A date after which an identification is no longer valid.

      nc:Date
      A full date.
      This optional element's value should be the expiration date of the license plate. Data should be formatted
      yyyy-mm-dd.

    nc:IdentificationJurisdictionText
    An area, region, or unit in which a unique identification is issued.
    This optional element's value should be the issuing state of the license plate.

  nc:ItemModelYearDate
  A year in which an item was manufactured or produced.
  This optional element will contain the year of the vehicle. Data should be formatted YYYY.

  nc:VehicleStyleCode
  A style of a vehicle.
  This optional element will contain the style of the vehicle being added. Allowable values come from the NCIC VST
  code table.

n2:NewYorkDerelictIndicator
Optional element containing a Y if the vehicle is New York derelict.
Optional element containing a Y if the vehicle is New York derelict.

n2:MiscellaneousUpdateText
Optional Miscellaneous Field. Free text format.
Optional Miscellaneous Field. Free format.

Cancel Formats

Cancellation of Impound File (NCI)

n2:NLETSUpdateData

  n2:NICBImpoundRecordIdentification
  This optional element will contain unique NICB impound record number.

    nc:IdentificationID
    A value that identifies something.
    This element will contain the NICB number being queried.

  nc:Vehicle
  A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.

    nc:VehicleIdentification
    A unique combination of alphanumeric characters that identifies a specific vehicle.

      nc:IdentificationID
      A value that identifies something.
      This element will contain the VIN to be queried.

Response Formats

Response to Impound/Export query (NIR)

n2:NLETSResponseData

  n2:ResponseText


  This element will contain the free text response. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the


  response does not contain any characters illegal in XML.

Response to all files query (NAR)

n2:NLETSResponseData

  n2:ResponseText


  This element will contain the free text response. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the


  response does not contain any characters illegal in XML.

  Some manufacturers provide NICB with the status of vehicles which have special circumstances pertaining to them.
  NICB then places a status condition into the status field. NICB may or may not have additional information regarding a
  status condition. Therefore, if a vehicle has a status condition, NICB should be contacted. Below is a list of status
  conditions and their definitions:

CONDITION DEFINITION
UNDEFINED The situation about the vehicle or VIN plate is not clearly defined.
UNUSED The VIN plate and its embossed or stamped number will not be installed or assigned to a
 vehicle.
STOLEN FROM LOT The vehicle was stolen from a factory or dealer lot.
DESTROYED The vehicle has been completely destroyed.
SCRAPPED The vehicle is unusable.
INCORRECT The VIN number found on the vehicle is incorrect. This number does not conform to the
 Federal Motor Vehicle Standard.
STAMPING ERROR Hidden numbers found on the vehicle, i.e., engine, transmission and/or chassis numbers


 are not correct. This situation relates to domestic built vehicles which denote a VIN
 derivative stamped, embossed, or labeled on component parts.

STOLEN PLATE Manufacturer advises that only the VIN plate was stolen.
FLOOD DAMAGED The vehicle has had water damage and is not to be sold.
UNSCRAPPED The vehicle previously reported as a scrapped vehicle has been repaired and is being
 sold.
FIRE DAMAGED The vehicle is reported as having fire damage and is not to be sold.
REPLACEMENT Replacement VIN plate - The vehicle's original VIN plate was damaged or is missing and


 a replacement plate was issued by the manufacturer.
Replacement Parts - The vehicle's component part has been replaced and the part has a
 new number.

DONATED VEHICLE The vehicle was donated and removed from commerce.
TEST VEHICLE The vehicle is used for testing purposes and is not to be sold.
DATE The date in which the vehicle was shipped (ccyy-mm-dd).
DEALER NAME The name of the dealership that the vehicle was shipped to.
DEALER CODE The dealer code supplied by the dealer.
DEALER CITY, STATE The city and state where the dealer is located.
PHONE The phone number for the dealer.

  If NICB has no information for a particular field, the field header will not appear on the response.

Response to Entry, Update or Cancel (NEA, NUA, NCA)

n2:NLETSResponseData

  n2:ResponseText


  This element will contain the free text response. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to ensure that the


  response does not contain any characters illegal in XML.

National Insurance Crime Bureau, National Vehicle Services and Locator NIEM Examples

Example 1: A query for Impound/Export Information.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NIQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NA</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NIQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>AAAAA1111AA111111</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: A query of All Files.

<?xml version="1.0" encoding="utf-16"?>
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NA</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NAQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>AAAAA111111111111</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 3: An Entry to Impound File.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>NEI</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
		<nh2:DestinationORIID>NA</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSUpdateData n2:key="NEI">
		<n2:LawEnforcementAgency>
			<nc:OrganizationPrimaryContactInformation>
				<nc:ContactTelephoneNumber>
					<nc:FullTelephoneNumber />
				</nc:ContactTelephoneNumber>
			</nc:OrganizationPrimaryContactInformation>
			<j:OrganizationAugmentation xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
				<j:OrganizationORIIdentification>
					<nc:IdentificationID>AZNLETS45</nc:IdentificationID>
				</j:OrganizationORIIdentification>
			</j:OrganizationAugmentation>
		</n2:LawEnforcementAgency>
		<nc:Incident>
			<nc:ActivityIdentification>
				<nc:IdentificationID>123456</nc:IdentificationID>
			</nc:ActivityIdentification>
		</nc:Incident>
		<n2:ImpoundActivity>
			<nc:ActivityIdentification />
			<nc:ActivityDate>
				<nc:Date>2019-11-21</nc:Date>
			</nc:ActivityDate>
		</n2:ImpoundActivity>
		<n2:ImpoundOrganization>
		<nc:OrganizationName>NLETS IMPOUND</nc:OrganizationName>
		</n2:ImpoundOrganization>
		<nc:Vehicle>
			<nc:ItemModelYearDate>2008</nc:ItemModelYearDate>
			<nc:VehicleStyleCode>LL</nc:VehicleStyleCode>
			<nc:ConveyanceRegistrationPlateIdentification>
				<nc:IdentificationID>111AAA</nc:IdentificationID>
				<nc:IdentificationCategoryText>PC</nc:IdentificationCategoryText>
			</nc:ConveyanceRegistrationPlateIdentification>
			<nc:VehicleIdentification>
				<nc:IdentificationID>1A1AA111AAA111111</nc:IdentificationID>
			</nc:VehicleIdentification>
			<nc:VehicleMakeCode>KIA</nc:VehicleMakeCode>
			<nc:VehicleModelCode>SPT</nc:VehicleModelCode>
		</nc:Vehicle>
		<n2:MiscellaneousUpdateText>Miscellaneous Info</n2:MiscellaneousUpdateText>
	</n2:NLETSUpdateData>
</n2:NLETS>

Example 4: A Response from NICB on an Impound File being added.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NEA</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:18</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:18</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00831</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:ResponseText>
        IMPOUND RECORD ADDED VIN/1A1AA111111111111.FIL/A1111111111
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 5: A Modification to Impound File.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>NUI</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
		<nh2:DestinationORIID>NA</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSUpdateData n2:key="NUI">
		<n2:LawEnforcementAgency>
			<j:OrganizationAugmentation xmlns:j="http://niem.gov/niem/domains/jxdm/4.1">
				<j:OrganizationORIIdentification>
					<nc:IdentificationID>AZNLETS45</nc:IdentificationID>
				</j:OrganizationORIIdentification>
			</j:OrganizationAugmentation>
		</n2:LawEnforcementAgency>
		<nc:Incident>
			<nc:ActivityIdentification>
				<nc:IdentificationID>123456</nc:IdentificationID>
			</nc:ActivityIdentification>
		</nc:Incident>
				<n2:ImpoundOrganization>
		<nc:OrganizationName>NLETS IMPOUND</nc:OrganizationName>
		</n2:ImpoundOrganization>
		<n2:ImpoundActivity>
			<nc:ActivityIdentification />
			<nc:ActivityDate>
				<nc:Date>2011-01-01</nc:Date>
			</nc:ActivityDate>
		</n2:ImpoundActivity>
		<nc:Vehicle>
			<nc:ConveyanceRegistrationPlateIdentification />
			<nc:VehicleIdentification />
		</nc:Vehicle>
		<n2:MiscellaneousUpdateText>Miscellaneous Info</n2:MiscellaneousUpdateText>
	</n2:NLETSUpdateData>
</n2:NLETS>

Example 6: A Response from NICB on a successful modification to an Impound File.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NUA</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:28</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:28</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00849</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData>
    <n2:ResponseText>
         IMPOUND RECORD UPDATED
         FIL/A1111111111
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 7: A Cancellation of Impound File.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
	<n2:NLETSMessageHeader>
		<nh2:MessageKeyCodeText>NCI</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
		<nh2:DestinationORIID>NA</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[NLETSTEST1]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSUpdateData n2:key="NCI">
		<n2:NICBImpoundRecordIdentification>
			<nc:IdentificationID>A1111111111</nc:IdentificationID>
		</n2:NICBImpoundRecordIdentification>
		<nc:Vehicle>
			<nc:VehicleIdentification>
				<nc:IdentificationID>1AAAA11A1AA111111</nc:IdentificationID>
			</nc:VehicleIdentification>
		</nc:Vehicle>
	</n2:NLETSUpdateData>
</n2:NLETS>

Example 8: A Response from NICB on a successful cancellation of an Impound File.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NCA</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:32</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:32</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00861</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NCA">
    <n2:ResponseText>
           IMPOUND RECORD CANCELLED VIN/AAAAA11A11A111111.FIL/A1111111111
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 9: A response to Impound/Export query.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NIR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:34</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:34</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00863</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NIR">
    <n2:ResponseText>
         ** NOTICE **         THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY         AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT         VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR         LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU         TAKE ANY ENFORCEMENT ACTION.         NICB RESPONSE FOR VIN/19AAA1A11AA111111 MSG 01 OF 01         *IMPOUND*         NICB FILE#/ A1111111111         ORI OF IMPOUNDING AGENCY/ AZ0000000 CASE #/111111         DATE OF IMPOUND/ 01/01/11 POUND/ STATE RECOVERY         VMA/ HOND VMO/ CIV VYR/ 10 VST/ 4D         MISC/ CONTACT SMITH         POUND PHONE #/ 6025551234     </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 10: A response from All Files.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:35</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:35</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00865</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
       ** NOTICE **
       THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
       AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
       VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
       LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
       TAKE ANY ENFORCEMENT ACTION.
       NICB RESPONSE FOR VIN/AAAAA1111AA111111
       MSG 02 OF 02
       CLAIM #/ 1111A111111111111111
       ACTUAL CASH VALUE/ 008000
       RECEIVED VALUE/ 000000 APPRAISED VALUE/ 000000
       *SALVAGE*
       NICB FILE#/ A1111111111
       VYR/ 99 VMA/ HOND DATE OF SALVAGE/ 05/16/10
       CAUSE OF CLAIM (LOSS)/ THEFT/STRIPPED
       INSURANCE COMPANY/ INSURANCE COMPANY
       INSURANCE COMPANY LOCATION/ PHOENIX,AZ
       CLAIM #/ 1111A11111111111111 ACTUAL CASH VALUE/ 009000
       RECEIVED VALUE/ 000900 APPRAISED VALUE/ 000000
       * NCIC INACTIVE VEHICLE *NICB FILE#/ A1111111111
       **** NEW NICB FILE INQUIRY FOR ANY QUESTIONS PLEASE CONTACT NICB ****
       602-555-1234
       VYR/99 VMA/HOND VMO/PRE VST/2D VCO/SIL
       NCIC#/ A111111111 NCIC MESSAGE KEY/ LV
       DATE OF THEFT/ 05/16/10 ORI/ AZ0000000 OCA/ 01-1234
       DATE OF RECOVERY/ 05/20/10 PLACE OF RECOVERY/ AZ0000000
       RECOVERING AGENCY CASE#/ 01-1234
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 11: A query to Locator Technologies for Canada.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NA</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NAQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>1HGCM71696A801057</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 12: A response from Locator Technologies for Canada.

Message 1:

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:37</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:37</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00871</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>** NOTICE **
      THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
      AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
      VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
      LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
      TAKE ANY ENFORCEMENT ACTION.
      NICB RESPONSE FOR VIN/1HGCM71696A801057    MSG 01 OF 01

      *SHIPPING*                                                            
      DATE/ 05/18/06                                                        
      DEALER NAME/ AMERICAN HONDA OF CANADA        DEALER CODE/ 809958      
      DEALER CITY, ST/ SCARBOROUGH              ,ON</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 2:

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:38</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:38</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00875</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>Locator Technologies Vehicle Impound records for VIN: 1HGCM71696A801057

      Impound Date : 2019-04-14
      Notes        : INVOICE 190128
      PO# NON-CONTRACT
      Location     : 180 Bullock St Unit 7 Markham ON L3P7N2
      Contact Name : Cardinal Towing Inc.,
      Contact Phone: 9054720426 or 4168841977
      Contact Email: impound@cardinaltowing.ca

      This information is being provided by Locator Technologies, LLC.
      If you require additional information or assistance, please contact
      a Law Enforcement Assistant at 310-722-2889.

      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 13: A query to Locator Technologies for Mexico.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NA</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NAQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>3N1EB31S49K367039</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 14: A response from Locator Technologies for Mexico.

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:41</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:41</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00877</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>Locator Technologies Vehicle Impound records for VIN: 3N1EB31S49K367039

      Source       : Mexico
      Impound Date : 2017-10-24
      Plate Number : MEX6972
      Vehicle Year : 2009
      Vehicle Make : NISSAN
      Vehicle Model: TSURU III
      Vehicle Color: BLUE
      Location     : OCRA Amecameca

      This information is being provided by Locator Technologies, LLC.
      The response contains information on vehicles impounded
      in Mexico which may be incomplete or will require additional
      effort to confirm.  For support with Mexico impound data
      please contact Locator Technologies Mexico Representatives
      mexico@locatortechnologies.com / 626-926-4943 or
      National Vehicle Services 708-429-0123 / n.v.s@att.net

      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 2:

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:08</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:08</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00002</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00107</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
      <![CDATA[Locator Technologies Vehicle Impound records for VIN: 3N1EB31S49K367039

      Source       : Mexico
      Impound Date : 2017-10-24
      Plate Number : MEX6972
      Vehicle Year : 2009
      Vehicle Make : NISSAN
      Vehicle Model: TSURU III
      Vehicle Color: BLUE
      Location     : OCRA Amecameca

      This information is being provided by Locator Technologies, LLC.
      The response contains information on vehicles impounded
      in Mexico which may be incomplete or will require additional
      effort to confirm.  For support with Mexico impound data
      please contact Locator Technologies Mexico Representatives
      mexico@locatortechnologies.com / 626-926-4943 or
      National Vehicle Services 708-429-0123 / n.v.s@att.net

      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 15: A query to Locator Technologies for America.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NA</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NAQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>1HGCR2F31EA024438</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 16: A response from Locator Technologies for America.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:12</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:12</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12020</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00112</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
      <![CDATA[** NOTICE **
      THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
      AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
      VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
      LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
      TAKE ANY ENFORCEMENT ACTION.
      NICB RESPONSE FOR VIN/1HGCR2F31EA024438    MSG 01 OF 02

      *SHIPPING*                                                            
      DATE/ 09/14/13                                                        
      DEALER NAME/ SOUTHWEST HONDA                 DEALER CODE/ 206601      
      DEALER CITY, ST/ AMARILLO                 ,TX                         
      *VEHICLE CLAIMS*         NICB FILE#/ H0237603246                      
      MEMBER COMPANY/ GOVERNMENT EMPLOYEES INSURANCE COMPANY                
      CLAIM NO/ 0487406520101040-09             INS PHONE/ 00000000000      
      IMPACT POINT/ REAR CENTER              MILEAGE/ 000000000             
      *VEHICLE CLAIMS*         NICB FILE#/ H0281053162                      
      MEMBER COMPANY/ FARMERS INSURANCE COMPANY INC                         
      CLAIM NO/ 7000002257-1-1                  INS PHONE/ 00000000000      
      IMPACT POINT/ NOT SUPPLIED             MILEAGE/ 000000000             
      *VEHICLE CLAIMS*         NICB FILE#/ H0288916997                      
      MEMBER COMPANY/ FARMERS INSURANCE COMPANY INC                         
      CLAIM NO/ 7000033469-1-1                                              
      IMPACT POINT/ POINT OF IMPACT UNKNOWN  MILEAGE/ 000075652             
      *VEHICLE CLAIMS*         NICB FILE#/ H0288920308                      
      MEMBER COMPANY/ FARMERS INSURANCE COMPANY INC                         
      CLAIM NO/ 7000033469-1-1                  INS PHONE/ 00000000000      
      IMPACT POINT/ FRONT CENTER             MILEAGE/ 000000000]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 2:
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:12</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:12</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>11854</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00113</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
      <![CDATA[** NOTICE **
      THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
      AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
      VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
      LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
      TAKE ANY ENFORCEMENT ACTION.
      NICB RESPONSE FOR VIN/1HGCR2F31EA024438    MSG 02 OF 02

      * NCIC INACTIVE VEHICLE *NICB FILE#/ N0054538545                      
      **** NEW NICB FILE INQUIRY FOR ANY QUESTIONS PLEASE CONTACT NICB **** 
                             847-544-7002                             
      VYR/14 VMA/HOND VMO/ACC VST/4D VCO/WHI                                
      NCIC#/ V680593806 NCIC MESSAGE KEY/ LV                                
      DATE OF THEFT/ 09/12/18 ORI/ MN0620900 OCA/ 18210021                  
      DATE OF RECOVERY/ 10/24/18 PLACE OF RECOVERY/ LANPD0002]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 3:
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:12</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:12</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00005</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00114</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
      <![CDATA[Locator Technologies Vehicle Impound records for VIN: 1HGCR2F31EA024438

      Impound Date : 2019-03-01
      Notes        : 648371
      Location     : 1396 Concordia Ave St Paul MN 55104
      Contact Name : Twin Cities Transport & Recovery
      Contact Phone: 651-429-5720
      Contact Email: jonathan.jones@tctr.com

      This information is being provided by Locator Technologies, LLC.
      If you require additional information or assistance, please contact
      a Law Enforcement Assistant at 310-722-2889.

      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 4:
<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NVNVS005V</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:12</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:12</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00064</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00115</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NAQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>1HGCR2F31EA024438</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>RESPONSE FOR VIN/ 1HGCR2F31EA024438
      VEHICLE LEASED FROM/ Toyota Financial Services

      NHTSA Unresolved Recall
      VIN: 1HGCR2F31EA024438
      Recall #: 17V418
      Recalled Component: ELECTRICAL SYSTEM:BATTERY

      Please refer to the NHTSA website http://www.nhtsa.gov/recalls
      or your Dealer with your VIN, there may be one or more open
      recalls on this vehicle.

      This response may contain Lien Holder, Mexican OCRA, and EBay auction data.
      This is in addition to a second response you will receive via Nlets that
      will contain Impound, Import/Export, Insurance Theft File, NCIC/CPIC Vehicle
      Purge Data, Manufacturer's Shipping File, Salvage File, International Index,
      Auction File, Pre-Inspection File, Vehicle Physical Damage Claim File, and Rental File data.

      This information is being provided by National Vehicle Service, NFPC.
      If you require additional information or assistance, please contact
      a Law Enforcement Assistant at 866-687-1102.

      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 17: A query to Locator Technologies for Vinspection Mobile App.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0"
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0"
xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
n2:version="4.00" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS45</nh2:OriginatingORIID>
    <nh2:DestinationORIID>NA</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="NAQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>JN1CA21D4XT800593</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 18: A response from Locator Technologies for Vinspection Mobile App.

Message 1:

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:24</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:24</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>12338</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00116</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
      <![CDATA[** NOTICE **
      THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
      AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
      VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
      LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
      TAKE ANY ENFORCEMENT ACTION.
      NICB RESPONSE FOR VIN/JN1CA21D4XT800593    MSG 01 OF 01

      *SHIPPING*                                                            
      DATE/ 08/31/98                                                        
      DEALER NAME/ DYAS NISSAN, INC.               DEALER CODE/ 2029        
      DEALER CITY, ST/ AUBURN                   ,AL  PHONE/ 3348214888]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 2:

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10:24</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>06/28/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>10:24</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00003</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00117</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>
      <![CDATA[Locator Technologies Vehicle Impound records for VIN: JN1CA21D4XT800593

      Impound Date : 2019-04-16
      GPS Location : 30.4483007 -88.3507168
      Contact Name : Felicia
      Contact Phone: 251-277-6020
      Contact Email: feliciablackwell89@gmail.com

      This information is being provided by Locator Technologies, LLC.
      If you require additional information or assistance, please contact
      a Law Enforcement Assistant at 310-722-2889.

      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.]]>
    </n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Message 3:

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[LOCATORTST]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:08</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:08</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00806</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>OCRA Mexico Stolen Vehicle Report for VIN: 3FA6P0H9XER153622

Stolen Date  : 2018-10-16
Vehicle Year : 2014
Vehicle Make : FORD
Vehicle Model: FUSION

This information is being provided by Locator Technologies, LLC
on behalf of OCRA.
The information provided, herein, is only an investigative tool
and has not been verified.  Please check with the California
Highway Patrol (CHP) - Mexican Liason Unit (MLU) at
MLU-601@chp.ca.gov or 858-650-3690 before taking any action.

Alternatively you may contact Locator Technologies Mexico Representatives
at mexico@locatortechnologies.com or Dennis Frias 626-926-4943
or Oscar Alva 619-572-6770.</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 19: A query to Locator Technologies for OCRA database

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>SVQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
    <nh2:DestinationORIID>LT</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CR055F1R31]]></nh2:DocumentControlFieldText>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="SVQ">
    <nc:Vehicle>
      <nc:VehicleIdentification>
        <nc:IdentificationID>3FA6P0H9XER153622</nc:IdentificationID>
      </nc:VehicleIdentification>
    </nc:Vehicle>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 20: A response from Locator Technologies from the OCRA database

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>SVR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CR055F1R31]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/22/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>11:09</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/22/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>11:09</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00825</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="SVR">
    <n2-svr:StolenVehicleRecord xmlns:n2-svr="http://www.nlets.org/niem/nlets-stolen-vehicle/1.0">
      <nc:Vehicle xmlns:nc="http://release.niem.gov/niem/niem-core/4.0/">
        <nc:ItemMakeName>FORD</nc:ItemMakeName>
        <nc:ItemModelName>FUSION</nc:ItemModelName>
        <nc:ItemModelYearDate>2014</nc:ItemModelYearDate>
        <nc:VehicleIdentification>
          <nc:IdentificationID>3FA6P0H9XER153622</nc:IdentificationID>
        </nc:VehicleIdentification>
      </nc:Vehicle>
      <n2-svr:VehicleTheft>
        <nc:ActivityDate xmlns:nc="http://release.niem.gov/niem/niem-core/4.0/">
          <nc:Date>2018-10-16</nc:Date>
        </nc:ActivityDate>
      </n2-svr:VehicleTheft>
    </n2-svr:StolenVehicleRecord>
  </n2:NLETSResponseData>
</n2:NLETS>

Top

Legacy (DEPRECATED)

National Insurance Crime Bureau and National Vehicle Services Legacy Specifications

This section describes message specifications and formats so that agencies may utilize the resources of the National Insurance Crime Bureau.

NICB and NCIC Stolen Vehicle Entries

NICB has a mirror image of NCIC's stolen vehicle file. Every stolen vehicle entered on NCIC will be passed to NICB by NCIC. NICB will enter this record on their file and will interrogate Impound (last 60 days entries), Export, Auction and International Index Files.

If a VIN match is made, the following message will be forwarded via Nlets ("AM" message) to the entering agency:

"THIS IS TO NOTIFY YOU THAT THE VEHICLE YOU ENTERED INTO NCIC,
VIN/12345671234567890, IS IN THE NICB DATABASE. BELOW IS THE NICB RELATED VEHICLE
RECORD. THIS MAY ASSIST YOU WITH ANY FOLLOW UP INVESTIGATION.
(followed by matching NICB record)

Queries to NICB Record Files

NICB provides automated access to twelve different files as listed below:

Impound file Pre-Inspection File
Export File Vehicle Claim File
Manufacturer's Shipping File Rental File
Salvage File Theft File
International Index File Theft (recovery) File
Auction File NCIC/CPIC Canceled File

These files may be accessed via two distinct types of inquiries.

  • One will access only the Impound and Export files (NIQ).
  • The other will access all ten files listed above (NAQ).

Access to these files is for investigative purposes only.

Users should not program their computers to automatically send inquiries to these files whenever an inquiry is sent to either the NCIC stolen vehicle file or state vehicle registration files.

If no information is found on any of the twelve NICB files the following message will be displayed: NO RECORD NICB.

Impound/Export File Inquiry (NIQ)

This transaction interrogates the NICB Impound and Export files only.

  • Impound records will only be returned on an "NIQ" if the date of impound is less than 60 days from the date of the inquiry.
  • The message key identifying a query on impound and export files is NIQ.
  • The destination ORI of NICB is "NA".

The following elements are included in an Impound/Export File query (NIQ)

Entry # Char. Explanation
NIQ. 3 Message key identifies query on Impound & Export files
followed by a period.
Sender ORI. 9 ORI of sender followed by a period.
NA. 2 Destination ORI of NICB followed by a period and optional
control field.
TXT 3 Fixed filed prefix to beginning of message.
VIN/ 4 Prefix for VIN.
VIN Max. 20 VIN for vehicle (no period after last field in inquiry).

All Files Inquiry (NAQ)

This transaction interrogates all available NICB files with one exception.

  • If only a partial VIN is available the user may submit the last 8 characters of the VIN.
  • In order to identify the VIN as partial to NICB the user MUST preface the partial VIN by the word "PARTIAL".
    For example a partial VIN with the year 1990 would look like this:
         VIN/PARTIAL24657490.
    Note that there is no space or separator between the word "PARTIAL" and the eight character VIN.
  • When a partial VIN search is requested only the Manufacturers Shipping File will be searched.

The following is the format for the "all NICB files" inquiry (NAQ).

Entry # Char. Explanation
NAQ. 3 Message key identifies query on Impound & Export files followed
by a period.
Sender ORI. 9 ORI of sender followed by a period.
NA. 2 Destination ORI of NICB followed by a period and optional
control field.
TXT 3 Fixed filed prefix to beginning of message.
VIN/ 4 Prefix for VIN.
VIN Max. 20

VIN for vehicle (no period for last data element); partial VIN may
be on the last 8 characters. A partial VIN must be preceded by
the word "PARTIAL". (E.G., VIN/PARTIAL24657490 Only the
Manufacturer's Shipping File will be searched on a partial VIN inquiry.

Responses to NICB Record File Queries (NAR)

Since NICB will be interrogating ten different files, responses will vary based on the hits that were made.

Manufacturer's Shipping File Response

Below is a list of status conditions and their definitions:

CONDITION DEFINITION
UNDEFINED The situation about the vehicle or VIN plate is not clearly defined.
UNUSED The VIN plate and its embossed or stamped number will not be
installed or assigned to a vehicle.
STOLEN FROM LOT The vehicle was stolen from a factory or dealer lot.
DESTROYED The vehicle has been completely destroyed.
SCRAPPED The vehicle is unusable.
INCORRECT The VIN number found on the vehicle is incorrect. This number
does not conform to the Federal Motor Vehicle Standard.
STAMPING ERROR

Hidden numbers found on the vehicle, i.e., engine, transmission
and/or chassis numbers are not correct. This situation relates to
domestic built vehicles which denote a VIN derivative stamped,
embossed, or labeled on component parts.

STOLEN PLATE Manufacturer advises that only the VIN plate was stolen.
FLOOD DAMAGED The vehicle has had water damage and is not to be sold.
UNSCRAPPED The vehicle previously reported as a scrapped vehicle has been
repaired and is being sold.
FIRE DAMAGED The vehicle is reported as having fire damage and is not to be sold.
REPLACEMENT

Replacement VIN plate - The vehicle's original VIN plate was
damaged or is missing and a replacement plate was issued by the
manufacturer.
Replacement Parts - The vehicle's component part has been
replaced and the part has a new number.

DONATED VEHICLE The vehicle was donated and removed from commerce.
TEST VEHICLE The vehicle is used for testing purposes and is not to be sold.
DATE The date in which the vehicle was shipped (mm/dd/yy or ccyymmdd).
DEALER NAME The name of the dealership that the vehicle was shipped to.
DEALER CODE The dealer code supplied by the dealer.
DEALER CITY, STATE The city and state where the dealer is located.
PHONE The phone number for the dealer.

If NICB has no information for a particular field, the field header will not appear on the response.

Salvage File Response

Entry Explanation
VYR/ The last two digits of the model year of the vehicle.
VMA/ The vehicle make as encoded in NCIC supplied tables.
DATE OF SALVAGE/ Date of salvage (mm/dd/yy or ccyymmdd).
CAUSE OF CLAIM/LOSS/ Cause of claim or loss.
INSURANCE COMPANY/ Name of insurance company.
INSURANCE COMPANY ADDRESS/ City and state where insurance company is located.
INSURANCE COMPANY PHONE/ Phone number of insurance company.
CLAIM #/ Claim number of insurance company.
ACTUAL CASH VALUE/ Actual cash value prior to loss.
RECEIVED VALUE/ Dollar amount insured received for loss.
APPRAISED VALUE/ Appraised value at the time of loss.

If NICB has no information for a particular field, the field header will not appear on the response.

Impound File Response

Impound records will only be returned on an "NIQ" if the date of impound is less than 60 days from the date of the inquiry.

Entry Explanation
ORI OF IMPOUNDING
AGENCY/
The nine digit identifier for the place of recovery/impound.
CASE #/ Case number assigned by the law enforcement agency that holds
the theft report.
DATE OF IMPOUND/ Date of recovery/impound (mm/dd/yy or ccyymmdd).
POUND/ Name of impounding lot.
VMA/ The vehicle make as encoded in NCIC supplied tables.
VMO/ The vehicle model of impounded vehicle.
VYR/ Last two or four digits of the model year of the vehicle.
VST/ The vehicle type as encoded in NICB tables.
LIC/ License number of impounded vehicle.
LIS/ The state in which the vehicle is licensed.
LIY/ The license year.
LIT/ The type of license issued.
MISC/ Miscellaneous information
POUND INV #/ Invoice number assigned by the impounding agency.
POUND PHONE/ The phone number of the impounding lot.
NY DERELICT/ Indicates whether or not the vehicle was impounded under the New
York Derelict program.

Export File Response

Entry Explanation
VYR/ Last two or four digits of the model year of the vehicle.
VMA/ The vehicle make as encoded in NCIC supplied tables.
DATE OF EXPORT/ Date of export (mm/dd/yy or ccyymmdd).
DESTINATION/ Destination of export.

If NICB has no information for a particular field, the field header will not appear on the response.

International Index Response

Sample response for an International Index Theft:

International Index Theft Response

NICB RESPONSE FOR VIN/1FABP10B7BF123456 MSG 01 OF 01
* INTERNATIONAL THEFT *
VYR/ XX VMA/ XX DATE OF THEFT/ XX/XX/XX FILNR/XXXXXXXXXXX
OWNER/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Sample response for an International Index Salvage:

International Index Salvage Response

NICB RESPONSE FOR VIN/1FABP10B7BF123456 MSG 01 OF 01
* INTERNATIONAL SALVAGE *
VYR/ XX VMA/ XX DATE OF SALVAGE/ XX/XX/XX FILNR/XXXXXXXXX
OWNER/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Below is an explanation of the entries in the International Index Salvage responses above.

Entry Explanation
VYR/ Last two digits of the model year of the vehicle.
VMA/ The vehicle make as encoded in NCIC supplied tables.
DATE OF THEFT/ Date of theft (mm/dd/yy or ccyymmdd).
DATE OF SALVAGE/ Date of salvage (mm/dd/yy or ccyymmdd).
FILNR/ Unique file number of record owner.
OWNER/ Owner of record.

Users should contact NICB if a hit is obtained on these records. If NICB has no information for a particular field, the field header will not appear on the response.

Auction File Response

Entry Explanation
AUCTION COMP/ Name of the Auction Company in possession of the vehicle.
AUCTION REFERENCE/ Number assigned to the vehicle by the Auction Company.
DATE OF AUCTION/ Day the vehicle is scheduled for auction (mm/dd/yy or ccyymmdd)
VYR/ Last two or four-digit model year of the vehicle.
VMA/ Vehicle make as encoded in NCIC supplied tables.
VMO/ Vehicle model as encoded in the NCIC tables.
ODOMETER/ Odometer reading as reported by the Auction Company.

If NICB has no information for a particular field, the field header will not appear on the response.

Pre-Inspection File Response

Entry Explanation
PRE-INSP COMP/ The name of the company responsible for the pre-inspection.
INSP DATE/ The date of the pre-inspection (mm/dd/yy or ccyymmdd)
INSP REPT #/ Inspection company file #
ODOMETER/ Odometer reading at time of inspection

If NICB has no information for a particular field, the field header will not appear on the response.

Vehicle Claim Responses

Entry Explanation
MEMBER COMPANY/ The name of the company that reported the claim.
CLAIM NUMBER/ The number assigned by the insurance company
INS PHONE/ The telephone number of the filing insurance company office
IMPACT POINT/ The initial impact point of the vehicle according to the filed claim
MILEAGE/ The mileage at the time of the accident.

If NICB has no information for a particular field, the field header will not appear on the response.

Rental File Response

Below is an explanation of the entries in the rental file response sample.

Entry Explanation
RENTAL COMP/ The name of the rental company.
RENTAL REFERENCE #/ The rental company's file #.
ACTIVITY DATE/ The date last action was taken on vehicle
(mm/dd/yy or ccyymmdd).
ACTIVITY REASON/ The reason the vehicle is on file.
NAME/ The name of the customer that rented the
vehicle.
ADDR/ The address of the customer.
VYR/ Vehicle year (2 or 4 characters).
VMA/ The vehicle make as encoded in NCIC supplied tables.
VST/ The vehicle style.
ODOMETER/ The odometer reading at time of activity.

If NICB has no information for a particular field, the field header will not appear on the response.

NICB Theft Response

The table below describes the entries in the Theft/Theft Recovery file sample.

Entry Explanation
CONDITION OF RECOVERY/ Condition of vehicle at time of recovery
RECOVERING ORI/ The 9 digit identifier of the recovering agency
REPORTING ORI/ The 9 digit identifier of the reporting agency

Formats to Add, Cancel, and Modify NICB Impound Files

Add a Record to the NICB Impound File

This transaction adds a record to the NICB impound file. The asterisked data fields are optional for entry. Below is the format for the impound entry transaction.

Entry # Char. Explanation
NEI. 3 Message key identifies NICB entry of Impound record
followed by a period.
Sender ORI. 9 ORI of sender followed by a period
NA. 2 Destination ORI of NICB followed by a period and
optional control field.
TXT 3 Fixed filed prefix to beginning of message
VIN/ 4 Prefix for VIN
VIN Max. 20 VIN for vehicle (no period after last field in inquiry)
ORI/ 4 Prefix for impound agency ORI
ORI. 9 ORI of impounding agency followed by a period
OCA/ 4 Prefix for Case #
Case #. 20 Case #(no special characters) followed by a period
DOI/ 4 Prefix for Date of Impound
Date of Impound 6-8 Date vehicle was impounded followed by a period.
mmddyy or ccyymmdd.
PND/ 4 Prefix for Name of Pound holding vehicle
Pound Name 24 Name of Pound holding vehicle followed by a period
VMA/ 4 Prefix for Vehicle Make
* Veh. Make 2-4 Vehicle Make followed by a period
VMO/ 4 Prefix for Vehicle Model
* Veh. Model 3 Vehicle Model followed by a period
VYR/ 4 Prefix for Vehicle Year
* Veh. Year 2-4 Vehicle Year followed by a period
VST/ 4 Prefix for Vehicle Style
* Veh. Style 2 Vehicle style followed by a period
LIC/ 4 Prefix for License # followed by a period
* License # 1-10 License # followed by a period
LIS/ 4 Prefix for License State followed by a period
* License State 2 License State followed by a period
LIY/ 4 Prefix for License Year
* License Year 2 License Year followed by a period
LIT/ 4 Prefix for License Type
* License Type 2 License Type followed by a period
MSC/ 4 Prefix for Miscellaneous Field
* Misc. Field 42 Free format field followed by a period
INV/ 4 Prefix for Pound's Inventory #
* Inventory # 12 Pound's Inventory # followed by a period
PHO/ 4 Prefix for Phone # of Pound
* Phone # 10 Phone # of Pound followed by a period
DER/ 4 Prefix for New York Derelict Vehicle
* Y 1 Fixed field of "Y" if a New York Derelict (Note: last field
must not be followed by a period)
  • Optional Fields

When the impound record is successfully entered you will receive an acknowledgment message from NICB.

If an error is made NICB will return an error message and the complete text of the entry.

If there is a duplicate record on file you will receive a message from NICB.

Modify an NICB Impound Record

The format for the Modify Impound Record transaction is provided in the table below.

  • Those data fields that have a double asterisk(**) may be added, deleted or modified.
  • Those fields with a single asterisk(*) may not be deleted since they are required fields.
  • The "FIL" and "ORI" fields are required and may not be updated in any way.
Entry # Char. Explanation
NUI. 3 Message key identifies NICB update of Impound record
followed by a period.
Sender ORI. 9 ORI of sender followed by a period.
NA. 2 Destination ORI of NICB followed by a period and
optional control field.
TXT 3 Fixed filed prefix to beginning of message.
FIL/ 4 Prefix for unique NICB impound record number.
File # 11 Unique NICB impound record number followed by period.
ORI/ 4 Prefix for impound agency ORI.
ORI. 9 ORI of impounding agency followed by a period.
OCA/ 4 Prefix for Case #.
* Case #. 20 Case #(no special characters) followed by a period.
DOI/ 4 Prefix for Date of Impound.
* Date of Impound 6-8 Date vehicle was impounded followed by a period.
mmddyy or ccyymmdd.
PND/ 4 Prefix for Name of Pound holding vehicle.
* Pound Name 24 Name of Pound holding vehicle followed by a period.
VMA/ 4 Prefix for Vehicle Make.
** Veh. Make 2-4 Vehicle Make followed by a period.
VMO/ 4 Prefix for Vehicle Model.
** Veh. Model 3 Vehicle Model followed by a period.
VYR/ 4 Prefix for Vehicle Year.
** Veh. Year 2-4 Vehicle Year followed by a period.
VST/ 4 Prefix for Vehicle Style.
** Veh. Style 2 Vehicle style followed by a period.
LIC/ 4 Prefix for License # followed by a period.
** License # 1-10 License # followed by a period.
LIS/ 4 Prefix for License State followed by a period.
** License State 2 License State followed by a period.
LIY/ 4 Prefix for License Year.
** License Year 2 License Year followed by a period.
LIT/ 4 Prefix for License Type.
** License Type 2 License Type followed by a period.
MSC/ 4 Prefix for Miscellaneous Field.
** Misc. Field 42 Free format field followed by a period.
INV/ 4 Prefix for Pound's Inventory #.
** Inventory # 12 Pound's Inventory # followed by a period.
PHO/ 4 Prefix for Phone # of Pound.
** Phone # 10 Phone # of Pound followed by a period.
DER/ 4 Prefix for New York Derelict Vehicle.
** Y 1 Fixed field of "Y" if a New York Derelict (Note: last field
must not be followed by a period).

When the impound record is successfully modified you will receive an acknowledgment message from NICB.

Cancel an NICB Impound Record

NICB maintains NCIC canceled records online dating back to 1972. Both NCIC and CPIC have authorized the release of canceled records by NICB.

Below is the format for the cancel impound transaction.

Entry # Char. Explanation
NCI. 3 Message key identifies cancel of Impound record followed by a
period.
Sender ORI. 9 ORI of sender followed by a period.
NA. 3 Destination ORI of NICB followed by a period and optional control
field.
TXT 3 Fixed filed prefix to beginning of message.
VIN/ 4 Prefix for VIN.
VIN Max. 20 VIN for vehicle (no period after last field in inquiry).
FIL/ 4 Prefix for NICB file (record) number.
File Number 11 NICB file number assigned to each impound record.

When the impound record has been successfully canceled you will receive a message from NICB.

National Insurance Crime Bureau and National Vehicle Services Legacy Examples

Example 1: A query for Impound/Export Information.

NIQ.AZNLETS20.NA.TXT
VIN/AAAAA1111AA111111

Example 2: A query of All Files.

NAQ.AZNLETS20.NA.TXT
VIN/AAAAA111111111111

Example 3: An Entry to Impound File.

NEI.AZNLETS20.NA.TXT
VIN/1A1AA111AAA111111.ORI/AZ0000000.OCA/A11111111.DOI/20120101.
PND/TOWING COMPANY.VMA/CHEV.VMO/CAV.VYR/2000.VST/4D.LIC/111AAA.
LIS/AZ.LIT/PC.MSC/AUTOMOTIVE CENTER, CONTACT JOHN.PHO/6025551234

Example 4: A Response from NICB on an Impound File being added.

NEA.ILNATBC00
10:00 01/01/2010 61239
10:00 01/01/2010 01239 AZNLETS20
TXT
IMPOUND RECORD ADDED VIN/1A1AA111111111111.FIL/A1111111111

Example 5: A Modification to Impound File.

NUI.AZNLETS20.NA.TXT
FIL/A1111111111.ORI/AZ0000000.DOI/20110101

Example 6: A Response from NICB on a successful modification to an Impound File.

NUA.ILNATBC00
15:00 01/01/2010 81232
15:00 01/01/2010 11239 AZNLETS20
TXT
IMPOUND RECORD UPDATED
FIL/A1111111111

Example 7: A Cancellation of Impound File.

NCI.AZNLETS20.NA.TXT
VIN/1AAAA11A1AA111111.FIL/A1111111111

Example 8: A Response from NICB on a successful cancellation of an Impound File.

NCA.ILNATBC00
15:00 01/01/2010 51231
15:00 01/01/2010 81235 AZNLETS20
TXT
IMPOUND RECORD CANCELLED VIN/AAAAA11A11A111111.FIL/A1111111111

Example 9: A response to Impound/Export query.

NIR.ILNATBC00
15:00 01/01/2010 21231
15:00 01/01/2010 01232 AZNLETS20
TXT
** NOTICE **
THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
TAKE ANY ENFORCEMENT ACTION.
NICB RESPONSE FOR VIN/19AAA1A11AA111111 MSG 01 OF 01
*IMPOUND*
NICB FILE#/ A1111111111
ORI OF IMPOUNDING AGENCY/ AZ0000000 CASE #/111111
DATE OF IMPOUND/ 01/01/11 POUND/ STATE RECOVERY
VMA/ HOND VMO/ CIV VYR/ 10 VST/ 4D
MISC/ CONTACT SMITH
POUND PHONE #/ 6025551234

Example 10: A response from All Files.

NAR.ILNATBC00


10:00 01/01/2010 21235
10:00 01/01/2010 81238 AZNLETS20
TXT
** NOTICE **
THE NICB PROVIDES THE INFORMATION CONTAINED HEREIN SOLELY
AS AN INVESTIGATORY AID. SINCE THESE RECORDS ARE NOT
VALIDATED, THE NICB DOES NOT GUARANTEE OR WARRANT THEIR
LEGITIMACY. PLEASE USE SECONDARY VERIFICATION BEFORE YOU
TAKE ANY ENFORCEMENT ACTION.
NICB RESPONSE FOR VIN/AAAAA1111AA111111
MSG 02 OF 02
CLAIM #/ 1111A111111111111111
ACTUAL CASH VALUE/ 008000
RECEIVED VALUE/ 000000 APPRAISED VALUE/ 000000
*SALVAGE*
NICB FILE#/ A1111111111
VYR/ 99 VMA/ HOND DATE OF SALVAGE/ 05/16/10
CAUSE OF CLAIM (LOSS)/ THEFT/STRIPPED
INSURANCE COMPANY/ INSURANCE COMPANY
INSURANCE COMPANY LOCATION/ PHOENIX,AZ
CLAIM #/ 1111A11111111111111 ACTUAL CASH VALUE/ 009000
RECEIVED VALUE/ 000900 APPRAISED VALUE/ 000000
* NCIC INACTIVE VEHICLE *NICB FILE#/ A1111111111
**** NEW NICB FILE INQUIRY FOR ANY QUESTIONS PLEASE CONTACT NICB ****
602-555-1234
VYR/99 VMA/HOND VMO/PRE VST/2D VCO/SIL
NCIC#/ A111111111 NCIC MESSAGE KEY/ LV
DATE OF THEFT/ 05/16/10 ORI/ AZ0000000 OCA/ 01-1234
DATE OF RECOVERY/ 05/20/10 PLACE OF RECOVERY/ AZ0000000
RECOVERING AGENCY CASE#/ 01-1234

Example 11: Microdot NVS Query.

NAQ.AZNLETS20.NA.TXT
VIN/AAVZZZ6SZHU027272

Example 12: Microdot NVS Response.

NAR.VANVS005V

07:55 12/07/2017 00387
07:55 12/07/2017 00010 AZNLETS20
TXT
RESPONSE FOR VIN/ AAVZZZ6SZHU027272
Micro Dot Response:
VIN: AAVZZZ6SZHU027272
Microdot Number: ZARDV00441281
Engine Number: CLP275260
Vehicle Year: 2017
Vehicle Make: VOLKSWAGEN
Vehicle Model: POLO VIVO SEDAN 1.4 T/LINE 63K
Vehicle Color: Pure White


If additional assistance is required, Recoveri may be contacted via email for additional assistance at: philip@recoveri.net or rphillips@recoveri.ca


This response may contain Lien Holder, Mexican OCRA, and EBay auction data. This is in addition to a second response you will receive via Nlets that
will contain Impound, Import/Export, Insurance Theft File, NCIC/CPIC Vehicle Purge Data, Manufacturer's Shipping File, Salvage File, International
Index, Auction File, Pre-Inspection File, Vehicle Physical Damage Claim File, and Rental File data.


This information is being provided by National Vehicle Service, NFPC.
If you require additional information or assistance, please contact a Law Enforcement Assistant at 866-687-1102.


PLEASE NOTE: The attached information is being provided as a lead only and should be verified before any action is taken by your Agency.

Top

Downloads

Download NAQ Schema

Download NAR Schema

Download NAR Stylesheet

Download NIR Schema

Download NIR Stylesheet

Download NCI Schema

Download NCI Stylesheet

Download NUA Schema

Download NUA Stylesheet

Download NUI Schema

Download NUI Stylesheet

Download NEI Schema

Download NEI Stylesheet

Download SVQ Schema -- Added on 11/20/19

Download SVR Schema -- Added on 11/20/19

Download SVR Stylesheet -- Added on 11/20/19

Top