NIEM Examples - National Insurance Crime Bureau and National Vehicle Services and Locator (NAQ/NAR, NCI, NEI, NIQ/NIR)

NIEM

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

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

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

NICB provides automated access to twelve different files:

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

NVS provides access to lien holder and auction data.

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

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

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

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

Access to these files is for investigative purposes only.

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

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

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

Element Dictionary

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

Query Formats

Query for Impound/Export Information (NIQ)

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

nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
- nc:VehicleIdentification
  A unique combination of alphanumeric characters that identifies a specific vehicle.
  - nc:IdentificationID
    A value that identifies something.
    This element will contain the VIN to be queried.

Query of all files (NAQ)

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

nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
- nc:VehicleIdentification
  A unique combination of alphanumeric characters that identifies a specific vehicle.
  - nc:IdentificationID
    A value that identifies something.
    This element will contain the VIN to be queried. If only a partial VIN is available the user may submit the last 8 characters of The VIN. In order to identify the VIN as partial to NICB the user MUST preface the partial VIN by the word "PARTIAL". For example a partial VIN with the year 1990 would look like this:
```
<nc:VehicleIdentification><nc:IdentificationID>PARTIAL24657468</nc:IdentificationID></nc:VehicleIdentification>
```
    Note that there is no space or Separator between the word "PARTIAL" and the six character VIN. When a partial VIN search is requested only the Manufacturers Shipping File will be searched.
n2:PartIdentification
A Vehicle Part
- nc:IdentificationID
  A unique combination of alphanumeric characters that identifies a specific Part. (used only by NVS)

Entry Formats

Entry to Impound File (NEI)

n2:NLETSUpdateData

n2:LawEnforcementAgency
- j:OrganizationAugmentation
  Additional information about an organization.
  - j:OrganizationORIIdentification
    A unique identifier assigned to a justice-related organization by the federal government.
    - nc:IdentificationID
      A value that identifies something.
      This element will contain the ORI of the impounding agency.
nc:Incident
An occurrence or an event that may require a response.
- nc:ActivityIdentification
  An identification that references an activity.
  - nc:IdentificationID
    A value that identifies something.
    This element will contain the case number.
n2:ImpoundActivity
Details about a impound action associated with a vehicle.
- nc:ActivityIdentification
  An identification that references an activity.
  - nc:IdentificationID
    A value that identifies something.
    This optional element will contain the inventory number of the pound.
- nc:ActivityDate
  A date of an activity.
  - nc:Date
    A full date.
    This optional element will contain the date the vehicle was impounded. The value should be in the format ccyy-mm-dd.
n2:ImpoundOrganization
Describes the entity that has impounded a vehicle.
- nc:OrganizationName
  A name of an organization.
  This element contains the name of the pound.
- nc:OrganizationPrimaryContactInformation
  A preferred means of contacting an organization.
  - nc:ContactTelephoneNumber
    A telephone number for a telecommunication device by which a person or organization may be contacted.
    - nc:FullTelephoneNumber
      A full telephone number.
      - nc:TelephoneNumberFullID
        A complete telephone number.
        Telephone number for this location of the pound. The actual value (all numeric, no dashes) should be contained in the subelement.
nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
- nc:VehicleIdentification
  A unique combination of alphanumeric characters that identifies a specific vehicle.
  - nc:IdentificationID
    A value that identifies something.
    This element will contain the VIN to be queried.
- nc:VehicleMakeCode
  A manufacturer of a vehicle.
  This optional element will contain the make of the vehicle being added. Allowable values come from the NCIC VMA code table.
- nc:VehicleModelCode
  A specific design or class of vehicle made by a manufacturer.
  This optional element will contain the model of the vehicle being added. Allowable values come from the NCIC VMO code table.
- nc:ConveyanceRegistrationPlateIdentification
  An identification on a metal plate fixed to a conveyance.
  - nc:IdentificationID
    A value that identifies something.
    This optional element will contain the license plate number to be queried.
  - nc:IdentificationCategoryText
    A kind of identification.
    This optional element should contain the type of license plate being queried. Allowable values come from the NCIC LIT code table.
  - nc:IdentificationExpirationDate
    A date after which an identification is no longer valid.
    - nc:Date
      A full date.
      This optional element's value should be the expiration date of the license plate. Data should be formatted yyyy-mm-dd.
  - nc:IdentificationJurisdictionText
    An area, region, or unit in which a unique identification is issued.
    This optional element's value should be the issuing state of the license plate.
- nc:ItemModelYearDate
  A year in which an item was manufactured or produced.
  This optional element will contain the year of the vehicle. Data should be formatted YYYY.
- nc:VehicleStyleCode
  A style of a vehicle.
  This optional element will contain the style of the vehicle being added. Allowable values come from the NCIC VST code table.
n2:NewYorkDerelictIndicator
Optional element containing a Y if the vehicle is New York derelict.
Optional element containing a Y if the vehicle is New York derelict.
n2:MiscellaneousUpdateText
Optional Miscellaneous Field. Free text format.
Optional Miscellaneous Field. Free format.

Update Formats

Modification to Impound File (NUI)

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

nc:IdentificationID
A value that identifies something.
This element will contain the actual NICB number being queried.
n2:LawEnforcementAgency
j:OrganizationAugmentation
Additional information about an organization.
j:OrganizationORIIdentification
A unique identifier assigned to a justice-related organization by the federal government.
nc:IdentificationID
A value that identifies something.
This element will contain the ORI of the impounding agency.

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

nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
This element will contain the case number.

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

nc:ActivityIdentification
An identification that references an activity.
nc:IdentificationID
A value that identifies something.
This optional element will contain the inventory number of the pound.
nc:ActivityDate
A date of an activity.
nc:Date
A full date.
This optional element will contain the date the vehicle was impounded. The value should be in the format ccyy-mm-dd.

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

nc:OrganizationName
A name of an organization.
This element contains the name of the pound.
nc:OrganizationPrimaryContactInformation
A preferred means of contacting an organization.
- nc:ContactTelephoneNumber
  A telephone number for a telecommunication device by which a person or organization may be contacted.
  - nc:FullTelephoneNumber
    A full telephone number.
    - nc:TelephoneNumberFullID
      A complete telephone number.
      Telephone number for this location of the pound. The actual value (all numeric, no dashes) should be contained in the subelement.

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

nc:VehicleIdentification
A unique combination of alphanumeric characters that identifies a specific vehicle.
- nc:IdentificationID
  A value that identifies something.
  This element will contain the VIN to be queried.
nc:VehicleMakeCode
A manufacturer of a vehicle.
This optional element will contain the make of the vehicle being added. Allowable values come from the NCIC VMA code table.
nc:VehicleModelCode
A specific design or class of vehicle made by a manufacturer.
This optional element will contain the model of the vehicle being added. Allowable values come from the NCIC VMO code table.
nc:ConveyanceRegistrationPlateIdentification
An identification on a metal plate fixed to a conveyance.
- nc:IdentificationID
  A value that identifies something.
  This optional element will contain the license plate number to be queried.
- nc:IdentificationCategoryText
  A kind of identification.
  This optional element should contain the type of license plate being queried. Allowable values come from the NCIC LIT code table.
- nc:IdentificationExpirationDate
  A date after which an identification is no longer valid.
  - nc:Date
    A full date.
    This optional element's value should be the expiration date of the license plate. Data should be formatted yyyy-mm-dd.
- nc:IdentificationJurisdictionText
  An area, region, or unit in which a unique identification is issued.
  This optional element's value should be the issuing state of the license plate.
nc:ItemModelYearDate
A year in which an item was manufactured or produced.
This optional element will contain the year of the vehicle. Data should be formatted YYYY.
nc:VehicleStyleCode
A style of a vehicle.
This optional element will contain the style of the vehicle being added. Allowable values come from the NCIC VST code table.

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

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

Cancel Formats

Cancellation of Impound File (NCI)

n2:NLETSUpdateData

n2:NICBImpoundRecordIdentification
This optional element will contain unique NICB impound record number.
- nc:IdentificationID
  A value that identifies something.
  This element will contain the NICB number being queried.
nc:Vehicle
A motor-driven conveyance designed to carry its operator, and optionally passengers and cargo, over land.
- nc:VehicleIdentification
  A unique combination of alphanumeric characters that identifies a specific vehicle.
  - nc:IdentificationID
    A value that identifies something.
    This element will contain the VIN to be queried.

Response Formats

Response to Impound/Export query (NIR)

n2:NLETSResponseData

n2:ResponseText
This element will contain the free text response. Nlets recommends the use of <![CDATA[CONTENT HERE]]> tags to ensure that the response does not contain any characters illegal in XML.

Response to all files query (NAR)

n2:NLETSResponseData

n2:ResponseText
This element will contain the free text response. Nlets recommends the use of <![CDATA[CONTENT HERE]]> tags to ensure that the response does not contain any characters illegal in XML.
Some manufacturers provide NICB with the status of vehicles which have special circumstances pertaining to them NICB then places a status condition into the status field. NICB may or may not have additional information regarding a status condition. Therefore, if a vehicle has a status condition, NICB should be contacted. Below is a list of status conditions and their definitions:

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

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

n2:NLETSResponseData

n2:ResponseText
This element will contain the free text response. Nlets recommends the use of <![CDATA[CONTENT HERE]]> tags to ensure that the response does not contain any characters illegal in XML.

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

Example 1: A query for Impound/Export Information.

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

Example 2: A query of All Files.

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

Example 3: An Entry to Impound File.

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

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

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

Example 5: A Modification to Impound File.

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

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

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

Example 7: A Cancellation of Impound File.

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

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

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

Example 9: A response to Impound/Export query.

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

Example 10: A response from All Files.

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

Example 11: A query to Locator Technologies for Canada.

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

Example 12: A response from Locator Technologies for Canada.

Example 12-1

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

Example 12-2

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZLOC0000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
    <nh2:DocumentControlFieldText><![CDATA[CROSSFIRE1]]></nh2:DocumentControlFieldText>
    <nh2:MessageReceiveDate>11/19/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:38</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>11/19/2019</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:38</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00875</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSResponseData n2:key="NAR">
    <n2:ResponseText>Locator Technologies Vehicle Impound records for VIN: 1HGCM71696A801057
 
      Impound Date : 2019-04-14
      Notes        : INVOICE 190128
      PO# NON-CONTRACT
      Location     : 180 Bullock St Unit 7 Markham ON L3P7N2
      Contact Name : Cardinal Towing Inc.,
      Contact Phone: 9054720426 or 4168841977
      Contact Email: impound@cardinaltowing.ca
 
      This information is being provided by Locator Technologies, LLC.
      If you require additional information or assistance, please contact
      a Law Enforcement Assistant at 310-722-2889.
 
      PLEASE NOTE: The attached information is being provided as a lead only
      and should be verified before any action is taken by your Agency.</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 13: A query to Locator Technologies for Mexico.

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

Example 14: A response from Locator Technologies for Mexico.

Example 14-1

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>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>

Example 14-2

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

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

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

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

Example 15: A query to Locator Technologies for America.

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

Example 16: A response from Locator Technologies for America.

Example 16-1

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nc4="http://release.niem.gov/niem/niem-core/4.0/" 
xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:j6="http://release.niem.gov/niem/domains/jxdm/6.1/" 
xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" 
xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>ILNATBC00</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS45</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>06/28/2019</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>10: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>

Example 16-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>

Example 16-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>

Example 16-4

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

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

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

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

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

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

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

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

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

Example 18-1

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

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

Example 18-2

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

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

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

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

Example 18-3

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

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

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

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

Example 19: A query to Locator Technologies for OCRA database

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

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

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

Example 21: An Inquiry to NVS by Part ID and response

Example 21-1

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>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">
    <n2:PartIdentification>
        <nc:IdentificationID>PID123456789</nc:IdentificationID>
    </n2:PartIdentification>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 21-2

<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>NAR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NVNVS005V</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>
       RESPONSE FOR VIN/ USAC1234

       RETAINAGROUP Marked Part
       VIN: 1C4BJWDGXHL747096
       Code: USAC1234
       Part: CATALYTIC
       Status: REGISTRATION
       Status Date: 2021-03-17
       
       To view all information available for this record, please visit http://www.isrcodecheck.com/
       
       This response may contain Lien Holder, NHTSA Recall, 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>