PRISM Requirements Added as Amendment.docx

Legislation

1. Seek authority to suspend (or revoke) and deny registration if the motor carrier responsible for safety of the vehicle is under a Federal out of service (OOS) order, including authority to deny registration to motor carriers attempting to avoid FMCSA enforcement sanctions by obtaining a new DOT number under a different name and motor carriers under Federal operating authority sanctions.

2. Seek authority to retrieve license plates from carriers whose registration has been suspended based on FMCSA sanctions.

Registration Processes

3. Check carrier safety status before issuing credentials and deny the registration if the motor carrier is prohibited from interstate operations.

4. Check carrier safety status during the registration period on a daily basis, and suspend the registrations of any vehicles assigned to motor carriers under a Federal OOS order or under Federal operating authority sanctions.

5. Check every Vehicle Identification Number (VIN) entered into the IRP system against the PRISM Target File to see if the vehicle is associated with a motor carrier that is under a Federal OOS order or under Federal operating authority sanctions.

6. Update the PRISM-SAFER database daily with vehicle registration information by uploading either a PRISM Vehicle File or CVIEW T0022 transactions.

7. Maintain/update the IRP Status Code within the vehicle registration records, and apply the 950 status code to vehicles that are suspended due to a Federal OOS order.

Data Collection and Forms

8. Identify, collect and maintain the DOT Number and Tax Identification Number (TIN) for the motor carrier responsible for the safe operation of each vehicle being registered.

9. Require all account holders (carriers) to notify their state IRP office within 10 calendar days if the motor carrier responsible for safety (MCRS) changes. This requirement would only apply to account holders that provide a MCRS DOT Number that is not expected to change during the registration year.

10. Validate the DOT Number and TIN before adding any DOT Number and TIN combination to the IRP registration files at the vehicle level (VIN).

11. Print and barcode the motor carrier information on the cab card if the motor carrier responsible for the safety of the vehicle is not expected to change during the registration year.

12. Incorporate PRISM requirements in temporary authority processes.

Communications and Training

13. Collect the number of registration denials and suspensions/revocations due to a motor carrier being identified as under a Federal OOS order, and report to the Division Office on a quarterly basis.

14. Provide assistance to FMCSA Division Office for carrier-related registration information requested.

15. Provide assistance to State motor carrier law enforcement for carrier-related registration information requested.

16. Ensure PRISM training is provided to all appropriate IRP staff, motor carriers, and other interested parties, including training of IRP staff on key FMCSA applications such as MCMIS and Query Central, where applicable.

Law Enforcement Program Requirements

1. Identify vehicles assigned to carriers under a Federal OOS order or operating without operating authority when operating authority is required and take the appropriate enforcement action by placing the vehicle OOS.

2. Identify vehicles assigned to carriers on the PRISM Target File and prioritize those carriers for inspection.

3. In probable cause states, obtain authority to consider as a probable cause the FMCSA OOS condition and/or OOS order against the DOT number of the motor carrier responsible for safety.

4. Seek and implement authority to remove the license plates from vehicles associated with motor carriers that have been suspended for operating under a Federal OOS order.

5. Implement procedures to determine how to correct the unassigned or incorrectly assigned safety events.

6. Ensure PRISM training is provided to all enforcement officers.

Updated: Thursday, March 12, 2015