Slide 1:
State Data Quality Review Program
Improving the Quality of State Crash and Inspection Data Uploaded to MCMIS

Slide 2:
State Data Quality Review Program
Components
1) Select state
2) Preanalysis
3) On-site visit
4) Post Visit
 - Document data reporting processes, observations and recommendations
 - State selects which recommendations to pursue
 - FMCSA technical assistance is available

Slide 3:
State Data Quality Program
Components
1) Select a state
2) Preanalysis
3) On-site visit
4) Post Visit
 - Document data reporting processes, observations and recommendations
 - State selects which recommendations to pursue
 - FMCSA technical assistance is available


Slide 4: How do we decide where to go?
(Graphic showing state map with figure throwing darts at a dartboard)

Slide 5: State Selection Methodology
1) State Safety Data Quality (SSDQ) Results
2) Contribution to the Nation's data quality performance
3) State's willingness to participate


Slide 6: SSDQ Results: June 2006
Crash Accuracy
Crash Timeliness
Pennsylvania Crash Accuracy 18%
Pennsylvania Crash Timeliness 13%
New Jersey Crash Accuracy 9%
New Jersey Crash Timeliness 13%
North Carolina Crash Accuracy 5%
North Carolina Crash Timeliness 5%


Slide 7: State Data Quality Program
Components
1) Select state
2) Preanalysis
3) On-site visit
4) Post Visit
 - Document data reporting processes, observations and recommendations
 - State selects which recommendations to pursue
 - FMCSA technical assistance is available

Slide 8: Preanalysis Completed Before the On-Site Visit
1) SSDQ results (A&I On-line)
2) Crash statistics (A&I On-line)
3) Ad hoc MCMIS reports
4) Crash form analysis


Slide 9: State Data Quality Program
Components
1) Select state
2) Preanalysis
3) On-site visit
4) Post Visit
 - Document data reporting processes, observations and recommendations
 - State selects which recommendations to pursue
 - FMCSA technical assistance is available


Slide 10: Who Participates in an On-Site Visit?
1) Federal Team
  - HQ representation (when possible)
  - MCMIS crash and inspection data
  - Crash form
  - Collection & reporting process
  - SafetyNet use
2) State managers and support staff
  - Crash and inspection data
  - Collection, reporting, training


Slide 11: What Happens During an On-Site Visit?
1) Talk to managers
2) Talk to support staff
3) Use as series of questions to guide the group through the discussions
  - Define collection and reporting process
  - Identify bottlenecks and practices resulting in compromised data quality
 
4) Last day Federal team provides draft list of observations


Slide 12: On-Site Visit: Covers Entire Crash Process
Crash Event ---> Data Collected
Data Collected ---> Input to State System
Data Collected ---> Upload Input to SNET
Input to State System ---> Upload Input to SNET
Upload Input to SNET ---> Upload to MCMIS

Slide 13: Crash Collection Process Compromises Data Accuracy
Complete Crash Form ---> Data Collected
Data Collected ---> Input to State System
Data Collected ---> Upload Input to SNET
Input to State System ---> Upload Input to SNET
Upload Input to SNET ---> Upload to MCMIS

Slide 14: Observation: Crash Collection Process Compromises Data Accuracy
1) No distinction between interstate and intrastate trucks on crash form
2) Crash reports sent to the State with common errors (USDOT#, GVWR, cargo body types)
3) Prior versions of the crash form used

Slide 15: Observation: Crash Reporting Process Compromises Data Accuracy
Complete Crash Form ---> Data Collected
Data Collected ---> Input to State System
Data Collected ---> Upload Input to SNET
Input to State System ---> Upload Input to SNET
Upload Input to SNET ---> Upload to MCMIS

Slide 16: Crash Reporting Process Compromises Data Accuracy
1) Missing data filled-in with incorrect information
2) Conversion of State data elements to SafetyNet elements

Slide 17: Observation: Some Practices and Procedures at the MCSAP Office Compromise Data Quality
Complete Crash Form ---> Data Collected
Data Collected ---> Input to State System
Data Collected ---> Upload Input to SNET
Input to State System ---> Upload Input To SNET
Upload Input To SNET ---> Upload to MCMIS

Slide 18: Observation: Some Practices and Procedures at the MCSAP Office Compromise Data Quality
1) SafetyNet carrier match process not being used before sending data to MCMIS
2) Infrequent census updates to SafetyNet
3) MCSAP office uploads from SafetyNET to MCMIS occurring infrequently

Slide 19: Observation: Not all FMCSA Reportable Crashes are Uploaded to MCMIS
Complete Crash Form ---> Data Collected
Data Collected ---> Input to State System
Data Collected ---> Upload Input to SNET
Input to State System ---> Upload Input To SNET
Upload Input To SNET ---> Upload to MCMIS

Slide 20: Observation: Not all FMCSA Reportable Crashes are Uploaded to MCMIS
1) State and FMCSA CMV definitions do not match
2) Officers trained to identify FMCSA reportable crashes according to State's definition
3) State's definition used to extract FMCSA reportable crashes from State's database

Slide 21: State Data Quality Program
Components

1) Select state
2) Preanalysis
3) On-site visit
4) After the onsite visit
 - Document data process flows, observations and recommendations
 - State selects which recommendations to pursue
 - FMCSA technical assistance is available

Slide 22: After the On-Site Visit: Document Crash Process Flow
Flow chart graphic reviews what steps to follow in documenting a Crash Event

Slide 23: After the On-Site Visit: The State is in control
1) State decides which recommendations to pursue
2) FMCSA Technical Assistance is Available
 - Crash form design to capture FMCSA data elements
 - Officer training for crash form completion
 - SafetyNet training

Slide 23: FMCSA Learns Too
1) Opportunity for the state to give feedback to FMCSA
 - Improve SafetyNet and MCMIS activity log formats
 - SafetyNet training course needed for new user

Slider 24: For more information, please contact
Betsy Benkowski
FMCSA Analysis Division
202-366-5387

Beth Deysher
USDOT Volpe Center
617-494-2570