General Information - 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 (Federal Motor Carrier Safety Administration) Database by sending a Driver License Query (DQ) or Driver History Query (KQ) to destination CL.

Please note that CL requires a DQ/KQ by name to be broken out into it's different fields; i.e. nc:PersonGivenName, nc:PersonMiddleName and nc:PersonSurName
When running a DQ or KQ using OLN with Destination "CL", please use the following element(s):

    If DST = CL
    then OLS needs to be nc:IdentificationJurisdictionNCICLSTACode, where nc is "http://niem.gov/niem/niem-core/2.0"

    If DST <> CL
    Then OLS needs nc:IdentificationJurisdictionText, where nc is "http://niem.gov/niem/niem-core/2.0"

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.

Nlets has worked with FMCSA to include data from the FMCSA Drug and Alcohol Clearinghouse. This data provides the querying agency information regarding a possible drug or alcohol related violation related to the operator of the commercial vehicle. This data will be included in the response and will ONLY be presented if the operator has a violation that might impact their status to operate a commercial vehicle.

This response is only available in a Driver License Query (DQ) or a Driver History Query (KQ) that is sent to the CL destination. The data will be presented in the message as part of the Additional Information group. The field name is “ValidateMessage” and will be followed by a field value similar to “DRUG AND ALCOHOL CLEARINGHOUSE - DRIVER IS PROHIBITED FROM OPERATING UNDER 382.501(A)”. The “ValidateMessage” field will NOT be present if there is no current violation.

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.

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.

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