Section 408 Safety Data Improvement Program Best Practices

1
Section 408 Safety Data Improvement
ProgramBest Practices Current Activity
2
State of The Union

• Within the current Section 408 Monitoring System
• 102 Projects to improve Crash data
• 7 Projects to improve Driver data
• 26 Projects to improve EMS data
• 10 Projects to improve Roadway data
• 25 Projects to improve Citation data
• 4 Projects to improve Vehicle data

3
e-Crash

• Most e-Crash projects are focusing upon provision
  of road-side software to collect the crash report
  and electronically pass that data to the state
  repository.
• Mixture of home-grown and commercial efforts.
• Various stages of implementation.

4
e-Citation

• Typically tied to an e-Crash effort, but not
  always.
• Focus is usually to provide road-side software,
  tied to other officer duties.
• Key player is the court system and their
  willingness to accept the electronic tickets.
• Major issue is electronic signatures.

5
Court Data Systems

• Not a lot of activity in this area.
• What exists is focusing on transfer of conviction
  data to driver history.
• Major road-block is diversity of courts and their
  internal systems.

6
EMS Systems

• Once again, focus is on road-side software to
  collect EMS Pre-Hospital Run Sheet data.
• Most states focusing upon providing vendors a
  spec for export and certifying vendors.
• Some working on web-based entry systems for
  volunteer services without hardware.
• Major challenge is diversity of providers.

7
NEMSIS Efforts

• Most states have signed the MOA to collect and
  submit EMS data to NHTSA.
• 18 vendors have been approved.
• New standards being developed.
• Reality check Most states are NOT ready and
  have lots to do before they will be able to
  submit ALL runs.

8
State EMS Data Submission
9
MMUCC Efforts

• Almost ALL states are making effort to adopt
  MMUCC into their forms databases.
• Progress will be driven by viable points for
  revision of databases.
• Amazing level of compliance already.
• MMUCC is about to go through another revision.

10
Where are YOU in these areas?

• Do you have any major initiatives?
• Do you have any major problems?

11
Section 408 Safety Data Improvement
ProgramPerformance Measure Guide
12
Section 408 Program Matrix

• Systems
• Crash
• Roadway
• Vehicle
• Driver
• Citation / Adjudication
• Injury Surveillance / EMS

• Performance Areas
• Timeliness
• Consistency
• Completeness
• Accuracy
• Accessibility
• Integration

13
What is a Performance Measure?

• Performance Measures are
• Expressed in terms of a change to a System
• In terms of a Performance Area
• Expressed as something that can be measured

14
What is a Performance Measure?

• Performance Measures impact SYSTEMS
• Crash
• Roadway
• Vehicle
• Driver
• Citation / Adjudication
• Injury Surveillance / EMS

15
What is a Performance Measure?

• Performance Measures impact Performance Areas
• Timeliness
• Consistency / Uniformity
• Completeness
• Accuracy
• Accessibility
• Integration

16
What is a Performance Measure?

• Performance Measures Measure Something
• Days
• Errors
• Missing Fields
• Number of users with access to a system
• In terms of an increase or decrease from a
  Baseline or starting measurement

17
Performance Measure Template

• The state will improve the
• performance area of the
• core system by demonstrating a measured
• increase/decrease in
• what will be measured
• where the baseline level was
• measurement before first year funding and
• goal levels for the future of
• value at the end of 2007,
• value at the end of 2008..

18
Performance Measure Template

• The state will improve the
• timeliness of the
• citation / adjudication by demonstrating a
  measured
• decrease in
• the number of days it takes between a citation
  being adjudicated by a court and it being posted
  to the driver history file (95th percentile)
• where the baseline level was 126 days and
• goal levels for the future of
• 100 at the end of 2007,
• 30 at the end of 2008
• 10 at the end of 2009
• 3 at the end of 2010

19
What is a Milestone?

• A Milestone is a step, phase, or reference point
  in the implementation of a project
• Number of people trained
• Number of PCs purchased
• Release of an RFP
• Award of a contract
• Completion of a project phase

20
What is a Goal?

• A Goal is expressed in terms of the status of a
  Performance Measure
• Annual levels
• Reasonable / Attainable Levels
• Measurable levels

21
Action Item Define P.M.s

• States MUST be able to show Progress to obtain
  second year funding
• Performance Measures are how they will
  demonstrate Progress
• Does the Plan contain P.M.s that are likely to
  show Progress by June?

22
Action Item Update Plans

• Most states should update plan to reflect
  priority, timing now that funding levels are
  known
• Most plans should be updated to clarify
  performance measures / goals.
• Most plans should be updated to modify
  expectations

23
Progress Current Wisdom

• As a minimum, every state should identify at
  least one performance area that will show a
  measurable change in at least one system /
  performance area in order to get second year
  funds
• a pilot project
• a part of the State

24
Other things to worry about

• Model Data Standards
• Has the State provided a list of elements they
  collect for MMUCC NEMSIS?
• Both NEMSIS and MMUCC are slated for updates is
  the State prepared?
• New guidance on MMIRE (Roadway) and
  Citation/Adjudication in the pipeline

25
Section 408 Safety Data Improvement
Program408 Program Monitoring System Overview
26
How are Regions going to

• Track status?
• Monitor state activity?
• Assure that State is on track for 2007?
• Provide technical support to State?

27
NHTSA 408 Monitoring System

• Based upon
• State Plan Documents
• State Progress Reports
• State Systems Inventories
• State MMUCC NEMSIS Reviews

28
NHTSA 408 Monitoring System

• Produces reports on
• Performance Measures
• Milestones
• MMUCC / NEMSIS Content
• Data from Systems Inventory

29
NHTSA 408 Monitoring System

• Depends Upon
• Most current Strategic Plan
• Regular updates to MMUCC NEMSIS content tables
• Regular updates to Systems Inventory
• Likely annual update in 1Q 2007
• Likely expansion of content to reflect TR
  Advisory

30
NHTSA 408 Monitoring System

• State access to reports via web
• FTP//24.123.50.115
• Log In as xx_TRCC where XX is 2-character state
  abbreviation
• Double-click on default.htm for navigation pages
• Region has access to all States in region
• State TR Coordinator can log in and see what is
  on file for his State ONLY.
• Contact kmueller_at_tsass.com for username /
  password issues.

31
NHTSA 408 Monitoring System

• State access to reports via web
• HTTP//www.nhtsa-tsis.net/408
• Public access to basic info on projects
• Clearinghouse
• Private Access to detailed information
• 408 Monitoring System
• Same login and password as FTP site
• Same access as FTP site.
• Maintains archive of all changes

32
NHTSA 408 Monitoring System

• State has OPTION to update all plan information
  on line
• Deficiencies
• Project Descriptions
• Milestones for Project
• Budgets for Project
• Project Contact
• Performance Measures
• Benchmarks / Goals
• Annual status
• Progress Reports by Project
• Uploaded PDFs of core documents

33
NHTSA 408 Monitoring System

• Sample Reports (current) are provided for each of
  your states in the workshop binder.
• Reports will be updated as we receive new
  information.
• Old reports will be archived for comparison

34
NHTSA 408 Monitoring System

• Deficiencies
• Core System exhibiting deficiency
• Performance Area be addressed
• Source of Deficiency
• Description of Deficiency

35
NHTSA 408 Monitoring System

• Project Summary
• Lead Agency
• Project Director
• Basis for Project
• Project Description
• Expected impact
• Project Status
• Milestones
• Budgets
• Progress Reports

36
NHTSA 408 Monitoring System

• Performance Measures
• Core System to be impacted
• Performance Area to be impacted
• What will be measured
• Improvement Increase / Decrease
• Baseline value of measure
• Annual Goals
• Annual Results
• Performance Goal Statement ()
• Annual Differences ()
• Latest Year Results ()
• () generated by system

37
NHTSA 408 Monitoring System

• Data Standards Status
• MMUCC Content Review
• NEMSIS Content Review
• (MMIRE Content Review)
• For each of above
• Number of missing elements ()
• Number of Partial elements ()
• Latest Year Change ()
• () generated by system

38
NHTSA 408 Monitoring System

• Traffic Records System Inventory
• (for each of 17 areas)
• Who manages the system
• Hardware / Software Platform
• How big is it
• How current is it
• Basic system metrics as appropriate
• Tracked from each annual update
• Changes in metrics by year ()
• () generated by system

39
On-Line System Demo
Sample Reports FTP Site www.nhtsa-tsis.net/408

• If technology works

40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
(No Transcript)
45
(No Transcript)
46
(No Transcript)
47
(No Transcript)
48
(No Transcript)
49
(No Transcript)
50
Other Functions

• Upload documents
• Certifications
• Signature Pages
• Attachments
• Reports
• Print Projects
• Print Traffic Records Inventory
• Print MMUCC / NEMSIS Reviews
• Prin Strategic Plan Package

51
Roll-Out Plan

• 2/12-16 - DC 408 Team Training
• By 2/28 Mailing to TR Coordinators
• What we have on file
• Request for TR Inventory Update
• Request for missing MMUCC / NENSIS data
  dictionaries
• OFFER of use of 408 Monitoring System
• User Registration Form

52
Contacts

• Dick Paddock Tech Support Project Lead
• rpaddock_at_tsass.com
• 614.539.4100
• 614.619.0049 cell
• Angie Schmit TR Systems Inventory, MMUCC
  Reviews
• aschmit_at_tsass.com
• 614.214.4100
• Kara Mueller 408 Monitoring System
• kmueller_at_tsass.com
• [phone]
• Tammy Paddock NEMSIS Reviews
• tpaddock_at_tsass.com
• 614.539.4100
• www.nhtsa-tsis.net/workshops