1. 1 How MMUCC, NIEM, VPIC, & EDT Can Help State Crash Data

2. Presenters MMUCC John Siegler, Traffic Records Team Lead, NHTSA John.Siegler@dot,gov NIEM Dan Morgan, Chief Data Officer, United States Department of Transportation Dan.Morgan@dot.gov EDT & VPIC Mike Frenchik, Chief, Safety Systems Management Division, NHTSA Mike.Frenchik@dot.gov 2

3. MMUCC: Model Minimum Uniform Crash Criteria Defines the crash data to be collected NIEM: National Information Exchange Model Protocols for exchanging information VPIC: Vehicle Product Information Catalog Provides vehicle information by decoding VINs EDT: Electronic Data Transfer Interchange of the States’ crash data to NHTSA 3

4. 4 EDT NIEM MMUCC Crash Data Collection Lifecycle

5. Model Minimum Uniform Crash Criteria (MMUCC) John Siegler Ph.D. Traffic Records Team

6. What is MMUCC? A voluntary standard that defines the minimum set of data elements States should collect on crashes. MMUCC recommends linkage to other traffic record systems to expand what is known about the crash, vehicle, roadway and the persons involved. 6

7. History of MMUCC Created cooperatively by NHTSA and GHSA in 1998 and updated in 2003, 2008, and 2012. An expert panel of stakeholders led the development and update process each time MMUCC 4 th edition is currently under review MMUCC 5 th edition will be published in 2017.

8. Why is MMUCC Important? Improves the quality of crash data and, subsequently, the national estimates based on these data. Comprehensive crash data are necessary to determine the most effective countermeasures, which is important for targeting resources so they will have the most impact. Easier to develop and implement software Statewide with uniform data elements and definitions. 8

9. Problem: States Implement MMUCC Differently MMUCC provided a guideline with no implementation guidance – Uniformity of Crash data suffered as States implemented MMUCC differently Common Issues: States combine MMUCC attributes States do not collect all MMUCC attributes 9

10. Solution: “Mapping” State Data to MMUCC Establishes rules and uniform process for States to compare their crash data with MMUCC Recognizes that while State data elements and attributes are different, they can be mapped to MMUCC 10

11. Mapping to MMUCC Example Step 1: Collect both target and source data 11

12. Step 2 Arrange elements/attributes on Mapping Table Target: MMUCC Ability to Map Source: PAR ElementAttributeElementAttribute C11. Weather Conditions 1.Clear C2. Weather Condition (1)No Adverse Condition (Clear, Cloudy) 2. Cloudy (3)Fog 3. Fog, Smog, Smoke(4) Mist 4. Rain(5)Rain 5. Sleet or Hail(6)Snow 6. Freezing Rain or Freezing Drizzle (7) Sleet/Hail 6. Snow(8) Smoke/ Dust 7. Blowing Snow(9)Other 8. Severe Crosswinds(10) Blowing Sand, Soil, Dirt, or Snow 9. Blowing Sand, Soil, Dirt(11) Severe Crosswinds 10. Other 11. Unknown 12

13. Step 3: Do comparison using MMUCC mapping rules Target: MMUCC Ability to Map Source: PAR ElementAttributeElementAttribute C11. Weather Conditions 1.ClearNo C2. Weather Condition (1) No Adverse Condition (Clear, Cloudy) 2. CloudyNo (1) No Adverse Condition (Clear, Cloudy) 3. Fog, Smog, SmokeYes(3) Fog, (8) Smoke/ Dust 4. RainYes(5) Rain 5. Sleet or HailYes(7) Sleet/Hail 6. Freezing Rain or Freezing Drizzle NoN/A 6. SnowYes(6) Snow 7. Blowing SnowNo (10) Blowing Sand, Soil, Dirt, or Snow 8. Severe CrosswindsYes(11) Severe Crosswinds 9. Blowing Sand, Soil, Dirt No (10) Blowing Sand, Soil, Dirt, or Snow 10. OtherNoN/A 11. UnknownNoN/A 13

14. Average Score for States Mapping to MMUCC N=5 14

15. Average Score for States Mapping to MMUCC N=5 Person Data Elements Data Element n=5 P1Name of Person Involved100% P2Date of Birth60% P3Sex100% P4Person Type53% P5Injury Status80% P6Occupant's Motor Vehicle Unit Number100% P7Seating Position70% P8Restraint Systems/Motorcycle Helmet Use71% P9Air Bag Deployed80% P10Ejection92% P11Driver License Jurisdiction51% P12Driver License Number, Class, CDL and Endorsements**57% P13Speeding Related24% P14Driver Actions at Time of Crash29% P15Violation Codes17% P16Driver Distracted By38% P17Condition at Time of the Crash45% P18Law Enforcement Suspects Alcohol Use40% P19Alcohol Test69% P20Law Enforcement Suspects Drug Use53% P21Drug Test70% P22Non-Motorist Number100% P23Non-Motorist Action/Circumstance Prior to Crash30% P24Non-Motorist Actions/Circumstances at Time of Crash28% P25Non-Motorist Location at Time of Crash34% P26Non-Motorist Safety Equipment43% P27Unit Number of Motor Vehicle Striking Non-Motorist60% P28Transported to First Medical Facility By33% Roadway Data Elements Data Element n=5 RL1 Bridge/Structure Identification Number0% RL2 Roadway Curvature0% RL3 Grade0% RL4 Part of National Highway System13% RL5 Roadway Functional Class16% RL6 Annual Average Daily Traffic5% RL7 Widths of Lane(s) and Shoulder(s)7% RL8 Width of Median20% RL9 Access Control0% RL10 Railway Crossing ID0% RL11 Roadway Lighting0% RL12 Pavement Markings, Longitudinal0% RL13 Presence/Type of Bicycle Facility0% RL14 Traffic Control Type at Intersection0% RL15 Mainline Number of Lanes at Intersection0% RL16 Cross-Street Number of Lanes at Intersection0% RL17 Total Volume of Entering Vehicles0% 15

16. Why Map to MMUCC? Identifies priority elements/attributes to change State PAR Crash Database Examines Compatibility of PAR and Crash Database Upon request, NHTSA can help States map their crash data to MMUCC through Crash Data Improvement Program (CDIP) or Go Team 16

17. MMUCC 5th Edition Timeline Spring 2016NHTSA published a Federal Register Notice and GHSA sponsored an on line forum to collect feedback on MMUCC Summer 2016 First panel meeting to discuss changes to MMUCC Sunday Workshop at TRF to discuss initial changes Fall 2016GHSA on line forum to collect feedback on unresolved issues and Federal Docket Second MMUCC panel meeting to finalize changes Spring 2017Publication of MMUCC 5 th edition 17

18. Pending Changes to MMUCC Reformatting MMUCC document Allowing States to decide what data to collect at scene, link, and derive Separate sections for crashes involving – (1) fatalities – (2) large truck and hazardous materials – (3) non-motorists A model crash form and edit checks New data element: “Motor Vehicle Automation Use” 18

19. 19