Legacy Text Examples - Commercial Vehicle Information (ACQ/ACR/AVQ/AVR/DQ/DR/KQ/KR)
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