The SSDQ results provide the States with a comprehensive evaluation on the completeness,
timeliness, accuracy, and consistency of State-reported crash and roadside inspection
data in MCMIS. The State Data Analysis Reports were created to provide additional
detail on activity that may be occurring within a State not immediately apparent
from the measure itself. These reports may support a State's endeavors to identify
improvement strategies for improving their overall State data quality.
The "Complete Record Analysis" report presents an analysis of all FMCSA-required
fields in each crash record submitted to FMCSA. A field is considered complete if
it contains any data. All FMCSA reportable crash records submitted by the States
through SAFETYNET to MCMIS were used in this analysis. The records represent all
interstate and intrastate carriers and include large truck and bus vehicle types.
The fields "report number", "crash date", "crash time"
and "time zone" are pre-populated in SAFETYNET so they are not evaluated
in this report. This report is based upon crash fields required to be completed
in SAFETYNET version 3.6.
A crash record contains information important to identify the carrier and driver,
the location of the crash, if hazardous materials were transported, and the sequential
crash events. All fields are expected to be accurately documented at the time of
the crash event and submitted in a timely manner to FMCSA. Populating fields with
erroneous data does not support FMCSA’s mission to reduce the number of commercial
motor vehicle crashes on our nation’s roadways. Monitoring the completeness
of the crash fields is important to FMCSA and the States. Any significant changes
in reporting should be evaluated further to determine if corrective actions are
needed.
Note: Any field counted as incomplete indicates that the data may not have been
entered into SAFETYNET properly or may not have been collected on the crash report
form.
Definitions
Carrier Information Table - Carrier information in crash records
can only be evaluated for completeness if one of the following conditions is met:
1) carrier type is equal to Interstate or 2) carrier type is equal to Intrastate
and the HM placard field is equal to yes. For all other crash records, the US DOT
# and MC/MX # fields may be left blank if these conditions are not met.
HM Information Table
HM Placard Displayed - If an HM Placard is displayed on a vehicle
(HM placard is marked as ’yes’ in SAFETYNET), then the fields HM Class
#, HM 4-Digit #, HM Name and HM Release were evaluated for completeness.
HM Placard Not Displayed - If an HM Placard is not displayed on
a vehicle (HM placard is marked as 'no' in SAFETYNET), then the fields HM Class
#, HM 4-Digit #, HM Name and HM Release should not contain data. These fields were
evaluated for completeness based upon the value of the HM Placard field.
HM Placard Not Applicable - If a vehicle is not required to display
an HM Placard (i.e. school bus), then the fields HM Class #, HM 4-Digit #, HM Name
and HM Release should not contain data. These fields were evaluated for completeness
based upon the value of the HM Placard field.
Agency, Location, Environment, Driver, Vehicle and Crash Information Table
- All fatal and non-fatal crash records are required to have complete information
for these fields, which are collected at the scene of every crash event.
Event 1, 2, 3 & 4 - A crash record accounts for the first and
up to three subsequent events that happened to the truck or bus involved in the
crash. A minimum of one event is typically recorded per crash event. These events
are entered in sequential order if there are multiple events.
The "Monthly Analysis" report presents an analysis of the driver and vehicle
fields in each crash record reported to FMCSA broken down by 1 month increments
for the 12-month analysis period. For each month, the 10 data fields (driver license
number, driver date-of-birth, driver first name, driver last name, license class,
vehicle identification number, license plate number, vehicle configuration, cargo
body type, and gross vehicle weight rating) are individually analyzed for completeness.
A field is considered complete if it contains any data. The records evaluated represent
all interstate and intrastate carriers and include large truck and bus vehicle types.
All driver and vehicle fields are expected to be accurately documented at the time
of the crash event and submitted in a timely manner to FMCSA. Populating fields
with erroneous data does not support FMCSA's mission to reduce the number of commercial
motor vehicle crashes on our nation's roadways. Monitoring the completeness of the
crash fields is important to FMCSA and the States. Any significant changes in reporting
should be evaluated further to determine if corrective actions are needed.
Note: Any field counted as incomplete indicates that the data may not have been
entered into SAFETYNET properly or may not have been collected on the crash report
form.
Definitions Event Date Range Analyzed (1 month) - One month period of analysis Crash Records Evaluated - Number of crash records analyzed during
one month period # Records - Number of records determined to have complete information
in specified field % Records - Percentage of records determined to have complete information
in specified field
The ’Monthly Analysis’ report presents the number of crash records reported
to FMCSA within 90 days of the crash event broken down by 1 month increments for
the 12-month analysis period. Each month was analyzed for reporting crash records
within the FMCSA standard of 90 days. The data for this report is based on MCMIS
fatal and non-fatal crash records that represent interstate and intrastate carriers
and includes large truck and bus vehicle types.
The graph illustrates the monthly analysis results for crash timeliness. The results
for each month are plotted against the FMCSA standard for reporting crash records
within 90 days - ’Good’ reporting is achieved at 90%. Fluctuations in
reporting may be observed. Any significant changes in reporting should be evaluated
further to determine if corrective actions are needed.
Crash events that occurred during the 12-month analysis period were included in
this analysis. FMCSA calculates the number of days an event takes to be reported
to FMCSA by calculating the number of days from the crash event to the date the
record was sent to MCMIS. The calculation only considers the first time the record
was uploaded to MCMIS; uploading a record more than once to MCMIS does not negatively
impact timeliness.
Definitions Event Date Range Analyzed (1 month) - One month period of analysis # Records with Upload Date > 90 Days - Number of records reported
more than 90 days after the crash event % Records with Upload Date > 90 Days - Percentage of records reported
more than 90 days after the crash event. The percentage is calculated by dividing
the number of records reported more than 90 days by the number of interstate &
intrastate crash records # Records with Upload Date <= 90 Days - Number of records reported
less than or equal to 90 days after the crash event % Records with Upload Date <= 90 Days - Percentage of records reported
less than or equal to 90 days after the crash event. The percentage is calculated
by dividing the number of records reported less than or equal to 90 days by the
number of interstate & intrastate crash records # Interstate & Intrastate Crash Records - Total number of crash
records reported to MCMIS during the 1-month period
The ’Frequency of Record Uploads to MCMIS’ report presents the frequency
of crash records uploaded to MCMIS and highlights how often there were more than
three days between uploads. The data for this report is based on MCMIS crash records
that were added, changed, deleted or rejected during an upload from SAFETYNET to
MCMIS. The records include all interstate and intrastate carriers, and large truck
and bus vehicle types.
The crash timeliness standard is a measurement of crash records reported to FMCSA
within 90 days of the crash event. States that upload crash records to MCMIS on
a consistent basis usually are in compliance with the timeliness standard. Monitoring
the frequency of uploads to MCMIS may improve a State’s crash timeliness measure
in the State Safety Data Quality evaluation.
The graph illustrates the total number of crash record uploads to MCMIS for the
most recent three years. The frequency of days between uploads is captured into
two groups: less than or equal to three days and greater than three days. This summary
data is displayed in the corresponding table below the graph.
The dates of each upload to MCMIS are listed in the second table of this report.
They are organized by month for the most recent 15 months. Rows in the table are
highlighted to indicate the number of days between record uploads to MCMIS was greater
than three days. The number of days between uploads to MCMIS is the difference between
two consecutive upload dates.
Any significant changes in reporting should be evaluated further to determine if
corrective actions are needed.
Definitions - 1st Table Year - Upload year Count of "# Days Since Last Upload" > 3 - Count of
number of uploads with more than 3 days between uploads Count of "# Days Since Last Upload" <= 3 - Count of
number of uploads with 3 days or less between uploads # Uploads per Year - Total number of uploads per year Definitions - 2nd Table MCMIS Crash Upload Date - Date of crash record upload to MCMIS # Days Since Last Upload - The difference in days between two consecutive
upload dates # Crash Records Uploaded - Number of crash records uploaded per
day
The ’Records Reported by Agency and Badge Number’ report presents the
number of crash records that were matched and unmatched to a company registered
in MCMIS by reporting agency and officer badge number. The data for this report
is based on MCMIS fatal and non-fatal crash records for 12 months that represent
interstate carriers and intrastate carriers transporting hazardous material and
includes large truck and bus vehicle types. The reporting agency/badge number analysis
provides supportive information when analyzing the relationship between the number
of matched crash records in MCMIS and the agency/officer responsible for reporting
the crash record information. Note: Agency and officer badge numbers identified
as ’blank’ indicate that the data may not have been entered into SAFETYNET
properly or may not have been collected on the crash report form.
Crash records entered per FMCSA’s "Procedures for Entering Crashes without
Carrier Identification into SAFETYNET" were not included in this analysis.
Definitions Agency - Name of agency recording the crash event information Officer Badge # - Badge # of officer recording the crash event
information # UnMatched Records - Number of records unmatched to a company
registered in MCMIS by agency and badge # % UnMatched Records - Percentage of records unmatched to a company
registered in MCMIS by agency and badge #. The percentage is calculated by dividing
the number of unmatched records by the number of interstate & HM intrastate crash
records # Matched Records - Number of records matched to a company registered
in MCMIS by agency and badge # % Matched Records - Percentage of records matched to a company
registered in MCMIS by agency and badge #. The percentage is calculated by dividing
the number of matched records by the number of interstate & HM intrastate crash
records # Interstate & HM Intrastate Crash Records - Total number of
matched and unmatched crash records
The ’Monthly Analysis’ report presents the number of inspection records
reported to FMCSA within 21 days of the inspection event broken down by 1 month
increments for the 12-month analysis period. Each month was analyzed for reporting
inspection records within the FMCSA standard of 21 days. The data for this report
is based on MCMIS inspection records that represent interstate and intrastate carriers
and includes large truck and bus vehicle types.
The graph illustrates the monthly analysis results for inspection timeliness. The
results for each month are plotted against the FMCSA standard for reporting inspection
records within 21 days - 'Good' reporting is achieved at 90%. Fluctuations in reporting
may be observed. Any significant changes in reporting should be evaluated further
to determine if corrective actions are needed.
Inspection events that occurred during the 12-month analysis period were included
in this analysis. FMCSA calculates the number of days an event takes to be reported
to FMCSA by calculating the number of days from the inspection event to the date
the record was sent to MCMIS. The calculation only considers the first time the
record was uploaded to MCMIS; uploading a record more than once to MCMIS does not
negatively impact timeliness.
Definitions Event Date Range Analyzed (1 month) - One month period of analysis # Records with Upload Date > 21 Days - Number of records reported
more than 21 days after the inspection event % Records with Upload Date > 21 Days - Percentage of records reported
more than 21 days after the inspection event. The percentage is calculated by dividing
the number of records reported more than 21 days by the number of interstate &
intrastate inspection records
# Records with Upload Date <= 21 Days - Number of records reported
less than or equal to 21 days after the inspection event %Records with Upload Date <= 21 Days - Percentage of records reported
less than or equal to 21 days after the inspection event. The percentage is calculated
by dividing the number of records reported less than or equal to 21 days by the
number of interstate & intrastate inspection records #Interstate & Intrastate Inspection Records - Total number
of inspection records reported to MCMIS during the 1-month period
The ’Records Reported by Inspector ID’ report presents the number of
inspection records reported to FMCSA within 21 days of the inspection event by inspection
identification number. The data for this report is based on MCMIS inspection records
for 12 months that represent interstate and intrastate carriers and includes large
truck and bus vehicle types.
The inspection identification number analysis provides supportive information when
analyzing the relationship between the number of inspection records reported within
21 days and the inspector responsible for reporting the inspection record information.
Note: Inspector ID numbers identified as 'blank' indicate that the inspector ID
number data may not have been entered into SAFETYNET properly or may not have been
collected on the inspection report form.
Inspection events that occurred during the 12-month analysis period were included
in this analysis. FMCSA calculates the number of days an event takes to be reported
to FMCSA by calculating the number of days from the inspection event to the date
the record was sent to MCMIS. The calculation only considers the first time the
record was uploaded to MCMIS; uploading a record more than once to MCMIS does not
negatively impact timeliness.
Definitions Inspector ID # - Identification # of inspector recording the inspection
event information # Records with Upload Date > 21 Days - Number of records reported
more than 21 days after the inspection event % Records with Upload Date > 21 Days - Percentage of records reported
more than 21 days after the inspection event. The percentage is calculated by dividing
the number of records reported more than 21 days by the number of interstate & intrastate
inspection records # Records with Upload Date <= 21 Days - Number of records reported
less than or equal to 21 days after the inspection event % Records with Upload Date <= 21 Days - Percentage of records reported
less than or equal to 21 days after the inspection event. The percentage is calculated
by dividing the number of records reported less than or equal to 21 days by the
number of interstate & intrastate inspection records # Interstate & Intrastate Inspection Records - Total number
of inspection records reported to MCMIS during the 12-month period
The ’Records Reported by Inspection Facility Type & Inspection Level’
report presents the number of inspection records reported to FMCSA within 21 days
of the inspection event by the facility type and the inspection level. The first
table presents a summary of all inspections by facility type, and the second table
summarizes the reporting of inspection records by inspection level. The data for
this report is based on MCMIS inspection records for 12 months that represent interstate
and intrastate carriers and includes large truck and bus vehicle types.
The inspection facility type and inspection level analysis provides supportive information
when analyzing the relationship between the number of inspection records reported
within 21 days and the type and location of the inspection event.
Inspection events that occurred during the 12-month analysis period were included
in this analysis. FMCSA calculates the number of days an event takes to be reported
to FMCSA by calculating the number of days from the inspection event to the date
the record was sent to MCMIS. The calculation only considers the first time the
record was uploaded to MCMIS; uploading a record more than once to MCMIS does not
negatively impact timeliness.
Definitions Facility Type - Type of inspection facility - either a fixed site
or at the roadside Inspection Level - The North American Standard Truck Inspection
procedures have identified six levels of inspections: full, walk-around, driver-only,
special study, terminal and radioactive materials # Records with Upload Date > 21 Days - Number of records reported
more than 21 days after the inspection event % Records with Upload Date > 21 Days - Percentage of records reported
more than 21 days after the inspection event. The percentage is calculated by dividing
the number of records reported more than 21 days by the number of interstate &
intrastate inspection records
# Records with Upload Date <= 21 Days - Number of records reported
less than or equal to 21 days after the inspection event % Records with Upload Date <= 21 Days - Percentage of records reported
less than or equal to 21 days after the inspection event. The percentage is calculated
by dividing the number of records reported less than or equal to 21 days by the
number of interstate & intrastate inspection records # Interstate & Intrastate Inspection Records - Total number
of inspection records reported to MCMIS during the 12-month period
The ’Records Reported by County’ report presents the number of inspection
records reported to FMCSA within 21 days of the inspection event by the county the
inspection was conducted in. The data for this report is based on MCMIS inspection
records for 12 months that represent interstate and intrastate carriers and includes
large truck and bus vehicle types. Analyzing the correlation between inspection
timeliness and the county (location) of the inspection event may identify location-specific
reporting issues and target improvement efforts.
Inspection records are uploaded to MCMIS via a State’s SAFETYNET system. All
records are assigned a report number by the State's SAFETYNET system. This report
presents a summary of the inspection records uploaded from the State's SAFETYNET
system and the county the inspection event occurred in. In general, the counties
identified are all within the boundaries of the selected State. However, there are
cases where inspections are coordinated across multiple States. In these situations,
additional counties outside the State boundaries are listed in their report.
Note: county names identified as "blank" indicate that the county data may not have
been entered into SAFETYNET properly or may not have been collected on the inspection
report form.
Inspection events that occurred during the 12-month analysis period were included
in this analysis. FMCSA calculates the number of days an event takes to be reported
to FMCSA by calculating the number of days from the inspection event to the date
the record was sent to MCMIS. The calculation only considers the first time the
record was uploaded to MCMIS; uploading a record more than once to MCMIS does not
negatively impact timeliness.
Definitions County - County name where inspection event occurred # Records with Upload Date > 21 Days - Number of records reported
more than 21 days after the inspection event % Records with Upload Date > 21 Days - Percentage of records reported
more than 21 days after the inspection event. The percentage is calculated by dividing
the number of records reported more than 21 days after the inspection event by the
total number of interstate & intrastate inspection records # Records with Upload Date <= 21 Days - Number of records reported
less than or equal to 21 days after the inspection event % Records with Upload Date <= 21 Days - Percentage of records
reported less than or equal to 21 days after the inspection event. The percentage
is calculated by dividing the number of records reported less than or equal to 21
days after the inspection event by the total number of interstate and intrastate
inspection records # Interstate & Intrastate Inspection Records - Total number
of inspection records reported to MCMIS during the 12-month period
The ’Records Reported by Inspector ID’ report presents the number of
inspection records that were matched and unmatched to a company registered in MCMIS
by inspection identification number. The data for this report is based on MCMIS
inspection records for 12 months that represent interstate carriers and intrastate
carriers transporting hazardous material and includes large truck and bus vehicle
types. The inspection identification number analysis provides supportive information
when analyzing the relationship between the number of matched inspection records
in MCMIS and the inspector responsible for reporting the inspection record information.
Note: Inspector ID numbers identified as ’blank’ indicate that the inspector
ID number data may not have been entered into SAFETYNET properly or may not have
been collected on the inspection report form.
Definitions Inspector ID # - Identification ID # of the inspector recording
the inspection event information # Unmatched Records - Number of records unmatched to a company
registered in MCMIS by inspector # % Unmatched Records - Percentage of records unmatched to a company
registered in MCMIS by inspector ID #. The percentage is calculated by dividing
the number of unmatched records by the number of interstate & HM intrastate
inspection records # Matched Records - Number of records matched to a company registered
in MCMIS by inspector ID # % Matched Records - Percentage of records matched to a company
registered in MCMIS by inspector ID #. The percentage is calculated by dividing
the number of matched records by the number of interstate & HM intrastate inspection
records #Interstate & HM Intrastate Inspection Records - Total number
of matched and unmatched inspection records
The ’Monthly Analysis’ report presents an analysis of the Vehicle Identification
Number of the first vehicle unit in all level 1-6 roadside inspection records reported
to FMCSA. This report only includes inspections conducted by State personnel; Federal
inspections were not included in this analysis. These records are broken down by
1 month increments for the 12-month analysis period. All trailing units are excluded
from this analysis. A VIN is considered accurate if the checksum digit (9th character
of the VIN) matches the checksum algorithm that uses the other 16 characters in
the VIN. Any VIN with invalid characters (i.e. I, O, or Q) or less than 17 characters
is considered to be not valid. For this measure, records with all the same numbers
(i.e. 99999999999999999) are also considered not valid.
Definitions Event Date Range Analyzed (1 month) - One month period of analysis # Vehicle Units Evaluated - Number of Inspection Vehicle records
analyzed during one month period # Records - Number of records in specified category (Invalid /
Valid) % Records - Percentage of records in specified category (Invalid
/ Valid)
The ’Records Reported by Inspector ID’ report presents an analysis of
the Vehicle Identification Number of the first vehicle unit in all level 1-6 roadside
inspection records reported to FMCSA by inspector identification number. This
report only includes inspections conducted by State personnel; Federal inspections
were not included in this analysis. All trailing units are excluded from this analysis.
The data for this report is based on MCMIS inspection records for 12 months that
represent interstate and intrastate carriers and includes large truck and bus vehicle
types. A VIN is considered accurate if the checksum digit (9th character of the
VIN) matches the checksum algorithm that uses the other 16 characters in the VIN.
Any VIN with invalid characters (i.e. I, O, or Q) or less than 17 characters is
considered to be not valid. For this measure, records with all the same numbers
(i.e. 99999999999999999) are also considered not valid. The inspector identification
number analysis provides supportive information when analyzing the relationship
between the number of inspection records with valid VINs in MCMIS and the inspector
responsible for reporting the inspection record
information. Note: Inspector ID numbers identified as ’blank’ indicate
that the inspector ID number data may not have been entered into SAFETYNET properly
or may not have been collected on the inspection report form.
Definitions Inspector ID # - ID # of the inspector recording
the inspection event information # Vehicle Units Evaluated - Number of Inspection Vehicle records
analyzed # Records - Number of records in specified category (Invalid /
Valid) % Records - Percentage of records in specified category (Invalid
/ Valid)
The ’Monthly Analysis’ report presents an analysis of the driver and
vehicle fields in each level 1, 2 and 3 inspection record reported to FMCSA broken
down by 1 month increments for the 12-month analysis period. This report only includes
inspections conducted by State personnel; Federal inspections were not included
in this analysis. For each month, the 6 data fields (driver license number, driver
date-of-birth, driver first name, driver last name, vehicle license plate number,
and gross vehicle weight rating) are individually analyzed for completeness.
A field is considered complete if it contains data and does not meet the following
guidelines for the specific field:
Driver license number
Unknown (and derivatives)
All the same numbers such as 00000000 and 99999999
Most standard keyboard special characters
Exception: hyphens and asterisks are allowed in the middle positions of the field.
Phrases such as: no lic; nolicense; no drivers; novalidlicense; driver; class A,
B, etc.; none; no; not; CDL; nodl; valid; listed; unlisted; available; legible;
No ledgible; unreadable; match; unspecified; passenger; sleeper
Driver date-of-birth - Driver date-of-birth less than or equal to the year
1920.
Driver first and last names
Most standard keyboard special characters
Exception: hyphens are allowed in the middle position of the field and multiple
spaces are allowed throughout the field.
Numbers in the entire field
Phrases such as: Parked / parked car; wrecked; properly; driverless vehicle; unoccupied;
public; not available; No Driver, Driver I, II, III; Driver Jr; Driver Sr; Vandriver;
none; legally; left scene; hit/skip; driver unknown; Not Listed; None Listed; Not
Applicable; Transportation; Transport; Driver Transported; Unattended
Vehicle license number
Unknown (and derivatives)
All the same numbers such as 00000000 and 99999999
Most standard keyboard special characters
Exception: hyphens are allowed in the middle positions of the field.
Phrases such as: No lic; nolicense; no drivers; novalidlicense; driver; class
A, B, etc.; none, no, not;; CDL; nodl; valid; listed; unlisted; available; legible;
No ledgible; unreadable; match; unspecified; passenger; sleeper
All driver and vehicle fields are expected to be accurately documented at the time
of the inspection event and submitted in a timely manner to FMCSA. Monitoring the
completeness of the inspection fields is important to FMCSA and the States. Any
significant changes in reporting should be evaluated further to determine if corrective
actions are needed.
Note: Any field counted as incomplete indicates that the data may not have been
entered into SAFETYNET properly or may not have been collected on the inspection
report.
Definitions Event Date Range Analyzed (1 month) - One month period of analysis # Vehicle Inspections - Number of Inspection Vehicle records analyzed during one month period # Records - Number of records determined to have complete information in specified field % Records - Percentage of records determined to have complete information in specified field
The ’Records Reported by Inspector ID’ report presents the number of inspection
driver records with complete driver information and the number of the individually
analyzed fields (date of birth, license number, first name, last name) with complete
information by inspector identification number. A field is considered complete
if it contains data and does not meet the following guidelines for the specific
field:
Driver license number
Unknown (and derivatives)
All the same numbers such as 00000000 and 99999999
Most standard keyboard special characters
Exception: hyphens and asterisks are allowed in the middle positions of the field.
Phrases such as: no lic; nolicense; no drivers; novalidlicense; driver; class A,
B, etc.; none; no; not; CDL; nodl; valid; listed; unlisted; available; legible;
No ledgible; unreadable; match; unspecified; passenger; sleeper
Driver date-of-birth - Driver date-of-birth less than or equal to the year
1920.
Driver first and last names
Most standard keyboard special characters
Exception: hyphens are allowed in the middle positions of the field and multiple spaces area allowed throughout the field.
Numbers in the entire field
Phrases such as: Parked / parked car; wrecked; properly; driverless vehicle; unoccupied;
public; not available; No Driver, Driver I, II, III; Driver Jr; Driver Sr; Vandriver;
none; legally; left scene; hit/skip; driver unknown; Not Listed; None Listed; Not
Applicable; Transportation; Transport; Driver Transported; Unattended
The data for this report is based on MCMIS inspection records for 12 months. The inspector identification number analysis provides supportive
information when analyzing the relationship between the number of completed inspection
driver records and the inspector responsible for reporting the inspection record
information. Note: Inspector ID numbers identified as ’blank’ indicate that the
inspector ID number data may not have been entered into SAFETYNET properly or may
not have been collected on the inspection report form.
Definitions Inspector ID # - ID # of the inspector recording the inspection event information # Driver Inspections - Number of Inspection driver records analyzed by inspector # # Records - Number of records determined to have complete information in specified field % Records - Percentage of records determined to have complete information in specified field
The ’Records Reported by Inspector ID’ report presents the number of
inspection vehicle records with complete vehicle information and the number of the
individually analyzed fields (vehicle license plate number, GVWR) with complete information
by inspector identification number. A field is considered complete if it contains
data and does not meet the following guidelines for the specific field:
Vehicle license number
Unknown (and derivatives)
All the same numbers such as 00000000 and 99999999
Most standard keyboard special characters
Exception: hyphens are allowed in the middle positions of the field.
Phrases such as: No lic; nolicense; no drivers; novalidlicense; driver; class
A, B, etc.; none, no, not;; CDL; nodl; valid; listed; unlisted; available; legible;
No ledgible; unreadable; match; unspecified; passenger; sleeper
The data for this report is based on MCMIS inspection records for 12 months. The inspector identification number analysis provides supportive
information when analyzing the relationship between the number of completed inspection
vehicle records and the inspector responsible for reporting the inspection record
information. Note: Inspector ID numbers identified as ’blank’ indicate that the
inspector ID number data may not have been entered into SAFETYNET properly or may
not have been collected on the inspection report form.
Definitions Inspector ID # - ID # of the inspector recording the inspection event information # Vehicle Inspections - Number of Inspection vehicle records analyzed by inspector # # Records - Number of records determined to have complete information in specified field % Records - Percentage of records determined to have complete information in specified field
Analysis Descriptions
Print Friendly Version