Monitor your SMS data for errors
Inaccurate Motor Carrier Management Information System (MCMIS) data have the potential to skew your motor carrier’s safety record.
The Compliance, Safety, Accountability (CSA) Safety Measurement System (SMS) relies on current, accurate MCMIS data to derive a carrier’s Behavior Analysis and Safety Improvement Category (BASIC) scores. BASIC scores are updated every month as MCMIS data is uploaded to the SMS.
Since CSA scores are only as accurate as the information going into the SMS, your carrier should assign someone to routinely review its data
What information is used by the SMS?
SMS uses data reported within the past two years by local, state, and federal enforcement officials, including commercial motor vehicle (CMV) accidents and roadside inspections. Elements of a motor carrier’s census data from the MCS-150 are also used in SMS’s algorithms.
Keep your MCS-150 current
Inaccurate motor carrier census data will affect your Unsafe Driving and Crash Indicator BASICs. The BASICs use the following MCS-150 data in their methodology: vehicle miles traveled (VMT), average number of power units (PUs), and types of vehicles (property, passenger
As a result, someone at your carrier needs to monitor your MCS-150 data:
- Is it current?
- Is it updated:
- At least once every 2 years, and
- Whenever there is a change in number of PUs and VMT
Check your roadside inspections
To see all the details surrounding a roadside inspection or crash, such as the driver’s name, your motor carrier must log into the SMS using the carrier view. The public view will provide data, but not all the specifics needed to find patterns.
A month’s worth of reports will show up when the SMS gets updated. If a roadside inspection is uploaded near the end of the month just after the cut-off date, it’s not going to show up in the SMS until the following run, about 30 days later. With delays in processing, it might be 35, 45, even almost 60 days before an inspection report appears on your profile.
If an inspection shows up that your carrier never even heard about, you should use DataQs to request a copy. This typically occurs when the driver fails to turn in the report or lost it, but it could be a carrier misidentification.
Identify incorrect data
Your carrier should examine roadside inspection and crash reports for accuracy. Errors can include incidents that didn’t happen, such as:
- A violation that shows that the driver was placed out of service when it was not the case;
- A violation or crash that was mistakenly assigned to your carrier by the officer; or
- A crash that wasn’t recordable, but is showing up anyway.
There are multiple ways that bad data can get into the SMS, usually involving human error. It shouldn’t be your carrier’s job to watch for those errors, but it is. No one else is going to audit your carrier’s data. If your carrier sees errors, they should be addressed through DataQs challenges. Your CSA scores are on the line.
Finding and addressing patterns
The SMS allows carriers to download their data. Carriers should try to identify patterns and commonalities by sorting the data by driver, vehicle, state, etc. They should also compare the last six months against prior inspection results to identify any spikes.
As you review your data, ask whether most violations involve:
- A handful of drivers
- A handful of vehicles
- Vehicles of a specific type or location
- One facility
- One trainer
- A specific state
When you find a pattern, look for the root cause and address it. If there is no pattern, you may have a systemic problem. Once the problem is corrected, more recent, violation-free inspections will help offset any previous inspections.