View source for Section 27: National Insurance Crime Bureau and National Vehicle Services and Locator

__TOC__

==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.
<ul>
<li>Each special agent is always on call to provide assistance to law enforcement in the identification of vehicles under investigation.
<li>Special agents are highly qualified investigators and experts in identifying vehicles on which identifying numbers have been removed, changed, altered, or obliterated.
<li>Special agents participate in training programs for law enforcement officers charged with the responsibility of theft, fraud, and arson investigations.
</ul>

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:

<table border="1">
<tr>
<th align="center">Manual</th>
<th align="center">Description</th>
</tr>
<tr>
<th align="left">Passenger Vehicle Identification Manual</th>
<th align="left">
Furnishes identification techniques for motor
<br>vehicles, engines, and transmissions, in
<br>addition to a brief summary of vehicle and
<br>marine laws and regulations.
</th>
</tr>
<tr>
<th align="left">Commercial Vehicle Identification
<br>Manual</th>
<th align="left">
Covers truck tractors, light-duty trucks, diesel
<br>engines, commercial trailer, recreational
<br>vehicles, farm, construction, and off-road
<br>equipment.
</th>
</tr>
<tr>
<th align="left">VIN Location Pocket Guide</th>
<th align="left">A quick reference to be carried by field
<br>personnel.</th>
</tr>
<tr>
<th align="left">NICB Annual Report</th>
<th align="left">Monitors trends in vehicle theft and fraud.</th>
</tr>
</table>

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:

<table border="1">
<tr>
<th align="left">
Dan Abbott
<br>National Insurance Crime Bureau
<br>Phone: (708) 237-4410
<br>Fax: (708) 430-2446
<br>E-mail: dabbott@nicb.org
<br>ORI: ILNATBC00
</th>
</tr>
</table>

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

<table border="1">
<tr>
<th align="left">
NVS contact information:
<br>email: n.v.s@att.net
<br>Phone: 708-429-0123
<br>Web Address: www.nvsliens.org
</th>
</tr>
</table>

===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

<table border="1">
<tr>
<th align="center" colspan="3">Data Fields (CamelCase)</th>
</tr>
<tr>
<th align="left">"MicrodotNumber"</th>
<th align="left">Alpha Numeric</th>
<th align="left">Max 17 Characters, No Minimum</th>
</tr>
<tr>
<th align="left">"VIN"</th>
<th align="left">Alpha Numeric</th>
<th align="left">Max 17 Characters, No Minimum</th>
</tr>
<tr>
<th align="left">"EngineNumber"</th>
<th align="left">Alpha Numeric</th>
<th align="left">Max 17 Characters, No Minimum</th>
</tr>
<tr>
<th align="left">"Make"</th>
<th align="left">Alpha</th>
<th align="left">Max 20 Characters, No Min</th>
</tr>
<tr>
<th align="left">"Model"</th>
<th align="left">Alpha Numeric</th>
<th align="left">Max 50 Characters, No Minimum</th>
</tr>
<tr>
<th align="left">"Colour"</th>
<th align="left">Alpha</th>
<th align="left">Max 20 Characters, No Minimum</th>
</tr>
<tr>
<th align="left">"ModelYear"</th>
<th align="left">Numeric</th>
<th align="left">Max 4</th>
</tr>
</table>

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

<table border="1">
<tr>
<th align="center" colspan="2">Country, State Example</th>
</tr>
<tr>
<th align="left">Example Number:</th>
<th align="left">USCORDV00252198</th>
</tr>
<tr>
<th align="left">Country Code</th>
<th align="left">US (United States)</th>
</tr>
<tr>
<th align="left">State Code</th>
<th align="left">CO (Colorado)</th>
</tr>
<tr>
<th align="left">Microdot Manufacturer</th>
<th align="left">RD (Recoveri Dot)</th>
</tr>
<tr>
<th align="left">Asset Class</th>
<th align="left">V (Vehicle)</th>
</tr>
<tr>
<th align="left">Unique Number</th>
<th align="left">00252198</th>
</tr>
</table>


<table border="1">
<tr>
<th align="center" colspan="2">Country Example</th>
</tr>
<tr>
<th align="left">Example Number</th>
<th align="left">ZARDV00252198</th>
</tr>
<tr>
<th align="left">Country Code</th>
<th align="left">ZA (South Africa)</th>
</tr>
<tr>
<th align="left">Microdot Manufacturer</th>
<th align="left">RD (Recoveri Dot)</th>
</tr>
<tr>
<th align="left">Asset Class</th>
<th align="left">V (Vehicle)</th>
</tr>
<tr>
<th align="left">Unique Number</th>
<th align="left">00252198</th>
</tr>
</table>

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:

<table border="1">
<tr>
<th align="left">Export File</th>
<th align="left">Impound File</th>
</tr>
<tr>
<th align="left">Salvage File</th>
<th align="left">Rental Fleet File</th>
</tr>
<tr>
<th align="left">Key Code transaction File</th>
<th align="left">Vehicle Lien Holder File</th>
</tr>
<tr>
<th align="left">OEM Shipping File</th>
<th align="left">Vehicle Claim File</th>
</tr>
<tr>
<th align="left">NCIC Purge File</th>
<th align="left">NCIC Inactive File</th>
</tr>
<tr>
</table>

These files may be accessed via two distinct types of inquiries.
<ul>
<li>One will access only the Impound and Export files (NIQ). (<b>Note</b>: Export files returned are historic files prior to August 2016).
<li>The other will access the other ten files listed above (NAQ).
</ul>

====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.

[[File:Section27-NIQ1.jpg|900px|thumb|none]]

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.

[[File:Section27-NIQ2.jpg|900px|thumb|none]]

====Impound / Export File Query Requirements (NIQ)====

<ul>
<li>Destination ORI for NICB queries is "NA".
<li>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.
<li>Access to these files is for investigative purposes only.
<li>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.
<li>If no information is found on any of the twelve NICB files the following message will be displayed: NO RECORD NICB.
</ul>

====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.

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Prefix:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="center">
 <syntaxhighlight lang="xml">
<j:VehicleID>
 </syntaxhighlight>
</th>
<th align="center">VIN/</th>
<th align="center">Max.
<br>20</th>
<th align="center">Alphanumeric</th>
<th align="left">VIN for vehicle (no period after
<br>last field in Native inquiry)</th>
</tr>
</table>

====All Files Inquiry (NAQ)====

This transaction interrogates all available NICB, NVS and OCRA (Mexican Stolens) files with one exception:
<ul>
<li>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".
<li>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.
<li>When a partial VIN search is requested only the Manufacturers Shipping File will be searched.
</ul>

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.

=====OEM Shipping File Query / Response (NAQ)=====

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

[[File:Section27-NAQ1.jpg|900px|thumb|none]]

=====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.

[[File:Section27-NAQ2.jpg|900px|thumb|none]]


=====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.

[[File:Section27-NAQ6.jpg|900px|thumb|none]]

=====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.

[[File:Section27-NAQ7.jpg|900px|thumb|none]]

=====NCIC Purge/Inactive 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.

[[File:Section27-NAQ8.jpg|900px|thumb|none]]

=====Vehicle Lien Holder 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

[[File:Section27-NAQ009.jpg|900px|thumb|none]]

=====Key Code Transaction / 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
<br>TRANSID/GM-18003003707 LSID/43Y22RNZ
 FOR ANY QUESTIONS PLEASE CONTACT NICB 847-544-7002

[[File:Section27-NAQ010.jpg|900px|thumb|none]]

=====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 [[Section 05: Help File Transactions|Help File Transactions]].

====Query Field Requirements====

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

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Prefix:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n2:NLETSInquiryData>
  <nc:Vehicle>
    <nc:VehicleIdentification>
      <nc:IdentificationID>
 </syntaxhighlight>
</th>
<th align="center">VIN/</th>
<th align="center">Max.
<br>20</th>
<th align="center">Alphanumeric</th>
<th align="left">
VIN for vehicle identification
<br>number (no period after last
<br>field in Native query).
</th>
</tr>
</table>

===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:

<table border="1">
<tr>
<th align="center">CONDITION</th>
<th align="center">DEFINITION</th>
</tr>
<tr>
<th align="left">UNDEFINED</th>
<th align="left">The situation about the vehicle or VIN plate is not clearly
<br>defined.</th>
</tr>
<tr>
<th align="left">UNUSED</th>
<th align="left">The VIN plate and its embossed or stamped number will not be
<br>installed or assigned to a vehicle.</th>
</tr>
<tr>
<th align="left">STOLEN FROM LOT</th>
<th align="left">The vehicle was stolen from a factory or dealer lot.</th>
</tr>
<tr>
<th align="left">DESTROYED</th>
<th align="left">The vehicle has been completely destroyed.</th>
</tr>
<tr>
<th align="left">SCRAPPED</th>
<th align="left">The vehicle is unusable.</th>
</tr>
<tr>
<th align="left">INCORRECT</th>
<th align="left">The VIN number found on the vehicle is incorrect. This number
<br>does not conform to the Federal Motor Vehicle Standard.</th>
</tr>
<tr>
<th align="left">STAMPING ERROR</th>
<th align="left">
Hidden numbers found on the vehicle, i.e., engine, transmission
<br>and/or chassis numbers are not correct. This situation relates to
<br>domestic built vehicles which denote a VIN derivative stamped,
<br>embossed, or labeled on component parts.
</th>
</tr>
<tr>
<th align="left">STOLEN PLATE</th>
<th align="left">Manufacturer advises that only the VIN plate was stolen.</th>
</tr>
<tr>
<th align="left">FLOOD DAMAGED</th>
<th align="left">The vehicle has had water damage and is not to be sold.</th>
</tr>
<tr>
<th align="left">UNSCRAPPED</th>
<th align="left">The vehicle previously reported as a scrapped vehicle has been
<br>repaired and is being sold.</th>
</tr>
<tr>
<th align="left">FIRE DAMAGED</th>
<th align="left">The vehicle is reported as having fire damage and is not to be
<br>sold.</th>
</tr>
<tr>
<th align="left">REPLACEMENT</th>
<th align="left">
Replacement VIN plate - The vehicle's original VIN plate was
<br>damaged or is missing and a replacement plate was issued by
<br>the manufacturer.
<br>Replacement Parts - The vehicle's component part has been
<br>replaced and the part has a new number.
</th>
</tr>
<tr>
<th align="left">DONATED VEHICLE</th>
<th align="left">The vehicle was donated and removed from commerce.</th>
</tr>
<tr>
<th align="left">TEST VEHICLE</th>
<th align="left">The vehicle is used for testing purposes and is not to be sold.</th>
</tr>
<tr>
<th align="left">DATE</th>
<th align="left">The date in which the vehicle was shipped (ccyy-mm-dd).</th>
</tr>
<tr>
<th align="left">DEALER NAME</th>
<th align="left">The name of the dealership that the vehicle was shipped to.</th>
</tr>
<tr>
<th align="left">DEALER CODE</th>
<th align="left">The dealer code supplied by the dealer.</th>
</tr>
<tr>
<th align="left">DEALER CITY, STATE</th>
<th align="left">The city and state where the dealer is located.</th>
</tr>
<tr>
<th align="left">PHONE</th>
<th align="left">The phone number for the dealer.</th>
</tr>
</table>

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:

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

====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:

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

====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:

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center">Translation</th>
</tr>
<tr>
<th align="left">VYR/</th>
<th align="left">Four digits of the model year of the vehicle</th>
</tr>
<tr>
<th align="left">VMA/</th>
<th align="left">The vehicle make as encoded in NCIC supplied tables</th>
</tr>
<tr>
<th align="left">DATE OF EXPORT/</th>
<th align="left">Date of export (ccyy-mm-dd)</th>
</tr>
<tr>
<th align="left">DESTINATION/</th>
<th align="left">Destination of export</th>
</tr>
</table>


====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:

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center">Translation</th>
</tr>
<tr>
<th align="left">MEMBER COMPANY/</th>
<th align="left">The name of the company that reported the claim.</th>
</tr>
<tr>
<th align="left">CLAIM NUMBER/</th>
<th align="left">The number assigned by the insurance company.</th>
</tr>
<tr>
<th align="left">INS PHONE/</th>
<th align="left">The telephone number of the filing insurance company
<br>office.</th>
</tr>
<tr>
<th align="left">IMPACT POINT/</th>
<th align="left">The initial impact point of the vehicle according to the
<br>filed claim.</th>
</tr>
<tr>
<th align="left">MILEAGE/</th>
<th align="left">The mileage at the time of the accident.</th>
</tr>
</table>

====Rental Fleet 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:
<ul>
<li>added to fleet
<li>missing
<li>never returned
<li>located
<li>taken out of fleet
</ul>

Explanation of field entries:

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

====NCIC Purge/Inactive 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.

====NCIC Purge/Inactive Response====

Explanation of Fields:

<table border="1">
<tr>
<th align="center">Legacy Code</th>
<th align="center">Translation</th>
</tr>
<tr>
<th align="left">CONDITION OF RECOVERY/</th>
<th align="left">Condition of vehicle at time of recovery</th>
</tr>
<tr>
<th align="left">RECOVERING ORI/</th>
<th align="left">The 9 digit identifier of the recovering agency.</th>
</tr>
<tr>
<th align="left">REPORTING ORI/</th>
<th align="left">The 9 digit identifier of the reporting agency.</th>
</tr>
</table>

====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.
<ul>
<li>The modify transaction is normally used if a mistake was made in the entry process.
<li>The cancel transaction is used when the agency wishes to remove the record from the impound file.
</ul>

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.

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Entry:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleID>
 </syntaxhighlight>
</th>
<th align="center">VIN/</th>
<th align="center">Max.
<br>20</th>
<th align="left">Alphanumeric</th>
<th align="left">VIN for vehicle.</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:OrganizationORIID>
 </syntaxhighlight>
</th>
<th align="center">ORI/</th>
<th align="center">9</th>
<th align="left">Alphanumeric</th>
<th align="left">
ORI of
<br>impounding
<br>agency.
</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:CaseID>
 </syntaxhighlight>
</th>
<th align="center">OCA/</th>
<th align="center">20</th>
<th align="left">Alphanumeric</th>
<th align="left">
Case # (no
<br>special
<br>characters).
</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:ImpoundDate>
 </syntaxhighlight>
</th>
<th align="center">DOI/</th>
<th align="center">8</th>
<th align="left">ccyy-mm-dd</th>
<th align="left">Date vehicle was
<br>impounded.</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:ContactOrganzationName>
 </syntaxhighlight>
</th>
<th align="center">PND/</th>
<th align="center">24</th>
<th align="left">See NCIC Manual</th>
<th align="left">Name of Pound
<br>holding vehicle.</th>
</tr>
<tr>
<th align="left" colspan="5">Optional Entries</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleMakeCode>
 </syntaxhighlight>
</th>
<th align="center">VMA/</th>
<th align="center">2-4</th>
<th align="left">See NCIC Manual</th>
<th align="left">Vehicle Make</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleModelCode>
 </syntaxhighlight>
</th>
<th align="center">VMO/</th>
<th align="center">4</th>
<th align="left">See NCIC Manual</th>
<th align="left">Vehicle Model</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleModelYearDate>
 </syntaxhighlight>
</th>
<th align="center">VYR/</th>
<th align="center">4</th>
<th align="left">ccyy</th>
<th align="left">Vehicle Year</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleStyleCode>
 </syntaxhighlight>
</th>
<th align="center">VST/</th>
<th align="center">2</th>
<th align="left">See NCIC Manual</th>
<th align="left">Vehicle Style</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleLicensePlateID>
 </syntaxhighlight>
</th>
<th align="center">LIC/</th>
<th align="center">1-10</th>
<th align="left">See NCIC Manual</th>
<th align="left">License #</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:IDIssuingAuthorityText
 </syntaxhighlight>
</th>
<th align="center">LIS/</th>
<th align="center">2</th>
<th align="left">See NCIC Manual</th>
<th align="left">License State</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:IDExpirationDate
 </syntaxhighlight>
</th>
<th align="center">LIY/</th>
<th align="center">4</th>
<th align="left">See NCIC Manual</th>
<th align="left">License Year</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleRegistrationPlateTypeCode>
 </syntaxhighlight>
</th>
<th align="center">LIT/</th>
<th align="center">2</th>
<th align="left">See NCIC Manual</th>
<th align="left">License Type</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:Miscellaneous>
 </syntaxhighlight>
</th>
<th align="center">MSC/</th>
<th align="center">42</th>
<th align="left">Free format</th>
<th align="left">
Free format
<br>miscellaneous
<br>field
</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:PoundInventoryID>
 </syntaxhighlight>
</th>
<th align="center">INV/</th>
<th align="center">12</th>
<th align="left">Alphanumeric</th>
<th align="left">Pounds
<br>Inventory #</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:ContactTelephoneNumber>
 </syntaxhighlight>
</th>
<th align="center">PHO/</th>
<th align="center">10</th>
<th align="left">Numeric</th>
<th align="left">Phone # of
<br>Pound</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:NewYorkDerelict>
 </syntaxhighlight>
</th>
<th align="left">DER/</th>
<th align="left">1</th>
<th align="left">Y</th>
<th align="left">
Fixed field of "Y"
<br>if a New York
<br>Derelict.
<br>(Note: Last field
<br>in Legacy message
<br>must not be
<br>followed by a
<br>period.)
</th>
</tr>
</table>

====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.
<ul>
<li>To add a field, place the new data in the field after the prefix identifier.
<li>To delete a field place an asterisk after the field prefix.
</ul>

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.

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Entry:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:PropertyFederalID>
 </syntaxhighlight>
</th>
<th align="center">FIL/</th>
<th align="center">11</th>
<th align="left">See NCIC manual</th>
<th align="left">
Unique NICB
<br>impound record
<br>number
</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:OrganizationORIID>
 </syntaxhighlight>
</th>
<th align="center">ORI/</th>
<th align="center">9</th>
<th align="left">Alpha/numeric</th>
<th align="left">ORI of impounding
<br>agency</th>
</tr>
</table>

These data fields are required but may be modified:

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Entry:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:CaseID>
 </syntaxhighlight>
</th>
<th align="center">OCA/</th>
<th align="center">20</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Case # (no special
<br>characters).</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:ImpoundDate>
 </syntaxhighlight>
</th>
<th align="center">DOI/</th>
<th align="center">8</th>
<th align="left">ccyy-mm-dd</th>
<th align="left">Date vehicle was
<br>impounded.</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:ContactOrganzationName>
 </syntaxhighlight>
</th>
<th align="center">PND/</th>
<th align="center">24</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Name of Pound
<br>holding vehicle</th>
</tr>
</table>

These fields may be modified, added or deleted:

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Entry:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleMakeCode>
 </syntaxhighlight>
</th>
<th align="center">VMA/</th>
<th align="center">2-4</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Vehicle Make</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleModelCode>
 </syntaxhighlight>
</th>
<th align="center">VMO/</th>
<th align="center">3</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Vehicle Model</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleModelYearDate>
 </syntaxhighlight>
</th>
<th align="center">VYR/</th>
<th align="center">4</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Vehicle Year</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleStyleCode>
 </syntaxhighlight>
</th>
<th align="center">VST/</th>
<th align="center">2</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Vehicle Style</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleLicensePlateID>
<j:ID>
 </syntaxhighlight>
</th>
<th align="center">LIC/</th>
<th align="center">1-10</th>
<th align="left">Alphanumeric</th>
<th align="left">License #</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:IDIssuingAuthorityText>
 </syntaxhighlight>
</th>
<th align="center">LIS/</th>
<th align="center">2</th>
<th align="left">See NCIC Manual.</th>
<th align="left">License State</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:IDExpirationDate>
 </syntaxhighlight>
</th>
<th align="center">LIY/</th>
<th align="center">4</th>
<th align="left">See NCIC Manual.</th>
<th align="left">License Year</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleRegistrationPlateTypeCode>
 </syntaxhighlight>
</th>
<th align="center">LIT/</th>
<th align="center">2</th>
<th align="left">See NCIC Manual.</th>
<th align="left">License Type</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:Miscellaneous>
 </syntaxhighlight>
</th>
<th align="center">MSC/</th>
<th align="center">42</th>
<th align="left">Free text</th>
<th align="left">Free format
<br>miscellaneous field</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:PoundInventoryID>
 </syntaxhighlight>
</th>
<th align="center">INV/</th>
<th align="center">12</th>
<th align="left">See NCIC Manual.</th>
<th align="left">Pounds Inventory #</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:ContactTelephoneNumber>
 </syntaxhighlight>
</th>
<th align="center">PHO/</th>
<th align="center">10</th>
<th align="left">Numeric</th>
<th align="left">Phone # of Pound</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<n:NewYorkDerelict>
 </syntaxhighlight>
</th>
<th align="center">DER/</th>
<th align="center">1</th>
<th align="left">Y</th>
<th align="left">
Fixed field of "Y" if
<br>a New York Derelict
<br>(Note: last field
<br>must not be
<br>followed by a
<br>period)
</th>
</tr>
</table>

====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.

<table border="1">
<tr>
<th align="center">IMPOUND RECORD CANCELED</th>
</tr>
</table>

Below is the format for the cancel impound transaction.

<table border="1">
<tr>
<th align="center">XML Tag:</th>
<th align="center">Legacy
<br>Entry:</th>
<th align="center">Field
<br>Size:</th>
<th align="center">Data
<br>Requirements:</th>
<th align="center">Translation:</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:VehicleID>
 </syntaxhighlight>
</th>
<th align="center">VIN/</th>
<th align="center">Max.
<br>20</th>
<th align="left">Alphanumeric</th>
<th align="left">VIN for vehicle</th>
</tr>
<tr>
<th align="left">
 <syntaxhighlight lang="xml">
<j:PropertyFederalID>
 </syntaxhighlight>
</th>
<th align="left">FIL/</th>
<th align="left">11</th>
<th align="left">Numeric</th>
<th align="left">
NICB file number
<br>assigned to each
<br>impound record.
</th>
</tr>
</table>

[[#top|Top]]

==GJXDM (DEPRECATED)==

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

[[#top|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:

<table border="1">
<tr>
<th align="left">Impound file</th>
<th align="left">Pre-Inspection File</th>
</tr>
<tr>
<th align="left">Export File</th>
<th align="left">Vehicle Claim File</th>
</tr>
<tr>
<th align="left">Manufacturer's Shipping File</th>
<th align="left">Rental File</th>
</tr>
<tr>
<th align="left">Salvage File</th>
<th align="left">Theft File</th>
</tr>
<tr>
<th align="left">International Index File</th>
<th align="left">Theft (recovery) File</th>
</tr>
<tr>
<th align="left">Auction File</th>
<th align="left">NCIC/CPIC Canceled File</th>
</tr>
</table>

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 [[03-Message_Structure|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: <u>Query for Impound/Export Information (NIQ)</u>, <u>Query of All Files (NAQ)</u>, <u>Entry to Impound File (NEI)</u>, <u>Modification to Impound File (NUI)</u>, <u>Cancellation of Impound File (NCI)</u>, <u>Response to Impound/Export Query (NIR)</u> and <u>Response from All Files (NAR)</u>.

====Query Formats====

<b><u>Query for Impound/Export Information (NIQ)</u></b>

<b>n2:NLETSInquiryData</b>
<br><i>This element will contain all elements specific to this transaction.</i>

&nbsp;&nbsp;<b>nc:Vehicle</b>
<br>&nbsp;&nbsp;<i>A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A unique combination of alphanumeric characters that identifies a specific vehicle.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the VIN to be queried.

<b><u>Query of all files (NAQ)</u></b>

<b>n2:NLETSInquiryData</b>
<br><i>This element will contain all elements specific to this transaction.</i>

&nbsp;&nbsp;<b>nc:Vehicle</b>
<br>&nbsp;&nbsp;<i>A motor-driven conveyance designed to carry its operator, and optionally 
passengers and cargo, over land.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A unique combination of alphanumeric characters that identifies 
a specific vehicle.</i>

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

====Entry Formats====

<b><u>Entry to Impound File (NEI)</u></b>

<b>n2:NLETSUpdateData</b>

&nbsp;&nbsp;<b>n2:LawEnforcementAgency</b>

&nbsp;&nbsp;&nbsp;&nbsp;<b>j:OrganizationAugmentation</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>Additional information about an organization.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>j:OrganizationORIIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A unique identifier assigned to a justice-related organization by the federal government.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the ORI of the impounding agency.

&nbsp;&nbsp;<b>nc:Incident</b>
<br>&nbsp;&nbsp;<i>An occurrence or an event that may require a response.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ActivityIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>An identification that references an activity.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the case number.

&nbsp;&nbsp;<b>n2:ImpoundActivity</b>
<br>&nbsp;&nbsp;<i>Details about a impound action associated with a vehicle.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ActivityIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>An identification that references an activity.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the inventory number of the pound.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ActivityDate</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A date of an activity.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:Date</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A full date.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the date the vehicle was impounded. The value should be in the format
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ccyy-mm-dd.

&nbsp;&nbsp;<b>n2:ImpoundOrganization</b>
<br>&nbsp;&nbsp;<i>Describes the entity that has impounded a vehicle.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:OrganizationName</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A name of an organization.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This element contains the name of the pound.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:OrganizationPrimaryContactInformation</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A preferred means of contacting an organization.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ContactTelephoneNumber</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A telephone number for a telecommunication device by which a person or organization may be contacted.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:FullTelephoneNumber</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A full telephone number.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:TelephoneNumberFullID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A complete telephone number.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Telephone number for this location of the pound. The actual value (all numeric, no dashes) should be contained
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in the subelement.

&nbsp;&nbsp;<b>nc:Vehicle</b>
<br>&nbsp;&nbsp;<i>A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A unique combination of alphanumeric characters that identifies a specific vehicle.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the VIN to be queried.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleMakeCode</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A manufacturer of a vehicle.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the make of the vehicle being added. Allowable values come from the NCIC VMA
<br>&nbsp;&nbsp;&nbsp;&nbsp;code table.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleModelCode</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A specific design or class of vehicle made by a manufacturer.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the model of the vehicle being added.  Allowable values come from the NCIC VMO
<br>&nbsp;&nbsp;&nbsp;&nbsp;code table.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ConveyanceRegistrationPlateIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>An identification on a metal plate fixed to a conveyance.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the license plate number to be queried.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationCategoryText</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A kind of identification.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional element should contain the type of license plate being queried. Allowable values come from the
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;NCIC LIT code table.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationExpirationDate</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A date after which an identification is no longer valid.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:Date</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A full date.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional element's value should be the expiration date of the license plate. Data should be formatted
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;yyyy-mm-dd.

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationJurisdictionText</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>An area, region, or unit in which a unique identification is issued.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional  element's value should be the issuing state of the license plate.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ItemModelYearDate</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A year in which an item was manufactured or produced.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the year of the vehicle. Data should be formatted YYYY.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleStyleCode</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A style of a vehicle.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the style of the vehicle being added.  Allowable values come from the NCIC VST
<br>&nbsp;&nbsp;&nbsp;&nbsp;code table.

&nbsp;&nbsp;<b>n2:NewYorkDerelictIndicator</b>
<br>&nbsp;&nbsp;<i>Optional element containing a Y if the vehicle is New York derelict.</i>
<br>&nbsp;&nbsp;Optional element containing a Y if the vehicle is New York derelict.

&nbsp;&nbsp;<b>n2:MiscellaneousUpdateText</b>
<br>&nbsp;&nbsp;<i>Optional Miscellaneous Field. Free text format.</i>
<br>&nbsp;&nbsp;Optional Miscellaneous Field. Free format.

====Update Formats====

<b><u>Modification to Impound File (NUI)</u></b>

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

&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;This element will contain the actual NICB number being queried.

<b>n2:LawEnforcementAgency</b>

&nbsp;&nbsp;<b>j:OrganizationAugmentation</b>
<br>&nbsp;&nbsp;<i>Additional information about an organization.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>j:OrganizationORIIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A unique identifier assigned to a justice-related organization by the 
federal government.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the ORI of the impounding agency.

<b>nc:Incident</b>
<br><i>An occurrence or an event that may require a response.</i>

&nbsp;&nbsp;<b>nc:ActivityIdentification</b>
<br>&nbsp;&nbsp;<i>An identification that references an activity.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the case number.

<b>n2:ImpoundActivity</b>
<br><i>Details about a impound action associated with a vehicle.</i>

&nbsp;&nbsp;<b>nc:ActivityIdentification</b>
<br>&nbsp;&nbsp;<i>An identification that references an activity.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the inventory number of the pound.

&nbsp;&nbsp;<b>nc:ActivityDate</b>
<br>&nbsp;&nbsp;<i>A date of an activity.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:Date</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A full date.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the date the vehicle was impounded. The value should be in the format
<br>&nbsp;&nbsp;&nbsp;&nbsp;ccyy-mm-dd.

<b>n2:ImpoundOrganization</b>
<br><i>Describes the entity that has impounded a vehicle.</i>

&nbsp;&nbsp;<b>nc:OrganizationName</b>
<br>&nbsp;&nbsp;<i>A name of an organization.</i>
<br>&nbsp;&nbsp;This element contains the name of the pound.

&nbsp;&nbsp;<b>nc:OrganizationPrimaryContactInformation</b>
<br>&nbsp;&nbsp;<i>A preferred means of contacting an organization.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:ContactTelephoneNumber</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A telephone number for a telecommunication device by which a person or organization may be contacted.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:FullTelephoneNumber</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A full telephone number.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:TelephoneNumberFullID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A complete telephone number.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Telephone number for this location of the pound. The actual value (all numeric, no dashes) should be contained
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in the subelement.

<b>nc:Vehicle</b>
<br><i>A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.</i>

&nbsp;&nbsp;<b>nc:VehicleIdentification</b>
<br>&nbsp;&nbsp;<i>A unique combination of alphanumeric characters that identifies a specific vehicle.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the VIN to be queried.

&nbsp;&nbsp;<b>nc:VehicleMakeCode</b>
<br>&nbsp;&nbsp;<i>A manufacturer of a vehicle.</i>
<br>&nbsp;&nbsp;This optional element will contain the make of the vehicle being added. Allowable values come from the NCIC VMA
<br>&nbsp;&nbsp;code table.

&nbsp;&nbsp;<b>nc:VehicleModelCode</b>
<br>&nbsp;&nbsp;<i>A specific design or class of vehicle made by a manufacturer.</i>
<br>&nbsp;&nbsp;This optional element will contain the model of the vehicle being added. Allowable values come from the NCIC VMO
<br>&nbsp;&nbsp;code table.

&nbsp;&nbsp;<b>nc:ConveyanceRegistrationPlateIdentification</b>
<br>&nbsp;&nbsp;<i>An identification on a metal plate fixed to a conveyance.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element will contain the license plate number to be queried.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationCategoryText</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A kind of identification.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional element should contain the type of license plate being queried. Allowable values come from the NCIC
<br>&nbsp;&nbsp;&nbsp;&nbsp;LIT code table.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationExpirationDate</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A date after which an identification is no longer valid.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:Date</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A full date.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This optional element's value should be the expiration date of the license plate. Data should be formatted
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;yyyy-mm-dd.

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationJurisdictionText</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>An area, region, or unit in which a unique identification is issued.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This optional  element's value should be the issuing state of the license plate.

&nbsp;&nbsp;<b>nc:ItemModelYearDate</b>
<br>&nbsp;&nbsp;<i>A year in which an item was manufactured or produced.</i>
<br>&nbsp;&nbsp;This optional element will contain the year of the vehicle. Data should be formatted YYYY.

&nbsp;&nbsp;<b>nc:VehicleStyleCode</b>
<br>&nbsp;&nbsp;<i>A style of a vehicle.</i>
<br>&nbsp;&nbsp;This optional element will contain the style of the vehicle being added.  Allowable values come from the NCIC VST
<br>&nbsp;&nbsp;code table.

<b>n2:NewYorkDerelictIndicator</b>
<br><i>Optional element containing a Y if the vehicle is New York derelict.</i>
<br>Optional element containing a Y if the vehicle is New York derelict.

<b>n2:MiscellaneousUpdateText</b>
<br><i>Optional Miscellaneous Field. Free text format.</i>
<br>Optional Miscellaneous Field. Free format.

====Cancel Formats====

<b><u>Cancellation of Impound File (NCI)</u></b>

<b>n2:NLETSUpdateData</b>

&nbsp;&nbsp;<b>n2:NICBImpoundRecordIdentification</b>
<br>&nbsp;&nbsp;<i>This optional element will contain unique NICB impound record number.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the NICB number being queried.

&nbsp;&nbsp;<b>nc:Vehicle</b>
<br>&nbsp;&nbsp;<i>A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.</i>

&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:VehicleIdentification</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;<i>A unique combination of alphanumeric characters that identifies a specific vehicle.</i>

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>nc:IdentificationID</b>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<i>A value that identifies something.</i>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This element will contain the VIN to be queried.

====Response Formats====

<b><u>Response to Impound/Export query (NIR)</u></b>

<b>n2:NLETSResponseData</b>

&nbsp;&nbsp;<b>n2:ResponseText</b>
<br>&nbsp;&nbsp;<i>This element will contain the free text response. Nlets recommends the use of <syntaxhighlight lang="xml"><!&#91;CDATA&#91;&#93;&#93;></syntaxhighlight> tags to ensure that the</i>
<br>&nbsp;&nbsp;<i>response does not contain any characters illegal in XML.</i>

<b><u>Response to all files query (NAR)</u></b>

<b>n2:NLETSResponseData</b>

&nbsp;&nbsp;<b>n2:ResponseText</b>
<br>&nbsp;&nbsp;<i>This element will contain the free text response. Nlets recommends the use of <syntaxhighlight lang="xml"><!&#91;CDATA&#91;&#93;&#93;></syntaxhighlight> tags to ensure that the</i>
<br>&nbsp;&nbsp;<i>response does not contain any characters illegal in XML.</i>

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

<table border="1">
<tr>
<th align="left">CONDITION</th>
<th align="left">DEFINITION</th>
</tr>
<tr>
<th align="left">UNDEFINED</th>
<th align="left">The situation about the vehicle or VIN plate is not clearly defined.</th>
</tr>
<tr>
<th align="left">UNUSED</th>
<th align="left">The VIN plate and its embossed or stamped number will not be installed or assigned to a
<br>&nbsp;vehicle.</th>
</tr>
<tr>
<th align="left">STOLEN FROM LOT</th>
<th align="left">The vehicle was stolen from a factory or dealer lot.</th>
</tr>
<tr>
<th align="left">DESTROYED</th>
<th align="left">The vehicle has been completely destroyed.</th>
</tr>
<tr>
<th align="left">SCRAPPED</th>
<th align="left">The vehicle is unusable.</th>
</tr>
<tr>
<th align="left">INCORRECT</th>
<th align="left">The VIN number found on the vehicle is incorrect. This number does not conform to the
<br>&nbsp;Federal Motor Vehicle Standard.</th>
</tr>
<tr>
<th align="left">STAMPING ERROR</th>
<th align="left">Hidden numbers found on the vehicle, i.e., engine, transmission and/or chassis numbers
<br>&nbsp;are not correct. This situation relates to domestic built vehicles which denote a VIN
<br>&nbsp;derivative stamped, embossed, or labeled on component parts.
</th>
</tr>
<tr>
<th align="left">STOLEN PLATE</th>
<th align="left">Manufacturer advises that only the VIN plate was stolen.</th>
</tr>
<tr>
<th align="left">FLOOD DAMAGED</th>
<th align="left">The vehicle has had water damage and is not to be sold.</th>
</tr>
<tr>
<th align="left">UNSCRAPPED</th>
<th align="left">The vehicle previously reported as a scrapped vehicle has been repaired and is being
<br>&nbsp;sold.</th>
</tr>
<tr>
<th align="left">FIRE DAMAGED</th>
<th align="left">The vehicle is reported as having fire damage and is not to be sold.</th>
</tr>
<tr>
<th align="left">REPLACEMENT</th>
<th align="left">Replacement VIN plate - The vehicle's original VIN plate was damaged or is missing and
<br>&nbsp;a replacement plate was issued by the manufacturer.
<br>Replacement Parts - The vehicle's component part has been replaced and the part has a
<br>&nbsp;new number.
</th>
</tr>
<tr>
<th align="left">DONATED VEHICLE</th>
<th align="left">The vehicle was donated and removed from commerce.</th>
</tr>
<tr>
<th align="left">TEST VEHICLE</th>
<th align="left">The vehicle is used for testing purposes and is not to be sold.</th>
</tr>
<tr>
<th align="left">DATE</th>
<th align="left">The date in which the vehicle was shipped (ccyy-mm-dd).</th>
</tr>
<tr>
<th align="left">DEALER NAME</th>
<th align="left">The name of the dealership that the vehicle was shipped to.</th>
</tr>
<tr>
<th align="left">DEALER CODE</th>
<th align="left">The dealer code supplied by the dealer.</th>
</tr>
<tr>
<th align="left">DEALER CITY, STATE</th>
<th align="left">The city and state where the dealer is located.</th>
</tr>
<tr>
<th align="left">PHONE</th>
<th align="left">The phone number for the dealer.</th>
</tr>
</table>

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

<b><u>Response to Entry, Update or Cancel (NEA, NUA, NCA)</u></b>

<b>n2:NLETSResponseData</b>

&nbsp;&nbsp;<b>n2:ResponseText</b>
<br>&nbsp;&nbsp;<i>This element will contain the free text response. Nlets recommends the use of <syntaxhighlight lang="xml"><!&#91;CDATA&#91;&#93;&#93;></syntaxhighlight> tags to ensure that the</i>
<br>&nbsp;&nbsp;<i>response does not contain any characters illegal in XML.</i>

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

<u>Example 1</u>: A query for Impound/Export Information.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 2</u>: A query of All Files.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<?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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 3</u>: An Entry to Impound File.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 4</u>: A Response from NICB on an Impound File being added.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 5</u>: A Modification to Impound File.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

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

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 7</u>: A Cancellation of Impound File.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

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

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 9</u>: A response to Impound/Export query.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 10</u>: A response from All Files.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 11</u>: A query to Locator Technologies for Canada.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 12</u>: A response from Locator Technologies for Canada.

<table border="1">
<tr>
<th align="left">
Message 1:
  <syntaxhighlight lang="xml">
<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>
</syntaxhighlight>
Message 2:
<syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 13</u>: A query to Locator Technologies for Mexico.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 14</u>: A response from Locator Technologies for Mexico.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
</syntaxhighlight>
Message 2:
<syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 15</u>: A query to Locator Technologies for America.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 16</u>: A response from Locator Technologies for America.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>


  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 17</u>: A query to Locator Technologies for Vinspection Mobile App.

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 18</u>: A response from Locator Technologies for Vinspection Mobile App.

<table border="1">
<tr>
<th align="left">
Message 1:
<syntaxhighlight lang="xml">
<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>
</syntaxhighlight>
Message 2:
<syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
Message 3:
<syntaxhighlight lang="xml">
<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>
</syntaxhighlight>
</th>
</tr>
</table>

<u>Example 19</u>: A query to Locator Technologies for OCRA database

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

<u>Example 20</u>: A response from Locator Technologies from the OCRA database

<table border="1">
<tr>
<th align="left">
  <syntaxhighlight lang="xml">
<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>
  </syntaxhighlight>
</th>
</tr>
</table>

[[#top|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:

<table border="1">
<tr>
<th align="left">
"THIS IS TO NOTIFY YOU THAT THE VEHICLE YOU ENTERED INTO NCIC,
<br>VIN/12345671234567890, IS IN THE NICB DATABASE. BELOW IS THE NICB RELATED VEHICLE
<br>RECORD. THIS MAY ASSIST YOU WITH ANY FOLLOW UP INVESTIGATION.
<br>(followed by matching NICB record)
</th>
</tr>
</table>

===Queries to NICB Record Files===

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

<table border="1">
<tr>
<th align="left">Impound file</th>
<th align="left">Pre-Inspection File</th>
</tr>
<tr>
<th align="left">Export File</th>
<th align="left">Vehicle Claim File</th>
</tr>
<tr>
<th align="left">Manufacturer's Shipping File</th>
<th align="left">Rental File</th>
</tr>
<tr>
<th align="left">Salvage File</th>
<th align="left">Theft File</th>
</tr>
<tr>
<th align="left">International Index File</th>
<th align="left">Theft (recovery) File</th>
</tr>
<tr>
<th align="left">Auction File</th>
<th align="left">NCIC/CPIC Canceled File</th>
</tr>
</table>

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

<ul>
<li>One will access only the Impound and Export files (NIQ).
<li>The other will access all ten files listed above (NAQ).
</ul>

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.

<ul>
<li>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.
<li>The message key identifying a query on impound and export files is NIQ.
<li>The destination ORI of NICB is "NA".
</ul>

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

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center"># Char.</th>
<th align="center">Explanation</th>
</tr>
<tr>
<th align="left">NIQ.</th>
<th align="center">3</th>
<th align="left">Message key identifies query on Impound &amp; Export files
<br>followed by a period.</th>
</tr>
<tr>
<th align="left">Sender ORI.</th>
<th align="center">9</th>
<th align="left">ORI of sender followed by a period.</th>
</tr>
<tr>
<th align="left">NA.</th>
<th align="center">2</th>
<th align="left">Destination ORI of NICB followed by a period and optional
<br>control field.</th>
</tr>
<tr>
<th align="left">TXT</th>
<th align="center">3</th>
<th align="left">Fixed filed prefix to beginning of message.</th>
</tr>
<tr>
<th align="left">VIN/</th>
<th align="center">4</th>
<th align="left">Prefix for VIN.</th>
</tr>
<tr>
<th align="left">VIN</th>
<th align="left">Max. 20</th>
<th align="left">VIN for vehicle (no period after last field in inquiry).</th>
</tr>
</table>

====All Files Inquiry (NAQ)====

This transaction interrogates all available NICB files with one exception.

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

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

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center"># Char.</th>
<th align="center">Explanation</th>
</tr>
<tr>
<th align="left">NAQ.</th>
<th align="center">3</th>
<th align="left">Message key identifies query on Impound &amp; Export files followed
<br>by a period.</th>
</tr>
<tr>
<th align="left">Sender ORI.</th>
<th align="center">9</th>
<th align="left">ORI of sender followed by a period.</th>
</tr>
<tr>
<th align="left">NA.</th>
<th align="center">2</th>
<th align="left">Destination ORI of NICB followed by a period and optional
<br>control field.</th>
</tr>
<tr>
<th align="left">TXT</th>
<th align="center">3</th>
<th align="left">Fixed filed prefix to beginning of message.</th>
</tr>
<tr>
<th align="left">VIN/</th>
<th align="center">4</th>
<th align="left">Prefix for VIN.</th>
</tr>
<tr>
<th align="left">VIN</th>
<th align="center">Max. 20</th>
<th align="left">
VIN for vehicle (no period for last data element); partial VIN may
<br>be on the last 8 characters. A partial VIN must be preceded by
<br>the word "PARTIAL". (E.G., VIN/PARTIAL24657490 Only the
<br>Manufacturer's Shipping File will be searched on a partial VIN inquiry.
</th>
</tr>
</table>

===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.

====OEM Shipping File Response====

Below is a list of status conditions and their definitions:

<table border="1">
<tr>
<th align="center">CONDITION</th>
<th align="center">DEFINITION</th>
</tr>
<tr>
<th align="left">UNDEFINED</th>
<th align="left">The situation about the vehicle or VIN plate is not clearly defined.</th>
</tr>
<tr>
<th align="left">UNUSED</th>
<th align="left">The VIN plate and its embossed or stamped number will not be
<br>installed or assigned to a vehicle.</th>
</tr>
<tr>
<th align="left">STOLEN FROM LOT</th>
<th align="left">The vehicle was stolen from a factory or dealer lot.</th>
</tr>
<tr>
<th align="left">DESTROYED</th>
<th align="left">The vehicle has been completely destroyed.</th>
</tr>
<tr>
<th align="left">SCRAPPED</th>
<th align="left">The vehicle is unusable.</th>
</tr>
<tr>
<th align="left">INCORRECT</th>
<th align="left">The VIN number found on the vehicle is incorrect. This number
<br>does not conform to the Federal Motor Vehicle Standard.</th>
</tr>
<tr>
<th align="left">STAMPING ERROR</th>
<th align="left">
Hidden numbers found on the vehicle, i.e., engine, transmission
<br>and/or chassis numbers are not correct. This situation relates to
<br>domestic built vehicles which denote a VIN derivative stamped,
<br>embossed, or labeled on component parts.
</th>
</tr>
<tr>
<th align="left">STOLEN PLATE</th>
<th align="left">Manufacturer advises that only the VIN plate was stolen.</th>
</tr>
<tr>
<th align="left">FLOOD DAMAGED</th>
<th align="left">The vehicle has had water damage and is not to be sold.</th>
</tr>
<tr>
<th align="left">UNSCRAPPED</th>
<th align="left">The vehicle previously reported as a scrapped vehicle has been
<br>repaired and is being sold.</th>
</tr>
<tr>
<th align="left">FIRE DAMAGED</th>
<th align="left">The vehicle is reported as having fire damage and is not to be sold.</th>
</tr>
<tr>
<th align="left">REPLACEMENT</th>
<th align="left">
<u>Replacement VIN plate</u> - The vehicle's original VIN plate was
<br>damaged or is missing and a replacement plate was issued by the
<br>manufacturer.
<br><u>Replacement Parts</u> - The vehicle's component part has been
<br>replaced and the part has a new number.
</th>
</tr>
<tr>
<th align="left">DONATED VEHICLE</th>
<th align="left">The vehicle was donated and removed from commerce.</th>
</tr>
<tr>
<th align="left">TEST VEHICLE</th>
<th align="left">The vehicle is used for testing purposes and is not to be sold.</th>
</tr>
<tr>
<th align="left">DATE</th>
<th align="left">The date in which the vehicle was shipped (mm/dd/yy or ccyymmdd).</th>
</tr>
<tr>
<th align="left">DEALER NAME</th>
<th align="left">The name of the dealership that the vehicle was shipped to.</th>
</tr>
<tr>
<th align="left">DEALER CODE</th>
<th align="left">The dealer code supplied by the dealer.</th>
</tr>
<tr>
<th align="left">DEALER CITY, STATE</th>
<th align="left">The city and state where the dealer is located.</th>
</tr>
<tr>
<th align="left">PHONE</th>
<th align="left">The phone number for the dealer.</th>
</tr>
</table>

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

====Salvage File Response====

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

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.

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

====Export File Response====

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center">Explanation</th>
</tr>
<tr>
<th align="left">VYR/</th>
<th align="left">Last two or four digits of the model year of the vehicle.</th>
</tr>
<tr>
<th align="left">VMA/</th>
<th align="left">The vehicle make as encoded in NCIC supplied tables.</th>
</tr>
<tr>
<th align="left">DATE OF EXPORT/</th>
<th align="left">Date of export (mm/dd/yy or ccyymmdd).</th>
</tr>
<tr>
<th align="left">DESTINATION/</th>
<th align="left">Destination of export.</th>
</tr>
</table>

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

====Vehicle Claims Responses====

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center">Explanation</th>
</tr>
<tr>
<th align="left">MEMBER COMPANY/</th>
<th align="left">The name of the company that reported the claim.</th>
</tr>
<tr>
<th align="left">CLAIM NUMBER/</th>
<th align="left">The number assigned by the insurance company</th>
</tr>
<tr>
<th align="left">INS PHONE/</th>
<th align="left">The telephone number of the filing insurance company office</th>
</tr>
<tr>
<th align="left">IMPACT POINT/</th>
<th align="left">The initial impact point of the vehicle according to the filed claim</th>
</tr>
<tr>
<th align="left">MILEAGE/</th>
<th align="left">The mileage at the time of the accident.</th>
</tr>
</table>

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

====Rental Fleet File Response====

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

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

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

====NCIC Purge/Inactive Response====

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

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center">Explanation</th>
</tr>
<tr>
<th align="left">CONDITION OF RECOVERY/</th>
<th align="left">Condition of vehicle at time of recovery</th>
</tr>
<tr>
<th align="left">RECOVERING ORI/</th>
<th align="left">The 9 digit identifier of the recovering agency</th>
</tr>
<tr>
<th align="left">REPORTING ORI/</th>
<th align="left">The 9 digit identifier of the reporting agency</th>
</tr>
</table>
===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.

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

* 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.

<ul>
<li>Those data fields that have a double asterisk(**) may be added, deleted or modified.
<li>Those fields with a single asterisk(*) may not be deleted since they are required fields.
<li>The "FIL" and "ORI" fields are required and may not be updated in any way.
</ul>

<table border="1">
<tr>
<th align="center">Entry</th>
<th align="center"># Char.</th>
<th align="center">Explanation</th>
</tr>
<tr>
<th align="left">NUI.</th>
<th align="center">3</th>
<th align="left">Message key identifies NICB update of Impound record
<br>followed by a period.</th>
</tr>
<tr>
<th align="left">Sender ORI.</th>
<th align="center">9</th>
<th align="left">ORI of sender followed by a period.</th>
</tr>
<tr>
<th align="left">NA.</th>
<th align="center">2</th>
<th align="left">Destination ORI of NICB followed by a period and
<br>optional control field.</th>
</tr>
<tr>
<th align="left">TXT</th>
<th align="center">3</th>
<th align="left">Fixed filed prefix to beginning of message.</th>
</tr>
<tr>
<th align="left">FIL/</th>
<th align="center">4</th>
<th align="left">Prefix for unique NICB impound record number.</th>
</tr>
<tr>
<th align="left">File #</th>
<th align="center">11</th>
<th align="left">Unique NICB impound record number followed by period.</th>
</tr>
<tr>
<th align="left">ORI/</th>
<th align="center">4</th>
<th align="left">Prefix for impound agency ORI.</th>
</tr>
<tr>
<th align="left">ORI.</th>
<th align="center">9</th>
<th align="left">ORI of impounding agency followed by a period.</th>
</tr>
<tr>
<th align="left">OCA/</th>
<th align="center">4</th>
<th align="left">Prefix for Case #.</th>
</tr>
<tr>
<th align="left">* Case #.</th>
<th align="center">20</th>
<th align="left">Case #(no special characters) followed by a period.</th>
</tr>
<tr>
<th align="left">DOI/</th>
<th align="center">4</th>
<th align="left">Prefix for Date of Impound.</th>
</tr>
<tr>
<th align="left">* Date of Impound</th>
<th align="center">6-8</th>
<th align="left">Date vehicle was impounded followed by a period.
<br>mmddyy or ccyymmdd.</th>
</tr>
<tr>
<th align="left">PND/</th>
<th align="center">4</th>
<th align="left">Prefix for Name of Pound holding vehicle.</th>
</tr>
<tr>
<th align="left">* Pound Name</th>
<th align="center">24</th>
<th align="left">Name of Pound holding vehicle followed by a period.</th>
</tr>
<tr>
<th align="left">VMA/</th>
<th align="center">4</th>
<th align="left">Prefix for Vehicle Make.</th>
</tr>
<tr>
<th align="left">** Veh. Make</th>
<th align="center">2-4</th>
<th align="left">Vehicle Make followed by a period.</th>
</tr>
<tr>
<th align="left">VMO/</th>
<th align="center">4</th>
<th align="left">Prefix for Vehicle Model.</th>
</tr>
<tr>
<th align="left">** Veh. Model</th>
<th align="center">3</th>
<th align="left">Vehicle Model followed by a period.</th>
</tr>
<tr>
<th align="left">VYR/</th>
<th align="center">4</th>
<th align="left">Prefix for Vehicle Year.</th>
</tr>
<tr>
<th align="left">** Veh. Year</th>
<th align="center">2-4</th>
<th align="left">Vehicle Year followed by a period.</th>
</tr>
<tr>
<th align="left">VST/</th>
<th align="center">4</th>
<th align="left">Prefix for Vehicle Style.</th>
</tr>
<tr>
<th align="left">** Veh. Style</th>
<th align="center">2</th>
<th align="left">Vehicle style followed by a period.</th>
</tr>
<tr>
<th align="left">LIC/</th>
<th align="center">4</th>
<th align="left">Prefix for License # followed by a period.</th>
</tr>
<tr>
<th align="left">** License #</th>
<th align="center">1-10</th>
<th align="left">License # followed by a period.</th>
</tr>
<tr>
<th align="left">LIS/</th>
<th align="center">4</th>
<th align="left">Prefix for License State followed by a period.</th>
</tr>
<tr>
<th align="left">** License State</th>
<th align="center">2</th>
<th align="left">License State followed by a period.</th>
</tr>
<tr>
<th align="left">LIY/</th>
<th align="center">4</th>
<th align="left">Prefix for License Year.</th>
</tr>
<tr>
<th align="left">** License Year</th>
<th align="center">2</th>
<th align="left">License Year followed by a period.</th>
</tr>
<tr>
<th align="left">LIT/</th>
<th align="center">4</th>
<th align="left">Prefix for License Type.</th>
</tr>
<tr>
<th align="left">** License Type</th>
<th align="center">2</th>
<th align="left">License Type followed by a period.</th>
</tr>
<tr>
<th align="left">MSC/</th>
<th align="center">4</th>
<th align="left">Prefix for Miscellaneous Field.</th>
</tr>
<tr>
<th align="left">** Misc. Field</th>
<th align="center">42</th>
<th align="left">Free format field followed by a period.</th>
</tr>
<tr>
<th align="left">INV/</th>
<th align="center">4</th>
<th align="left">Prefix for Pound's Inventory #.</th>
</tr>
<tr>
<th align="left">** Inventory #</th>
<th align="center">12</th>
<th align="left">Pound's Inventory # followed by a period.</th>
</tr>
<tr>
<th align="left">PHO/</th>
<th align="center">4</th>
<th align="left">Prefix for Phone # of Pound.</th>
</tr>
<tr>
<th align="left">** Phone #</th>
<th align="center">10</th>
<th align="left">Phone # of Pound followed by a period.</th>
</tr>
<tr>
<th align="left">DER/</th>
<th align="center">4</th>
<th align="left">Prefix for New York Derelict Vehicle.</th>
</tr>
<tr>
<th align="left">** Y</th>
<th align="center">1</th>
<th align="left">Fixed field of "Y" if a New York Derelict (Note: last field
<br>must not be followed by a period).</th>
</tr>
</table>

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.

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

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=====

<u>Example 1</u>: A query for Impound/Export Information.

<table border="1">
<tr>
<th align="left">NIQ.AZNLETS20.NA.TXT
<br>VIN/AAAAA1111AA111111</th>
</tr>
</table>

<u>Example 2</u>: A query of All Files.

<table border="1">
<tr>
<th align="left">NAQ.AZNLETS20.NA.TXT
<br>VIN/AAAAA111111111111</th>
</tr>
</table>

<u>Example 3</u>: An Entry to Impound File.

<table border="1">
<tr>
<th align="left">
NEI.AZNLETS20.NA.TXT
<br>VIN/1A1AA111AAA111111.ORI/AZ0000000.OCA/A11111111.DOI/20120101.
<br>PND/TOWING COMPANY.VMA/CHEV.VMO/CAV.VYR/2000.VST/4D.LIC/111AAA.
<br>LIS/AZ.LIT/PC.MSC/AUTOMOTIVE CENTER, CONTACT JOHN.PHO/6025551234
</th>
</tr>
</table>

<u>Example 4</u>: A Response from NICB on an Impound File being added.

<table border="1">
<tr>
<th align="left">
NEA.ILNATBC00
<br>10:00 01/01/2010 61239
<br>10:00 01/01/2010 01239 AZNLETS20
<br>TXT
<br>IMPOUND RECORD ADDED VIN/1A1AA111111111111.FIL/A1111111111
</th>
</tr>
</table>

<u>Example 5</u>: A Modification to Impound File.

<table border="1">
<tr>
<th align="left">NUI.AZNLETS20.NA.TXT
<br>FIL/A1111111111.ORI/AZ0000000.DOI/20110101</th>
</tr>
</table>

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

<table border="1">
<tr>
<th align="left">
NUA.ILNATBC00
<br>15:00 01/01/2010 81232
<br>15:00 01/01/2010 11239 AZNLETS20
<br>TXT
<br>IMPOUND RECORD UPDATED
<br>FIL/A1111111111
</th>
</tr>
</table>

<u>Example 7</u>: A Cancellation of Impound File.

<table border="1">
<tr>
<th align="left">NCI.AZNLETS20.NA.TXT
<br>VIN/1AAAA11A1AA111111.FIL/A1111111111</th>
</tr>
</table>

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

<table border="1">
<tr>
<th align="left">
NCA.ILNATBC00
<br>15:00 01/01/2010 51231
<br>15:00 01/01/2010 81235 AZNLETS20
<br>TXT
<br>IMPOUND RECORD CANCELLED VIN/AAAAA11A11A111111.FIL/A1111111111
</th>
</tr>
</table>

<u>Example 9</u>: A response to Impound/Export query.

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

<u>Example 10</u>: A response from All Files.

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

<u>Example 11</u>: Microdot NVS Query.

<table border="1">
<tr>
<th align="left">NAQ.AZNLETS20.NA.TXT
<br>VIN/AAVZZZ6SZHU027272</th>
</tr>
</table>

<u>Example 12</u>: Microdot NVS Response.

<table border="1">
<tr>
<th align="left">NAR.VANVS005V
07:55 12/07/2017 00387
<br>07:55 12/07/2017 00010 AZNLETS20
<br>TXT
<br>RESPONSE FOR VIN/ AAVZZZ6SZHU027272
<br>Micro Dot Response:
<br>VIN: AAVZZZ6SZHU027272
<br>Microdot Number: ZARDV00441281
<br>Engine Number: CLP275260
<br>Vehicle Year: 2017
<br>Vehicle Make: VOLKSWAGEN
<br>Vehicle Model: POLO VIVO SEDAN 1.4 T/LINE 63K
<br>Vehicle Color: Pure White

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

<br>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
<br>will contain Impound, Import/Export, Insurance Theft File, NCIC/CPIC Vehicle Purge Data, Manufacturer's Shipping File, Salvage File, International <br>Index, Auction File, Pre-Inspection File, Vehicle Physical Damage Claim File, and Rental File data.

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

<br>PLEASE NOTE: The attached information is being provided as a lead only and should be verified before any action is taken by your Agency.</th>
</tr>
</table>

[[#top|Top]]

== Downloads ==

[https://schema.nlets.org/Wiki/Schemas/NAQ.ZIP Download NAQ Schema]

[https://schema.nlets.org/Wiki/Schemas/NAR.ZIP Download NAR Schema]

[https://schema.nlets.org/Wiki/Stylesheets/NAR.xslt Download NAR Stylesheet]

[https://schema.nlets.org/Wiki/Schemas/NIR.ZIP Download NIR Schema]

[https://schema.nlets.org/Wiki/Stylesheets/NIR.xslt Download NIR Stylesheet]

[https://schema.nlets.org/Wiki/Schemas/NCI.ZIP Download NCI Schema]

[https://schema.nlets.org/Wiki/Stylesheets/NCI.xslt Download NCI Stylesheet]

[https://schema.nlets.org/Wiki/Schemas/NUA.ZIP Download NUA Schema]

[https://schema.nlets.org/Wiki/Stylesheets/NUA.xslt Download NUA Stylesheet]

[https://schema.nlets.org/Wiki/Schemas/NUI.ZIP Download NUI Schema]

[https://schema.nlets.org/Wiki/Stylesheets/NUI.xslt Download NUI Stylesheet]

[https://schema.nlets.org/Wiki/Schemas/NEI.ZIP Download NEI Schema]

[https://schema.nlets.org/Wiki/Stylesheets/NEI.xslt Download NEI Stylesheet]

[https://schema.nlets.org/Wiki/Schemas/SVQ.ZIP Download SVQ Schema] -- Added on 11/20/19

[https://schema.nlets.org/Wiki/Schemas/SVR.ZIP Download SVR Schema] -- Added on 11/20/19

[https://schema.nlets.org/Wiki/Stylesheets/SVR.xslt Download SVR Stylesheet] -- Added on 11/20/19

[[#top|Top]]