Section 26: Commercial Vehicle Information

From Nlets Wiki
Jump to: navigation, search

Commercial Vehicle Information (ACQ/ACR, AVQ/AVR, DQ/DR & KQ/KR)

This section describes how to access the Performance and Registration Information Systems Management file (PRISM). This system provides Nlets users with access to safety information on motor carriers and the vehicles that are assigned to those motor carriers. Nlets users can access the PRISM Target File through an Nlets Carrier Status Query (ACQ) or an Nlets Vehicle Status Query (AVQ) to destination FM. Nlets users can access the FMCSA Database by sending a Driver License Query (DQ) or Driver History Query (KQ) to destination CL.

PRISM Background

The Federal Motor Carrier Safety Administration of the U.S. Department of Transportation has developed the SAFER and PRISM Systems. Each of the PRISM states receives a copy of the U.S. Department of Transportation's Motor Carrier Management Information System (MCMIS) Census File from the SAFER System or the PRISM Census File that is a subset of the MCMIS Census File from the PRISM System. These files contain information on all motor carriers who have been assigned a US Department of Transportation Number (DOT Number).

One of the information items is a Motor Carrier Safety Improvement Process (MCSIP) rating which is a two-character code. This MCSIP 'Step' indicates a motor carrier's safety status. PRISM states using PRISM files can download daily updates to the MCMIS Census File. PRISM States also have the option of using a SAFER process named CVIEW (Commercial Vehicle Exchange Window) that provides daily carrier and IRP vehicle registration updates. For those states using PRISM files the PRISM Central Site extracts motor carrier information for all motor carriers whose MCSIP Step places them in MCSIP. This PRISM Carrier File is available for daily downloading from the PRISM Central Site. The PRISM State must then scan their IRP vehicle registration records for all vehicles assigned for safety to a MCSIP carrier and transmit the PRISM Vehicle File to the PRISM Central Site each night. PRISM States using CVIEW will receive daily updates on carrier and IRP vehicle registration records and will provide updates on a daily basis to SAFER for all IRP vehicle registration changes.

The PRISM Target File data along with the CVIEW vehicle data are used to create the daily PRISM Target File.

MCSIP Step Chart (Feb 2014)

Step Number Targeted at Roadside Deny Registration Step Description External Description for Web
Sites, Inspection Software, etc.
0 N N Not In MCSIP Not Targeted
3 Y N Past Due CR Not Targeted
7 Y N Mandatory CR Not Targeted
22 N N Compliance Review Complete Not Targeted
52 Y Y Biennial Update not Completed Biennial Update not COmpleted
53 N N Not Implemented - Placeholder for future new OOSO N/A
54 Y Y OOSO - Imminent Hazard OOS: Imminent Hazard
55 Y Y OOSO - Unsat/Unfit OOS: Unfit Motor Carrier
56 Y Y OOSO - New Entrant Revoked

for Expedited Actions and

Intrastate Out-of-Service
New Entrant - OOSO Revoked

for Expedited Actions and

Intrastate Out-of-Service
57 Y Y OOSO - Failure to Pay Fine for Safety Violation OOS: Failure to Pay
58 Y Y OOSO - New Entrant Revoked for Expedited Actions New Entrant - OOSO Revoked for Expedited Actions
59 Y N Intrastate Out-of-Service Intrastate Out-of-Service
60 Y Y OOSO - Imminent Hazard and Intrastate Out-of-Service OOS: Imminent Hazard and Intrastate Out-of-Service
61 Y Y OOSO - Unsat/Unfit and Intrastate Out-of-Service OOS: Unfit Motor Carrier and Intrastate Out-of-Service
62 Y Y OOSO - Failure to Pay and Intrastate Out-of-Service OOS: Failure to Pay and Intrastate Out-of-Service
63 Y Y OOSO - New Entrant Revoked for Refusal of Audit/No Contact New Entrant - OOSO Revoked for Refusal of Audit/No Contact
64 Y Y OOSO - New Entrant Revoked for Failure of Safety Audit New Entrant - OOSO Revoked for Failure of Safety Audit
65 Y Y OOSO - Operating without Authority OOS: Operating without Authority
66 Y Y OOSO - Operating without

Authority and Intrastate Out-of-

Service
OOS: Operating without

Authority and Intrastate Out-of-

Service
67 Y Y OOSO - New Entrant Revoked

for Refusal of Audit/No Contact

and Intrastate Out-of-Service
New Entrant - OOSO Revoked

for Refusal of Audit/No Contact

and Intrastate Out-of-Service
68 Y Y OOSO - New Entrant Revoked

for Failure of Safety Audit and

Intrastate Out-of-Service
New Entrant - OOSO Revoked

for Failure of Safety Audit and

Intrastate Out-of-Service
99 N N Carrier Out of Business Not Targeted

FMCSA Background

Federal Motor Carrier Safety Administration (FMCSA), has provided their Commercial Driver's License Information System to Nlets users. CDLIS supports the issuance of commercial driver licenses (CDLs) by the jurisdictions and assists jurisdictions in meeting the goals of the basic tenet "that each driver, nationwide, have only one driver license and one record." CDLIS has operated in all 51 U.S. jurisdictions (50 states and the District of Columbia) since 1992. CDLIS consists of a Central Site and nodes at the Motor Vehicle Agencies (MVAs) of the 51 jurisdictions. The Central Site houses identification data about each commercial driver registered in the jurisdictions, such as:

  • Name
  • Date of birth
  • Social Security Number
  • State driver license number
  • AKA information
  • Current "State of Record" (SOR)

This information constitutes a driver's unique CDLIS Master Pointer Record (MPR). Each MVA houses detailed information about each driver for which it is the SOR. This detailed information, called the driver history, includes identification information, license information, and a history of convictions and withdrawals.

Up until now, Motor Carrier Safety Officers and other law enforcement personnel seeking commercial driver's license detail were required to query CDLIS through a web application provided by FMCSA. While this application is robust, it is generally accessed through a mobile data terminal equipped with a wireless cellular air card. These devices have proved costly and therefore the service has not been available to all whom need it. Nlets and the FMCSA have been working together to provide a solution that allows access by all Nlets users via their existing Nlets connections. Utilizing the existing Nlets Drivers Query Message Key (DQ), any and all authorized Nlets users may query the central CDLIS database.

In order to query CDLIS via Nlets your state or agency will need to make two minor modifications to your Nlets DQ message transaction:

  • Regardless of the state of record, the Nlets DQ header must be destined to the Nlets destination of "CL".
  • A mandatory field of "OLS" has been added to the DQ transaction. It is in this field that your users will enter the state of record.

Carrier Status Query / Response (ACQ/ACR)

This section provides an overview and details regarding the Carrier Status Query/Response (ACQ/ACR).

Overview

An agency may request carrier information by sending the Carrier Status Query (ACQ) to the PRISM Central Site Target File where the information is stored.

Section26-ACQ.jpg

Query Requirements

  • Carrier Status Queries are addressed to the 2-character destination code "FM".
  • All messages will be preceded by a standard input header.
  • No embedded spaces or special characters (i.e., hyphens) should be in the inquiry.
  • Control characters are permitted throughout the text of the message and should be ignored by the queried organization when examining the inquiry.

Carrier Status Query Field Requirements (ACQ)

The table that follows describes requirements for Carrier Status Queries (ACQ).

The field requirement for Carrier Status Queries (ACQ):

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<nc:IdentificationID>
DOT/ 1-7 Alphanumeric only Department of Transportation (DOT) number

Carrier Status Responses (ACR)

The table that follows describes requirements for Carrier Status Responses (ACR).

The requirements for Carrier Status Responses (ACR), along with their translations are:

Entry: Field
Size:
Data Requirements: Translation:
USDOT NBF/ 7 Alphanumeric only US DOT number assigned by the Office of
Motor Carriers.
NAM/ 55 Alpha Characters Name
DBA/ 55 Alphanumeric only Doing business as
ADR/ 30 See NCIC Manual Street address
CITY/ 25 See NCIC Manual City
CTY/ 3 Alphanumeric only County code
ST/ 2 XX=2 character state code State code
ZIP/ 10 Numeric Postal code
CAR-TARG HIST-IND/ 1 Single character T or H Carrier Target (T) or History (H) indicator
MCSIP STEP/ 2 Numeric MCSIP step
MCSIP DATE/ 8 ccyy-mm-dd MCSIP date

Vehicle Status Query / Response (AVQ/AVR)

This section provides an overview and details regarding the Vehicle Status Query and Vehicle Status Response (AVQ/AVR).

Overview

An agency may request vehicle information by sending the Nlets Vehicle Status Query (AVQ) to the PRISM Central Site Target File. Information may be requested either by vehicle identification number (VIN) or by license plate number (LIC) and license state (LIS). The PRISM Target File will route the response back to the requester.

Section26-AVQ.jpg

Query Requirements

  • All messages will be preceded by a standard input header.
  • No embedded spaces or special characters (i.e., hyphens) should be in the inquiry.
  • Control characters are permitted throughout the text of the message and should be ignored by the queried organization when examining the inquiry.
Vehicle Status Query Field Requirements (AVQ)

The table that follows describes requirements for Vehicle Status Queries (AVQ).

The field requirements used for vehicle status queries by vehicle identification number or by license plate number and license state are described in the tables that follow.

XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
<nc:IdentificationID>
VIN/ Max.17 Alphanumeric Vehicle ID number
OR
<nc:IdentificationID>
LIC/ Max.17 Alphanumeric License plate number
<nc:IdentificationSourceText>
LIS/ 1-7 2 character state code License state

Vehicle Status Responses (AVR)

The table that follows describes requirements for Vehicle Status Responses (AVR).

Entries used for Vehicle Status Responses (AVR), along with their translations are:

Entry: Field
Size:
Data Requirements: Translation:
USDOT NBF/ 7 Alphanumeric only US DOT number assigned by the Office of
Motor Carriers
NAM/ 55 See NCIC Manual Name
DBA/ 55 Alphanumeric only Doing business as
ADR/ 30 See NCIC Manual Street address
CITY/ 25 See NCIC Manual City
CTY/ 3 Alphanumeric only County code
ST/ 2 XX=2 character state code State code
ZIP/ 10 Alphanumeric Zip code
CAR-TARG HIST-IND/ 1 Single character "T" or "H" Carrier Target (T) or History (H) indicator
CAR-TAR-HIST DATE/ 8 ccyy-mm-dd Date of the Target/History indicator
MCSIP STEP/ 2 Numeric MCSIP step
MCSIP DATE/ 8 ccyy-mm-dd MCSIP date

Vehicle Status Response Additional Information (AVR)

A message providing an overall assement of the carrier's safety status will appear at the top of the response text. The following messages are used and are based on the value of the MCSIP Step:

CARRIER IS TARGETED FOR INSPECTION
CARRIER IS UNDER FEDERAL OOSO ' IMMINENT HAZARD
CARRIER IS UNDER FEDERAL OOSO ' UNSAT/UNFIT
CARRIER IS UNDER FEDERAL OOSO ' FAILURE TO PAY
CARRIER IS UNDER FEDERAL OOSO ' NEW ENTRANT REVOKED FOR REFUSAL OF AUDIT/NO CONTACT
CARRIER IS UNDER FEDERAL OOSO ' NEW ENTRANT REVOKED FOR FAILURE OF SAFETY AUDIT
CARRIER IS UNDER FEDERAL OOSO ' NEW ENTRANT REVOKED FOR EXPEDITED ACTIONS

PRIOR SEPTEMBER 29, 2013
CARRIER IS UNDER FEDERAL OOSO ' REVOCATION OR SUSPENSION OF OPERATING AUTHORITY
CARRIER IS UNDER FEDERAL OOSO ' REVOCATION OR SUSPENSION OF FOR-HIRE OPERATING AUTHORITY

AFTER SEPTEMBER 29, 2013
CARRIER IS UNDER FEDERAL OOSO ' OPERATING WITHOUT AUTHORITY
CARRIER IS UNDER FEDERAL OOSO ' OPERATING WITHOUT AUTHORITY AND INTRASTATE OOS

In some cases (shown below) the following message will be appended to the OOSO message:
INTRASTATE OUT-OF-SERVICE
If the carrier is not on the PRISM Target File, this message will be displayed:
NOT ON FILE

Top

GJXDM (DEPRECATED)

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

Top

NIEM

Commercial Vehicle Information NIEM Specifications

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

This system provides Nlets users with access to safety information on motor carriers and the vehicles that are assigned to those motor carriers. Nlets users can access the CVIS Target File through a Nlets Carrier Status Query (ACQ) or a Nlets Vehicle Status Query (AVQ).

A second purpose of the Nlets/AAMVAnet connection is to permit state CVIS registration users to utilize the Nlets vehicle registration transactions (RQ/RR) directly from their AAMVAnet terminals.

An agency may request carrier information by sending the Carrier Status Request (ACQ) to the CVIS Central Site Target File where the information is stored. When AAMVAnet responds with an ACR:

  • Up to five ACR messages may be received.
  • When multiple ACR messages are received, each message will have a notation at the bottom of the message "PAGE n of n PAGES" so that the recipient will know how many messages to expect.
  • If more than five carrier records exist on the CVIS Target File, a special notation will be placed at the bottom of each message "MATCH LIMIT EXCEEDED, NOTIFY PRISM HELP DESK".
  • If this message is received, recipients are asked to contact the CVIS Help Desk at AAMVAnet (888) 226-8280(AAMVA80) and report this incident.

An agency may request vehicle information by sending the NLETS Vehicle Status Request (AVQ) to the CVIS Central Site Target File. When AAMVAnet responds with an AVR, there is the possibility that multiple Vehicle Status responses (AVR) messages will be received in response to the Vehicle Status inquiry (AVQ).

  • Although more than 1 registration for a vehicle is unusual, the CVIS Target File may have up to 10 registrations for a single vehicle. The last two lines which contain registration related data may be repeated up to 10 times.
  • A maximum of 10 AVR messages may be received.
  • If multiple AVR messages are sent the following notation will be at the end of each message, "PAGE n of n PAGES".
  • If more than 10 vehicle records have been found on the CVIS Target File with the same VIN or License Plate Number/State, the following notation will be found at the end of each message, "MATCH LIMIT EXCEEDED, NOTIFY CVIS HELP DESK". When this notation is received, the recipient is asked to contact the CVIS Help Desk at AAMVAnet (888) 222-8280(AAMVA80) and report the incident.

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 by DOT Number (ACQ), Query by License Plate, Type, Year (AVQ), Query by VIN (AVQ), Response to Carrier Status Query (ACR) Response to Vehicle Status Query (AVR), Driver's License Query (DQ), Driver's License Response in Free Text (DR), Drivers History Query (KQ) & Drivers History Response in Free Text (KR).

Query Formats

Query by DOT Number (ACQ)

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

  nc:CommercialVehicle
  A class of vehicle that includes motor vehicles with a gross vehicle weight rating of 26,001 pounds or more.
  This element will contain data about a commercial vehicle.

    nc:VehicleMotorCarrierIdentification
    US DOT Number

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

      nc:IdentificationSourceText
      A person, organization, or locale which issues an identification.
      The value "DOT" should be contained in this element to indicate that this federal ID is the DOT number.

Query by License Plate, Year, Type (AVQ)

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:ConveyanceRegistrationPlateIdentification
    An identification on a metal plate fixed to a conveyance.

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

      nc:IdentificationSourceText
      A person, organization, or locale which issues an identification.
      This element's value should be the issuing state of the license plate.

Query by VIN (AVQ)

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
    An identification on a metal plate fixed to a conveyance.

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

Response Formats

Response to carrier status query (ACR)

n2:NLETSResponseData

  n2:ResponseText


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

[CDATA[]]

tags to ensure that the


  response does not contain any characters illegal in XML.

Response to vehicle status query (AVR)

n2:NLETSResponseData

  n2:ResponseText


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

[CDATA[]]

tags to ensure that the


  response does not contain any characters illegal in XML.

Commercial Vehicle Information NIEM Examples

Example 1: Carrier Status query by DOT Number.

<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>ACQ</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>FM</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[1234567890]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="ACQ">
		<nc:CommercialVehicle>
			<nc:VehicleMotorCarrierIdentification>
				<nc:IdentificationID>1234567</nc:IdentificationID>
			</nc:VehicleMotorCarrierIdentification>
		</nc:CommercialVehicle>
	</n2:NLETSInquiryData>
</n2:NLETS>

Example 2: Carrier Status response.

<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>ACR</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>FMLIC0000</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[1234567890]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>12/01/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>00:52</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>12/01/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>00:52</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00015</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSResponseData n2:key="ACR">
		<n2:ResponseText>
       CARRIER IS TARGETED FOR INSPECTION.
       DOT/0111111.
       NAM/ACME INC.
       DBA/ .
       ADR/1234 ANY STREET.
       CITY/PHOENIX.ST/AZ.ZIP/85000
       CAR TARG-IND/T.MCSIP STEP/11.MCSIP
       DATE/20000101.
       PAGE/01 OF/01
		</n2:ResponseText>
	</n2:NLETSResponseData>
</n2:NLETS>

Example 3: Vehicle Status query by License Plate and License State (LIS).

<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>AVQ</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>FM</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[0123456789]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="AVQ">
		<nc:Vehicle>
			<nc:ConveyanceRegistrationPlateIdentification>
				<nc:IdentificationID>AAA1111</nc:IdentificationID>
				<nc:IdentificationSourceText>AZ</nc:IdentificationSourceText>
			</nc:ConveyanceRegistrationPlateIdentification>
		</nc:Vehicle>
	</n2:NLETSInquiryData>
</n2:NLETS>

Example 4: Vehicle Status query by VIN.

<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>AVQ</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
		<nh2:DestinationORIID>FM</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[0123456789]]>
		</nh2:DocumentControlFieldText>
	</n2:NLETSMessageHeader>
	<n2:NLETSInquiryData n2:key="AVQ">
		<nc:Vehicle>
			<nc:VehicleIdentification>
				<nc:IdentificationID>1AAAA11A11A111111</nc:IdentificationID>
			</nc:VehicleIdentification>
		</nc:Vehicle>
	</n2:NLETSInquiryData>
</n2:NLETS>

Example 5: Vehicle Status response.

<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>AVR</nh2:MessageKeyCodeText>
		<nh2:OriginatingORIID>FMLIC0000</nh2:OriginatingORIID>
		<nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
		<nh2:DocumentControlFieldText>
			<![CDATA[1234567890]]>
		</nh2:DocumentControlFieldText>
		<nh2:MessageReceiveDate>12/01/2019</nh2:MessageReceiveDate>
		<nh2:MessageReceiveTime>01:04</nh2:MessageReceiveTime>
		<nh2:MessageSendDate>12/01/2019</nh2:MessageSendDate>
		<nh2:MessageSendTime>01:04</nh2:MessageSendTime>
		<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
		<nh2:SendMessageNumeric>00018</nh2:SendMessageNumeric>
	</n2:NLETSMessageHeader>
	<n2:NLETSResponseData n2:key="AVR">
		<n2:ResponseText>
       CARRIER IS TARGETED FOR INSPECTION.
       DOT/0111111.
       NAM/TRUCKING INC.
       DBA/ .
       ADR/1234 ANY STREET.
       CITY/PHOENIX.ST/AZ.ZIP/85000
       CAR TARG-IND/T.MCSIP STEP/11.MCSIP DATE/20000101.
       VMA/ KEN.VYR/1990.VIN/1XXXX1X1XX111111.
       LIC/AAA1111.LIS/AZ.REG EFF DATE/20010101.REG EXP DATE/20120101.
       VEH TARG-HIST IND/T.
       PAGE/01 OF/01
		</n2:ResponseText>
	</n2:NLETSResponseData>
</n2:NLETS>


Top

Legacy (DEPRECATED)

Commercial Vehicle Information Legacy Specifications

This section provides Legacy format specifications and examples for Nlets user access to Performance and Registration Information Systems Management file (PRISM).

This system provides Nlets users with access to safety information on motor carriers and the vehicles that are assigned to those motor carriers. Nlets users can access the PRISM Target File through an Nlets Carrier Status Query (ACQ) or a Nlets Vehicle Status Query (AVQ).

A second purpose of the Nlets/AAMVAnet connection is to permit state PRISM registration users to utilize the Nlets vehicle registration transactions (RQ/RR) directly from their AAMVAnet terminals.

-Please note-
When querying FMCSA in the TEXT format by NAM, DOB, SEX & OLS; you must not include the first name of the individual. A limitation in the search algorithm exists where FMCSA can only query on the last name of the individual. This limitation does not exist in GJXDM or NIEM formats.

Query Formats

An agency may request carrier information by sending the Carrier Status Request (ACQ) to the PRISM Central Site Target File where the information is stored.

The format for the Nlets Carrier Status Query (ACQ) is as follows.

Entry # Char. Explanation
ACQ. 3 Message type followed by a period.
Message Header 13-24 Standard input message header.
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional).
DOT/ 4 Prefix to identify DOT number.
DOT number 1-7 DOT number.

Vehicle Status Query Specifications (AVQ)

The requirements for vehicle status queries are described below.

  • An agency may request vehicle information by sending the Nlets Vehicle Status Request (AVQ) to the PRISM Central Site Target File.
  • Information may be requested either by vehicle identification number (VIN) or by license plate number (LIC) and license state (LIS).
  • All messages will be preceded by a standard input header.
  • No imbedded spaces nor special characters (i.e., hyphens) should be in the inquiry.
  • All data elements (i.e., vehicle identification number or license plate number and license state) are preceded by a prefix and terminated by a period.
  • The final character should not be a period (this conforms to NCIC message structure).
  • Control characters are permitted throughout the text of the message and should be ignored by the queried organization when examining the inquiry.

The format for a vehicle status query (AVQ) is as follows.

Entry # Char. Explanation
AVQ. 3 Message type followed by a period.
Message Header 13-24 Standard input message header.
TXT 3 Fixed filed prefix to beginning of message.
CR,LF,DEL 3 Control characters (optional)
VIN/ 4 Prefix to identify VIN.
Vehicle ID # Max.17 VIN.
OR
LIC/ 4 Prefix to identify license plate number.
License # Max.10 License plate # followed by a period.
LIS/ 4 Prefix to identify license state.
License state 2 License state.

Response Formats

Carrier Status Response Specifications (ACR)

The requirements for carrier status responses are described below.

  • Up to five ACR messages may be received.
  • When multiple ACR messages are received, each message will have a notation at the bottom of the message "PAGE n of n PAGES" so that the recipient will know how many messages to expect.
  • If more than five carrier records exist on the PRISM Target File, a special notation will be placed at the bottom of each message "MATCH LIMIT EXCEEDED, NOTIFY PRISM HELP DESK". If this message is received, recipients are asked to contact the PRISM Help Desk at AAMVAnet (888) 226-8280(AAMVA80) and report this incident.

The prefixes used for carrier responses, along with their translation are as follows.

Prefix Field Size Translation
USDOT NBR 7 US DOT number assigned by the Office of Motor
Carriers.
NAM/ 55 Name.
DBA/ 55 Doing business as.
ADR/ 30 Street address.
CITY/ 25 City.
CTY/ 3 County code.
ST/ 2 State code.
ZIP/ 10 Zip code.
CAR FILE DATE/ 8 Carrier file date (MMDDYYYY).
CAR-TARG-HIST-IND/ 1 Carrier target (T) or history (H) indicator.
CAR TARG-HIST DATE/ 8 Date of the Target/History Indicator (MMDDYYYY).
MCSIP STEP/ 2 MCSIP step.
MCSIP DATE/ 8 MCSIP date (MMDDYYYY).
SAFESTAT SCORE/ 3 SAFESTAT score.
TIP/ 1 Taxpayer ID type.
TIN/ 9 taxpayer ID #.
MCMIS UPD/ 8 Date of last MCMIS update.
MCMIS UID/ 8 User ID of last MCMIS update.
VMA/ 4 Vehicle make.
VYR/ 4 Vehicle year.
VIN/ 17 Vehicle ID number.
LIC/ 10 License plate number.
LIS/ 2 State code of registration jurisdiction.
REG EFF DATE/ 8 Registration effective date.
REG EXP DATE/ 8 Registration expiration date.
VFC/ 8 Vehicle file create date.
VEH TARG-HIST IND/ 1 Vehicle target/history indicator.
VEH TARG-HIST DATE/ 8 Date of vehicle target/history indicator
(MMDDYYYY).

If PRISM is temporarily unavailable, the sender will receive a Status Message (SM) stating, "TARGET FILE TEMP UNAVAILABLE".

If the Nlets Carrier Status Request (ACQ) message is received between the hours of 11:00pm and 5:00am (CST), the sender will receive a Status Message (SM) stating "AVIS TARGET FILE NOT AVAILABLE FROM 11:00PM - 5:00AM (CST)".

Vehicle Status Response Specifications (AVR)

The requirements for vehicle status responses are described below.

  • There is the possibility that multiple AVR messages will be received in response to the AVQ inquiry.
  • Although more than 1 registration for a vehicle is unusual, the PRISM Target File may have up to 10 registrations for a single vehicle. The last two lines which contain registration related data may be repeated up to 10 times.
  • A maximum of 10 AVR messages may be received.
  • If multiple AVR messages are sent the following notation will be at the end of each message, "PAGE n of n PAGES".
  • If more than 10 vehicle records have been found on the PRISM Target File with the same VIN or LIC/LIS, the following notation will be found at the end of each message, "MATCH LIMIT EXCEEDED, NOTIFY PRISM HELP DESK".
  • When the above notation is received, the recipient is asked to contact the PRISM Help Desk at AAMVAnet (888) 222-8280(AAMVA80) and report the incident.

If PRISM is temporarily unavailable, the sender will receive a Status Message (SM) stating "DESTINATION DOWN, AAMVAnet WILL NOT FORWARD MESSAGE".

If the Nlets Vehicle Status Request (AVQ) message is received between the hours of 11:00pm and 5:00am (CST), the sender will receive a Status Message (SM) stating "AVIS TARGET FILE NOT AVAILABLE FROM 11:00PM - 5:00AM (CST)".

FMCSA Commercial Driver's License Legacy Specifications

This section provides the Legacy format for Commercial Driver's License Query (DQ/KQ) and Commercial Driver's License Response (DR/KR). The DQ/KQ must be sent to the destination CL.

Federal Motor Carrier Safety Administration (FMCSA), has provided their Commercial Drivers License Information System to Nlets users. CDLIS supports the issuance of commercial driver licenses (CDLs) by the jurisdictions, and assists jurisdictions in meeting the goals of the basic tenet "that each driver, nationwide, have only one driver license and one record." CDLIS has operated in all 51 U.S. jurisdictions (50 states and the District of Columbia) since 1992. CDLIS consists of a Central Site and nodes at the Motor Vehicle Agencies (MVAs) of the 51 jurisdictions. The Central Site houses identification data about each commercial driver registered in the jurisdictions, such as:

  • Name
  • Date of birth
  • Social Security Number
  • State driver license number
  • AKA information
  • Current "State of Record" (SOR)

This information constitutes a driver's unique CDLIS Master Pointer Record (MPR). Each MVA houses detailed information about each driver for which it is the SOR. This detailed information, called the driver history, includes identification information, license information, and a history of convictions and withdrawals.

Up until now, Motor Carrier Safety Officers and other law enforcement personnel seeking commercial drivers license detail were required to query CDLIS through a web application provided by FMCSA. While this application is robust, it is generally accessed through a mobile data terminal equipped with a wireless cellular air card. These devices have proved costly and therefore the service has not been available to all whom need it. Nlets and the FMCSA have been working together to provide a solution that allows access by all Nlets users via their existing Nlets connections. Utilizing the existing Nlets Drivers Query Message Keys (DQ/KQ), any and all authorized Nlets users may query the central CDLIS database.

In order to query CDLIS via Nlets your state or agency will need to make two minor modifications to your Nlets DQ message transaction:

  • Regardless of the state of record, the Nlets DQ/KQ header must be destined to the Nlets destination of "CL".
  • A mandatory field of "OLS" has been added to the DQ/KQ transaction. It is in this field that your users will enter the state of record.

Query Formats

The table below describes the legacy prefixes, field sizes, data requirements and a translation of each requirement.

Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
OLN/ 1-20 Alphanumeric Driver's License
Number
NAM/ 4 Alpha
Characters
Name
SEX/ 4 M, F or U Sex
DOB/ 8 ccyy-mm-dd Date of Birth
OLS 2 Alpha
Characters
Issuing State
Commercial Vehicle Information Legacy Examples

Example 1: Carrier Status query by DOT Number to the PRISM file.

ACQ.AZNLETS20.FM.TXT
DOT/111111

Example 2: Carrier Status response.

ACR.FMLIC0000
10:55 11/17/2011 98034
10:55 11/17/2011 99228 AZNLETS20
TXT
 
CARRIER IS TARGETED FOR INSPECTION.
DOT/0111111.
NAM/ACME INC.
DBA/ .
ADR/1234 ANY STREET.
CITY/PHOENIX.ST/AZ.ZIP/85000
CAR TARG-IND/T.MCSIP STEP/11.MCSIP
DATE/20000101.
PAGE/01 OF/01

Example 3: Carrier Status response.

ACR.CL0000000
10:55 11/17/2011 98034
10:55 11/17/2011 99228 AZNLETS20
TXT
 
CARRIER IS TARGETED FOR INSPECTION.
DOT/0111111.
NAM/ACME INC.
DBA/ .
ADR/1234 ANY STREET.
CITY/PHOENIX.ST/AZ.ZIP/85000
CAR TARG-IND/T.MCSIP STEP/11.MCSIP
DATE/20000101.
PAGE/01 OF/01

Example 4: Vehicle Status query by License Plate and License State (LIS).

AVQ.AZNLETS20.FM.TXT
LIC/AAA1111.LIS/AZ

Example 5: Vehicle Status query by VIN.

AVQ.AZNLETS20.FM.TXT
VIN/1AAAA11A11A111111

Example 6: Vehicle Status response.

AVR.FMLIC0000
10:37 11/17/2011 98908
10:37 11/17/2011 09518 AZNLETS20
TXT
 
CARRIER IS TARGETED FOR INSPECTION.
DOT/0111111.
NAM/TRUCKING INC.
DBA/ .
ADR/1234 ANY STREET.
CITY/PHOENIX.ST/AZ.ZIP/85000
CAR TARG-IND/T.MCSIP STEP/11.MCSIP DATE/20000101.
VMA/ KEN.VYR/1990.VIN/1XXXX1X1XX111111.
LIC/AAA1111.LIS/AZ.REG EFF DATE/20010101.REG EXP DATE/20120101.
VEH TARG-HIST IND/T.
PAGE/01 OF/01

Example 7: A Commercial query to CDLIS.

DQ.AZNLETS20.CL.TXT
OLN/1111111111.OLS/AZ

Example 8: A Commercial response from CDLIS.

DR.CLLIC0000
10:00 01/01/2010 41235
10:00 01/01/2010 01236 AZNLETS20
TXT
Query data:
OLN/A11111111.
NAME: JOHN SMITH
RESIDENCE ADDRESS: 1234 ANY ST; PHOENIX,AZ 85000
COUNTRY: United States
DATE OF BIRTH: 1950-01-01
SSN: XXXXX1111
HEIGHT: 550
WEIGHT: 220
EYE COLOR: BLUE
GENDER: MALE
*** DRIVER LICENSE DETAILS ***
DRIVER AUTHORIZATION ID: A11111111
JURISDICTION AUTHORITY CODE: AZ
DRIVER ENDORSEMENT: NONE
ISSUE DATE: 2009-01-01
EXPIRATION DATE: 2014-01-01
DRIVER LICENSE PERMIT QUANTITY: 0
DRIVER LICENSE COMMERCIAL CLASS CODE: A
DRIVER LICENSE NON-COMMERCIAL CLASS: CM
DRIVER LICENSE COMMERCIAL STATUS: LICENSED
DRIVER LICENSE NON-COMMERCIAL STATUS: LICENSED
*** ADDITIONAL INFORMATION ***
FIELD NAME: DriverStateAKA 1
FIELD VALUE: AZ
*** ADDITIONAL INFORMATION ***
FIELD NAME: DriverLicenseAKA 1
FIELD VALUE: 111111111

Example 9: A Commercial query by driver history to CDLIS.

KQ.AZNLETS20.CL.TXT
OLN/1111111111.OLS/AZ

Example 10: A Commercial response by driver history from CDLIS.

KR.CLLIC0000
10:00 01/01/2010 41235
10:00 01/01/2010 01236 AZNLETS20
TXT
Query data:
OLN/A11111111.
NAME: JOHN SMITH
RESIDENCE ADDRESS: 1234 ANY ST; PHOENIX,AZ 85000
COUNTRY: United States
DATE OF BIRTH: 1950-01-01
SSN: XXXXX1111
HEIGHT: 550
WEIGHT: 220
EYE COLOR: BLUE
GENDER: MALE
*** DRIVER LICENSE DETAILS ***
DRIVER AUTHORIZATION ID: A11111111
JURISDICTION AUTHORITY CODE: AZ
DRIVER ENDORSEMENT: NONE
ISSUE DATE: 2009-01-01
EXPIRATION DATE: 2014-01-01
DRIVER LICENSE PERMIT QUANTITY: 0
DRIVER LICENSE COMMERCIAL CLASS CODE: A
DRIVER LICENSE NON-COMMERCIAL CLASS: CM
DRIVER LICENSE COMMERCIAL STATUS: LICENSED
DRIVER LICENSE NON-COMMERCIAL STATUS: LICENSED
*** ADDITIONAL INFORMATION ***
FIELD NAME: DriverStateAKA 1
FIELD VALUE: AZ
*** ADDITIONAL INFORMATION ***
FIELD NAME: DriverLicenseAKA 1
FIELD VALUE: 111111111

Top

Downloads

Download ACQ Schema

Download ACQ Stylesheet

Download ACR Schema

Download ACR Stylesheet

Download AVQ Schema

Download AVQ Stylesheet

Download AVR Schema

Download AVR Stylesheet

Download DQ Schema

Download DQ Stylesheet

Download DR Schema

Download DR Stylesheet

Download KQ Schema

Download KQ Stylesheet

Download KR Schema

Download KR Stylesheet

Top