Vermont Traffic Records Strategic Plan for FFY2018 · 2018-12-21 · Vermont Traffic Records...

State of Vermont Traffic Records Strategic Plan for FFY2019

July 1, 2018

State Traffic Safety Information System Improvement

Vermont Traffic Records Strategic Plan Federal Fiscal Year 2019

This page is intentionally left blank.


July 1, 2018 Page i

Table of Contents

1. Executive Summary ................................................................................................................. 1

2. Traffic Records Coordinating Committee ............................................................................... 2

2.1 Traffic Records Improvement Program Coordinator ....................................................... 2

2.2 TRCC Charter .................................................................................................................... 3

2.3 TRCC Committees ............................................................................................................. 6

2.3.1 Executive Committee ................................................................................................ 6

2.3.2 Technical Committee ................................................................................................ 6

2.4 TRCC Operation ................................................................................................................ 8

2.5 Past TRCC Meeting Dates ............................................................................................... 10

2.6 Future TRCC Meeting Schedule ...................................................................................... 10

3. Progress ................................................................................................................................. 11

3.1 Traffic Records Performance Measures ......................................................................... 11

3.1.1 Citation Completeness– Agencies Deployed .......................................................... 11

3.1.2 Citation Uniformity – Paper vs Electronic ............................................................... 13

3.1.3 EMS Uniformity ....................................................................................................... 17

3.2 Traffic Records Performance Targets ............................................................................. 19

3.2.1 Target for Citation Completeness – Agencies Deployed ........................................ 19

3.2.2 Target for Citation Uniformity – Paper vs Electronic .............................................. 19

3.2.3 Target for EMS Uniformity ...................................................................................... 19

4. TRCC Project Prioritization and Budget ................................................................................ 20

5. TRCC Projects ........................................................................................................................ 21

5.1 AOT Crash Data Reporting System ................................................................................. 21

5.1.1 Contact .................................................................................................................... 21

5.1.2 Lead Agency ............................................................................................................ 21

5.1.3 Status ...................................................................................................................... 21

5.1.4 Project Description ................................................................................................. 21

5.1.5 Schedule .................................................................................................................. 22

5.1.6 Budget ..................................................................................................................... 22

5.1.7 Activity Reporting ................................................................................................... 22

5.1.8 Performance Measures ........................................................................................... 35

5.2 DUI Data Integration ...................................................................................................... 36


July 1, 2018 Page ii

5.2.1 Contact .................................................................................................................... 36

5.2.2 Lead Agency ............................................................................................................ 36

5.2.3 Status ...................................................................................................................... 36

5.2.3 Budget ..................................................................................................................... 36


5.2.5 Schedule .................................................................................................................. 37


5.3 SIREN .............................................................................................................................. 38

5.3.1 Contact .................................................................................................................... 38

5.3.2 Lead Agency ............................................................................................................ 38

5.3.3 Status ...................................................................................................................... 38


5.3.5 Schedule .................................................................................................................. 39

5.3.6 Budget ..................................................................................................................... 39



5.4 Web Crash Auto Populate .............................................................................................. 61

5.4.1 Contact .................................................................................................................... 61

5.4.2 Lead Agency ............................................................................................................ 61

5.4.3 Status ...................................................................................................................... 61


5.4.5 Schedule .................................................................................................................. 61



5.5 Local Road LRS ................................................................................................................ 66

5.5.1 Contact .................................................................................................................... 66

5.5.2 Lead Agency ............................................................................................................ 66

5.5.3 Status ...................................................................................................................... 66


5.5.5 Schedule .................................................................................................................. 66


5.6 TRCC Consultant ............................................................................................................. 70

5.6.1 Contact .................................................................................................................... 70


July 1, 2018 Page iii

5.6.2 Lead Agency ............................................................................................................ 70

5.6.3 Status ...................................................................................................................... 70


5.6.5 Schedule .................................................................................................................. 70

5.6.6 Budget ..................................................................................................................... 71


5.7 End User Crash Data Query Tool .................................................................................... 79

5.7.1 Contact .................................................................................................................... 79

5.7.2 Lead Agency ............................................................................................................ 79

5.7.3 Status ...................................................................................................................... 79


5.7.5 Schedule .................................................................................................................. 79



5.8 DPS E-Citation Implementation ..................................................................................... 84

5.8.1 Contact .................................................................................................................... 84

5.8.2 Lead Agency ............................................................................................................ 84

5.8.3 Status ...................................................................................................................... 84


5.8.5 Schedule .................................................................................................................. 85

5.8.6 Budget ..................................................................................................................... 85



5.9 Horizontal Curve Data Inventory on Local Roads .......................................................... 95

5.9.1 Contact .................................................................................................................... 95

5.9.2 Lead Agency ............................................................................................................ 95

5.9.3 Status ...................................................................................................................... 95


5.9.5 Schedule .................................................................................................................. 96


5.10 Model Inventory of Roadway Elements Collection at Intersections .......................... 98

5.10.1 Contact .................................................................................................................... 98

5.10.2 Lead Agency ............................................................................................................ 98


July 1, 2018 Page iv

5.10.3 Status ...................................................................................................................... 98


5.10.5 Schedule .................................................................................................................. 99

5.10.6 Budget ................................................................................................................... 100

5.11 AOT Statewide Reporting System Upgrades ............................................................ 101

5.11.1 Contact .................................................................................................................. 101

5.11.2 Lead Agency .......................................................................................................... 101

5.11.3 Status .................................................................................................................... 101

5.11.4 Project Description ............................................................................................... 101

5.11.5 Schedule ................................................................................................................ 102

5.11.6 Budget ................................................................................................................... 102

6. Traffic Records Data Standards Compliance ....................................................................... 103

6.1 Model Inventory of Roadway Elements (MIRE) Compliance ....................................... 103

6.1.1 Mire Data Collection Status .................................................................................. 103

6.1.2 Data Collection Methodology ............................................................................... 104

6.1.3 Coordination with Other Agencies ....................................................................... 105

6.1.4 Prioritization of MIRE Fundamental Data Elements Collection ............................ 105

6.1.5 Costs and Resources for MIRE FDE Data Collection ............................................. 106

6.2 Model Minimum Uniform Crash Criteria (MMUCC) Compliance ................................ 107

6.3 National Emergency Medical Services Information System (NEMSIS) Compliance .... 107

7. Traffic Records Assessment Update ................................................................................... 108

7.1 State of Vermont Traffic Records Assessment Update ................................................ 108

7.1.1 Crash Recommendations ...................................................................................... 108

7.1.2 Data Use and Integration Recommendation ........................................................ 108

7.1.3 Driver Recommendations ..................................................................................... 109

7.1.4 Roadway Recommendations ................................................................................ 109

7.1.5 Vehicle Recommendations ................................................................................... 110

7.1.6 Citation/Adjudication Recommendations ............................................................ 110

7.1.7 EMS/Injury Surveillance Recommendations......................................................... 111


July 1, 2018 Page 1

Vermont Traffic Records Strategic Plan

1. Executive Summary

The Vermont Traffic Records Coordinating Committee (TRCC) provides a forum to discuss, plan, and prioritize Vermont Highway Traffic Records data systems. These data systems consist of Crash, Driver, Vehicle, Roadway, Citation/Adjudication, and Injury Surveillance.

On February 2, 2017, the State completed a NHTSA Traffic Records Assessment. This assessment resulted in a set of recommendations intended to guide the State in improving traffic records data systems technologies and related processes. The State’s plans for implementing the recommendations are detailed in Section 7 of this plan.

Over the last two years, Vermont has improved the statewide crash reporting system, the statewide EMS run reporting system, and has made gained considerable ground building the e-Ticket electronic citation system. These three projects include technological improvements and increased adherence to national traffic records standards. Additionally, in FFY19, Vermont plans to deploy the electronic citation system statewide, significantly improving the timeliness and accuracy of citations issued within the State.

This traffic records strategic plan includes projects that improve roadway data (i.e. MIRE Collection at Intersections), crash reporting (i.e. AOT Crash Data Reporting System), EMS run reporting (i.e. SIREN), and the further deployment of the DPS E-Citation Implementation project.

In Section 3 of this plan, NHTSA Model Performance Measures can be found that demonstrate improvements in

1. Citation completeness (as a factor of active electronic citation law enforcement agencies), Citation uniformity (paper vs electronic),

2. EMS run report uniformity to the National EMS Information System V3 standard.

Any grant funds awarded under FAST Act, Section 405c shall be used to make quantifiable, measurable progress improvements in the accuracy, completeness, timeliness, uniformity, accessibility, or integration of data in a core highway safety database.


July 1, 2018 Page 2

2. Traffic Records Coordinating Committee

2.1 Traffic Records Improvement Program Coordinator

Name: Mr. James H. Baraw, MPA Title: Highway Safety Program Coordinator Agency: Vermont Agency of Transportation Office: Office of Highway Safety, Governor’s Highway Safety Program Address: One National Life Drive, 3th Floor City, Zip: Montpelier 05633 Phone: 802-760-9222 Email: [email protected]


July 1, 2018 Page 3

2.2 TRCC Charter

VERMONT

TRAFFIC RECORDS COORDINATING COMMITTEE

CHARTER


July 1, 2018 Page 4


July 1, 2018 Page 5


July 1, 2018 Page 6

2.3 TRCC Committees

2.3.1 Executive Committee

Name / Title Organization Function

John Quinn Secretary and State CIO

Agency of Digital Services Information Technology

Mark Levine, MD Commissioner

Department of Health

Injury Surveillance System

Joe Flynn Secretary

Agency of Transportation

Crash/Roadway

Keith Flynn Chief

Governor’s Highway Safety

Highway Safety

Thomas D. Anderson Commissioner

Department of Public Safety

Law Enforcement

Patricia Gabel State Court Administrator

Court Administrators Office

Citation

Wanda Manoli (Acting Commissioner)

Department of Motor Vehicles

Driver/Vehicle

2.3.2 Technical Committee


Joe Arduca Safety Program Manager

FMCSA FMSCA

Jennifer Pittsley IT Manager

ADS IT

Information Tech

Sgt. Owen Ballinger VT State Police

Vermont State Police –

Traffic Operations

Law Enforcement

James H. Baraw Highway Safety Program Coordinator


Highway Safety

Chris Bell EMS Director



Gabriel Cano Deputy Regional Administrator

NHTSA Region 1

NHTSA

mailto:[email protected]


July 1, 2018 Page 7


Eleni Churchill Sr. Trans Planner

Agency of Transportation Roadway

Evelyn McFarlane VHSA Coordinator

Vermont Highway Safety Alliance

Highway Safety

Barbara Cormier ADS Program Manager

Agency of Digital Services

Information Tech

Leslie Bodette CJTC Trainer

Vermont Police Academy

Law Enforcement

Johnathan Croft AOT Mapping Chief


Roadway

Dan Demille Regional Program Manager

NHTSA Region 1

NHTSA

Mario Dupigny-Giroux Traffic Safety Engineer


Roadway

Donna Earle DMV Chief of Records


Driver/Vehicle

Col. William Elovirta Chief


Law Enforcement/

Commercial Driver/Vehicle Paul White Law Enforcement Liaison


Law Enforcement/

Highway Safety Lt. John Flannigan Lieutenant – VT State Police

Vermont State Police

Law Enforcement

Chelsea Dubie SIREN Data Analyst



Karen Gennette Director, Crime Research Group

Crime Research Inc.

Research

Dean Hamel DPS IT Manager

Department of Public Safety

Information Tech

Jon Kaplan AOT Bike/Ped Coordinator


Roadway


July 1, 2018 Page 8


Deb Laferriere Exec. Assistant

Judiciary Citation

Mike Smith Director of Driver Improvement


Driver/Vehicle

Jeffrey Loewer Chief Information Officer

Vermont Judiciary

Citation

Ture Nelson FHWA Region Administrator

FHWA

FHWA

Charlene Oakley Regional Program Manager

NHTSA Region 1

NHTSA

Laurie Roberts AOT Technician II


Crash

Cindy Taylor Training Coordinator

Vermont Police Academy

Law Enforcement

Roger Thompson Safety Engineer

FHWA

FHWA

Lise Veronneau Business Administrator

Burlington PD

Law Enforcement

Mandy White Crash Technician


Crash

2.4 TRCC Operation

The legislation & Federal Register call for certification that the TRCC continues to operate. Please provide the following information about your TRCC’s structure and operation.

Do you have an executive (policy level) TRCC? Yes

If so, how often does it meet? As Needed.

Do you have a technical (working level) TRCC? Yes

If so, how often does it meet? Quarterly.

Does your TRCC have in place documents that demonstrate that the TRCC meets the following requirements of the legislation & Federal register?


July 1, 2018 Page 9

Yes The TRCC has the authority to approve the Strategic Plan.

Yes The TRCC has the authority to review any of the State’s highway safety data and traffic records systems and to review changes to such systems before the changes are implemented.

Yes The TRCC includes representative from highway safety, highway infrastructure, law enforcement and adjudication, public health, injury control and motor carrier agencies and organizations.

Yes

The TRCC provides a forum for the discussion of highway safety data and traffic records issues and report on any such issues to the agencies and organizations in the State that create, maintain, and use highway safety data and traffic records.

Yes The TRCC considers and coordinates the views of organizations in the State that are involved in the administration, collection and use of the highway safety data and traffic records systems.

Yes The TRCC represents the interests of the agencies and organizations within the traffic records system to outside organizations.

Yes The TRCC reviews and evaluates new technologies to keep the highway safety data and traffic records systems up-to-date.


July 1, 2018 Page 10

2.5 Past TRCC Meeting Dates

Vermont held TRCC meetings on the following dates:

July 19, 2017

October 18, 2017

January 17, 2018

April 18, 2018

2.6 Future TRCC Meeting Schedule

Future TRCC meetings are tentatively scheduled for:

July 18, 2018

October 17, 2018

January 16, 2019

April 17, 2019

July 17, 2019



3. Progress

3.1 Traffic Records Performance Measures

3.1.1 Citation Completeness– Agencies Deployed

Label: C-C-01 Status of Improvement: Demonstrated Improvement Active Status: Active Last Updated: 04-April-2018 Related Project: eCitation Narrative

The measure shows the number and percentage of agencies in Vermont where citations are issued electronically.

The State began piloting its eCitation program in 2016 and continues to rollout eCitation statewide as resources and interfaces become available. Beginning in July 2016, Vermont law enforcement started issuing citations electronically in three of the State’s 95 law enforcement agencies. By the end of March 2018, eCitation has been deployed to 21 of the State’s 95 agencies with 60 equipped vehicles on the system.

Measurements

Start Date End Date Agencies Percent of Total Agencies

April 1, 2015 March 31, 2016 0 0%

April 1, 2016 March 31, 2017 11 12%

April 1, 2017 March 31, 2018 21 22%



Supporting Materials (Backup)

Count of Agencies Where eCitation is Deployed

Month 2015 2016 2017

2018

Jan 0 8 21

Feb 0 11 21

Mar 0 11 21

Apr 0 0 11

May 0 0 11

Jun 0 0 11

Jul 0 3 11

Aug 0 3 11

Sep 0 6 11

Oct 0 6 11

Nov 0 6 11

Dec 0 8 21



3.1.2 Citation Uniformity – Paper vs Electronic

Label: C-CU-02 Status of Improvement: Demonstrated Improvement Active Status: Active Revision Date: 14-May-2018 Related Project: eCitation Narrative

This performance measure shows the percentage of Vermont citations issued electronically versus paper. The State started issuing electronic citations on 7/1/2016.

For the current measurement period, 12.2% of Vermont citations were issued electronically.

Measurements

Start Date End Date Paper Electronic Percent Electronic

April 1, 2015 March 31, 2016 88,926 0 0%

April 1, 2016 March 31, 2017 94,908 1,218 1.2%

April 1, 2017 March 31, 2018 95,198 11,687 12.2%




Citations – April 01, 2015 through March 31, 2016



3.1.3 EMS Uniformity

Label: I-U-02 Status of Improvement: Demonstrated Improvement Active Status: Active Revision Date: 14-May-2018

Narrative

This performance measure is based on the I-U-02 model performance measure.

Vermont will improve the Uniformity of EMS patient care reports as measured in terms of an increase in the number of NEMSIS V3 compliant EMS patient care reports entered into the database or obtained via linkage to other databases.

The state will show measurable progress using the following method: Count the number of NEMSIS V3 reports during the baseline period and compare against the same numbers during the performance period.

This performance measure demonstrates an increase in uniformity of EMS patient care reports during the performance period as compared to the baseline period.

The result is a 100 % increase in uniformity of NEMSIS V3 compliant data reports.

Measurements

Start Date End Date NEMSIS V2 Reports

NEMSIS V3 Reports

NEMSIS V3 Percentage

April 1, 2015 March 31, 2016 88,552 0 0%

April 1, 2016 March 31, 2017 68,731 21,058 23.5%

April 1, 2017 March 31, 2018 0 69,426 100%


NEMSIS V2 Compliant Reports April 1, 2015-March 31, 2016

Year Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Total

2015 7,325 7,434 7,140 7,768 7,706 7,444 7,215 6,723 7,291 88,552

2016 7,513 7,358 7,635





2016 7,227 7,166 7,076 7,666 7,447 7,379 7,068 5,963 6,358 68,731

2017 3,287 1,658 436



2016 18 261 1,043 1,649 21,058

2017 4,698 5,868 7,521



2017 5604 5674 5632 6163 6000 5940 5635 5168 6023 69,426

2018 4656 5819 7112



3.2 Traffic Records Performance Targets

3.2.1 Target for Citation Completeness – Agencies Deployed

The target for citation completeness for agencies deployed:

Start Date End Date Agencies Percent of Total Agencies

April 1, 2018 March 31, 2019 25 25.3%

3.2.2 Target for Citation Uniformity – Paper vs Electronic

The target for citation uniformity as a percentage of electronic reports:

Start Date End Date Percent Electronic

April 1, 2018 March 31, 2019 18%

3.2.3 Target for EMS Uniformity

The target for EMS Uniformity has reached maximum performance for NEMSIS V3 compliance.

Start Date End Date NEMSIS V3 Percentage

April 1, 2018 March 31, 2019 100%



4. TRCC Project Prioritization and Budget

The following FFY2019 projects were reviewed by the Vermont GHSP and forwarded to the Secretary of the Agency of Transportation for his approval.

Projects for FFY2019 Budget

AOT Crash Data Reporting System 150,000

SIREN 207,721

Model Inventory Collection (Intersection) 179,000

DPS E-Citation Implementation 505,140

Traffic Records Consultant 65,000

Department of Liquor Control – DUI Data Integration 17,360

Total $1,124,221



5. TRCC Projects

5.1 AOT Crash Data Reporting System

5.1.1 Contact

Ms. Mandy White Title: Crash Technician Agency: Vermont Agency of Transportation Office: Highway Research Address: 1 National Life Building, Drawer 33 City, Zip: Montpelier 05633 Phone: 802-595-9341 Email: [email protected]

5.1.2 Lead Agency

Vermont Agency of Transportation

5.1.3 Status

Active

5.1.4 Project Description

This is the base project for ongoing enhancements for the crash data interface. This project will result in the improvement of the crash data production process and address uniformity, integration and timeliness of the crash data. These enhancements will benefit both law enforcement users and data analysts. A portion of this project will be to review the uniform crash report form and make necessary changes with the Model Minimum Uniform Crash Criteria (MMUCC) as a guide. A second component to this project is to add additional states to the auto population portion of Web Crash. This will increase timeliness and integration by expediting at scene time and validating the data point of entry. Another portion of this project would be to create a crash collection stand-alone client application for law enforcement to create and submit reports from the field. It will address the poor internet connectivity in many rural parts of the state, allowing officers to continue with their crash reporting when connectivity is lost and submit later when connectivity is re-established. A contracted vendor will develop strategies to address need for hardware/software, user accounts, task framework, address schema requirements, research the costs associated with building and implementing a Crash Client app and outline an implementation plan. The Client Application was a recommendation in both the Vermont 2012 Crash Data Improvement Program (CDIP) review as well as in the 2012 and 2016 Traffic Records Assessments. This feature will provide for improved timeliness in reporting, per the CDIP and TR Assessments. Finally, a data bridge between SIREN and Web Crash is planned. This bridge will improve data linkage and allow for review of outcomes across the datasets.




Problem Statement: The online data entry system for law enforcement crash reporting and the VTrans (Vermont Agency of Transportation) legacy data records system require periodic evaluation for upgrades and improvements.

Countermeasures: Data improvement recommendations indicated in the 2012 & 2016 TR Assessment.

Strategies: Hardware and software upgrades and development of a plan with recommendations to improve run-time field loss of law enforcement connectivity in rural areas of the state.

Goals: To improve uniformity of the Crash data production process and applications and to receive the crash data in a more timely manner.

5.1.5 Schedule

October 1, 2018 – September 30, 2019

5.1.6 Budget

Budget Source Budget Year Total Budget

NHTSA 405c 2019 $150,000.00

5.1.7 Activity Reporting

Report Start

06-07-2011

Report End

06-07-2011

Provided By

Mary Spicer

Activity Data Collection – Revised Uniform Crash Report form necessitated update to Web Crash data entry forms/screens. Included new data fields and changes to audits. Also, included is a Fatal crash alert notification for FARS staff, and informational link for new features, IE 8 compatibility resolution, and additional SafetyNet features.

Interfaces – Middlebury PD interface work started. Implemented web services tool for large truck/bus carrier information. Implemented Google map tool for GPS coordinate verification.

Analysis Tools – Standard and Ad-hoc reporting capabilities built into Web Crash. Provided other State agency personnel with access to crash database via Citrix.

Problems Data Collection – More of a challenge is getting al law enforcement on board. To date, we have all Vermont State Police and 62 of the 65 local law enforcement agencies using web crash.

Interfaces: After much work by the consultant and DPS IT staff, the powers at DPS decided to discontinue the Spillman interface work.

Analysis Tools – Encouraging law enforcement to sue the reporting tools. The data available for Web Crash users only trend back to the date they started entering electronically. Paper-based agencies do not have access to the reporting tools.

Plans Data Collection – Complete current contract deliverables: VIN lookup implementation plan, Crash Diagramming tool implementation plan, revise LRS tool, software changes due to modifications, and IT Training on system components. VT will be submitting a



Report Start

06-07-2011

Report End

06-07-2011

Provided By

Mary Spicer

request to the 2012 legislature for a statue that requires law enforcement to submit crash reports electronically.

Interfaces – Complete Middlebury interface in FFY2011. Interface with EMS SIREN project for EMS and hospital run information. eCitation project is in its infant stage in Vermont. Interfacing to eCrash (Web Crash) is an activity of the eCitation project. (eCitation work is a few years down the road.)

Analysis Tools – Continue to provide for special reports as requested by law enforcement and data and/or software programming issues/changes.

Working towards a web query tool to provide for public access to crash data and access to all law enforcement agencies so trending analyses can be performed. This tool to be addressed in a new project title for FFY2012: “End User Crash Data Query Tool.”

Comments This project has absorbed the previously named “Crash Data Linkages to Other Sources” project and the web-based reporting features activities of the previously named “Analytical Reporting Capability.” (The public web app query tool has been given its own project name, “End User Crash Data Query Tool,” and is the in the FFY2012 project list.)

Report Start

07-01-2011

Report End

09-30-2011

Provided By

Mary Spicer

Activity Incorporated Uniform Crash Report form changes and made related changes to Web Crash and Vermont Crash System Group.

Added new law enforcement agencies to the Web Crash Users Group.

Completed work on automatically populating Commercial Vehicles data fields in Web Crash.

Problems Vermont has all but three local law enforcement agencies using the Vermont Web Crash to submit electronic motor vehicle crash reports. The three remaining police departments may need to be persuaded to sue Web Crash. The challenge is to determine the best way to persuade these departments to begin using Web Crash (legislation, hardware, …)

Plans Continue work on VIN verification at point of entry and use for automatically populating vehicle information.

Continue discussions on building interfaces to reduce data reporting redundancies and disseminating crash data throughout the State of Vermont:

Burlington Police RMS Vermont Department of Health EMS system (Siren) Vermont Department of Public Safety E-Citation project Vermont Department of Public Safety Crime Mapping project



Report Start

07-01-2011

Report End

09-30-2011

Provided By

Mary Spicer

Continue consultant training (Deep River LLC) of Vermont Agency of Transportation IT staff on VCSG and CDCI.

Continued research to determine the best crash scene diagramming tool for Web Crash.

Begin work to incorporate a map interface into Web Crash for identifying crash location.

Report Start

10-01-2011

Report End

12-31-2011

Provided By

Mary Spicer

Activity Completed work to make Perceived Race Data Mandatory on the UCR.

Compiled and posted crash counts to SHSP web page.

Problems Vermont has all but three local law enforcement agencies using Vermont Web Crash to submit electronic motor vehicle crash reports. The three remaining police departments may need to be persuaded to use Web Crash. The challenge is to determine the best way to persuade these departments to begin using Web Crash (legislation, hardware, …).



Burlington Police RMS Middlebury Police Department VTRANS Highway Safety Staff: layer crash data over safety project information Vermont Department of Health EMS system (Siren) Vermont Department of Public Safety E-Citation project Vermont Department of Public Safety Crime Mapping project

Continue consultant training (Deep River LLC) of Vermont Agency of Transportation IT staff on VCSG and CDCI.


Continue work to incorporate a map interface into Web Crash for identifying crash location.

Evaluate new LRS VCSG wizard developed by consultant.

Summarize Standard Report changes in VCSG and provide to vendor for estimate and final work.



Report Start

01-01-2012

Report End

03-31-2012

Provided By

Mary Spicer

Activity Completed interface to Middlebury Police Department RMS (IM) to submit crash data electronically to VAOT.

Completed consultant training (Deep River LLC) of Vermont Agency of Transportation IT staff on VCSG and CDCI.

Completed new LRS VCSG wizard.

Completed summary of Standard Report changes in VCSG and provide to vendor for estimate and final work.




Burlington Police RMS VTRANS Highway Safety Staff: layer crash data over safety project information Vermont Department of Health EMS system (Siren) Vermont Department of Public Safety E-Citation project Vermont Department of Public Safety Crime Mapping project


Continue work to incorporate a map interface into Web Crash for identifying crash location.

Report Start

04-01-2012

Report End

06-30-2012

Provided By

Mary Spicer

Activity E-Citation: Reviewed consultants LE Needs and Expansion of System reports. Provided comments to DPS Project Manager.

Participated in the 2012 Traffic Records Assessment (May 2012).

Crash data count updates posted to SHSP web page: Opening page Fatalities and Fatal Crash counts updated as information comes in. Data charts updated quarterly.

Middlebury PD interface is done and functioning. Reports being exported from their IMC/TriTech system to Web Crash.

Map creator tool for LDE within Web Crash: Reviewed beta and provided feedback



Report Start

04-01-2012

Report End

06-30-2012

Provided By

Mary Spicer


Plans VTrans Highway Safety staff: layer crash data over safety project information as well as analyses for before/after crash reduction.

DPS, Crime Mapping System: layer crash data over crime data.

VTrans Training Center will be incorporating crash stats into their Defensive Driving class.

Assisting GHS office with data tables and charts to support various report due dates and initiatives.

Web Crash will export crash data that Spillman can accept. The interface will be built this way because Web Crash ha s100% of the Uniform Crash Report form data items and Spillman only 50% (to the best of my knowledge to date). According to the Crash project consultant, we should be able to pick up where we left off. Original reports export test was successful. We will pick up with export test of updated reports.

Summarized Crash standard reports: We have identified some standard reports needing updating and some new reports needed. Consultant working on the udpats.

Burlington PD interface: Awaiting BPD’s contact for readiness to address crash data. We had expected contact in May, but believe they are dealing issues with their new CAD/RMS system.

VIN and Driver information: Working with DMV and DPS IT. Looks like we may be able to set up a virtual LAM at VTrans and have access via message switch at DPS.

The crash report consultant is working on a Map Creator tool for the Ad-hoc reporting module.

Comments Crash Data Improvement Program (CDIP) review postponed due to workload issues. Awaiting new date options from NHTSA.

Report Start

07-01-2012

Report End

09-30-2012

Provided By

Mary Spicer

Activity Completed work on Map Creator tool for the Ad-hoc reporting module.

Completed updates to Standard Reports and Ad-hoc reporting tool in VCSG.

Provided GHS office with data table updates for their Highway Safety Plan for NHTSA.

Put out an FI for the Crash Diagram Tool.

Completed the Law Enforcement Web Crash Mapping Query Tool.



Report Start

07-01-2012

Report End

09-30-2012

Provided By

Mary Spicer

Problems Vermont has all but four local law enforcement agencies using Vermont Web Crash to submit electronic motor vehicle crash reports. The four remaining police departments may need to be persuaded to use Web Crash. The challenge is to determine the best way to persuade these departments to begin using Web Crash (legislation, hardware, …).

Plans Planning for Crash Data Improvement Program (CDIP) review for October 2-4, 2012.

Continuing research on mapping crime and crash data.

Burlington PD interface: Awaiting BPD’s contact for readiness to address crash data. We had expected contact in May, but believe they are dealing issues with their new CAD/RMS system.

Continuing work on registration and Driver information interface with DMV and DPS IT. Appears access via message switch at DPS is possible.

Scheduling a conference call with the University of Connecticut (UCONN) to discuss how UCONN built the Connecticut Crash Data Query Tool.

Developing an end use training manual for the Law Enforcement Crash Mapping Query Tool.

Report Start

10-01-2012

Report End

12-31-2012

Provided By

Mary Spicer

Activity Completed Crash Data Improvement Program (CDIP) review.

Held conference call with the University of Connecticut (UCONN) to discuss how UCONN built the Connecticut Crash Data Query Tool.

SHSP/VHSA Data Team developed draft SOW for Web Query Tool.

Problems Vermont has all but four local law enforcement agencies using Vermont Web Crash to submit electronic motor vehicle crash reports. The four remaining police departments may need to be persuaded to use Web Crash. The challenge is to determine the best way to persuade these departments to begin using Web Crash (legislation, hardware, …).

Plans Continuing work on registration and Driver information interface with DMV and DPS IT.

Continuing research on mapping crime and crash data.

Continuing work on an end user training manual for the Law Enforcement Crash Mapping Query Tool.

Continuing work on the Spillman RMS interface to Web Crash.

Continuing work on the Burlington PD Valcour RMS interface to Web Crash.

Continue research on a Crash Diagramming tool for Web Crash.



Report Start

01-01-2013

Report End

05-31-2013

Provided By

Mary Spicer

Activity Regional Safety Forum: Presented at the April 17th (#2, Lamoille and Washington Counties) and preparing for the May 29th (#3, Addison and Rutland Counties) forum.

Included monthly fatality count reporting to NSC.

E-Citation: RFP advertised and DPS PM received questions. PM requested I review the questions and provide response by May 15, 2013.

Web Crash Training, Policy Academy: Mandy participated in a successful training session at the Academy.

Diagramming Tool: Bob has submitted an RFI and received some information.

Testing Deep River (DR) put in place possible solution for SAVE issue.

Problems Auto Population tool (separate project under 408): Awaiting approval.

Only two PDs not using Web Crash: Montpelier and Bristol. Word is that Montpelier will move to BPD’s Valcour CAD/RMS. Not sure if this means Montpelier will use the Web Crash link, but I will follow up with Chief Facos to confirm.

Plans Responding to requests for crash data: LE, locals, public.

Working with data users and VTrans IT to establish a public web app query tool. (Separate project, partially funded with 408 money.) Bids received and the financials are currently under review by VTrans Audit Section. Once Audit blesses, the review team can evaluate the proposals.

Spillman Interface – Awaiting information from DPS.

Montpelier PD – Confirm use of Web Crash via Valcour.

Burlington PD Interface – Ongoing work with BPD and consultant, Crosswind.

Integrate diagramming tool with Web Crash.

Build virtual LAN at VTrans to access vehicle and operator data via DPS message switch.

Assure all documentation is completed.

Contract PS0029, amendment #2: Standard monthly maintenance Unanticipated maintenance needs.

Contract PS0029 proposed amendment #3:



Report Start

06-01-2013

Report End

08-01-2013

Provided By

Mary Spicer

Activity Deep River contracts are renewed. Several PDs with Valcour are now fully live with interface.

Problems One detail related to VTrans server upgrade causing some problems in the field – a DII vendor (C2) will take a look at certain users current issues with Crash interface.

Plans Mary hopes to have an opportunity to fully review the CDIP recommendations and assess where things are. Mary has asked that she and Many have read-only access to Valcour to be able to help with user questions/problems.

Report Start

08-01-2013

Report End

10-31-2013

Provided By

Mary Spicer

Activity Mandy White led a review of the changes to the crash report form discussed previously, reminding everybody that the purpose of these changes is creating as much clarity as possible in the form so that users of the data will have a greater likelihood of consistent information. The group discussed/approved each item as we went through the document.

Plans Implement changes to UCR and provide office training.

Report Start

11-01-2013

Report End

02-01-2014

Provided By

Mary Spicer

Activity VTrans Crash Vendor providing ongoing tech support.

Mary reported that the volume of crash reports is 99% electronic.

There is access now to non-injury crashes from crime reports data to analyze and post to SHSP site.

Improved upon data completeness with a tool to include non-reportable motor vehicle crash incidents.

Plans Complete Burlington PD interface fully executed cooperative agreement.

VTrans Crash Vendor working with TR IT coordinator, DPS IT, and CPI on installation of message switch at DPS for auto population feature.

Report Start

03-01-2014

Report End

06-01-2014

Provided By

Mary Spicer

Activity To date, 9% of the volume of crash reports are received electronically via Web Crash. Still only one law enforcement agency not using Web Crash.

All “Non-Reportable” crash incidents included in the Crash database.

Had preliminary discussions between VTrans Crash vendor and BPD’s Valcour vendor re: data flow and additional data items.



Report Start

03-01-2014

Report End

06-01-2014

Provided By

Mary Spicer

Vendor built “Impaired” report for SHSP based on new definition.

Plans Continue work on CDIP and TR Assessment comparison.

VTrans Crash Vendor working with TR IT coordinator, DPS IT, and CPPI on installation of message switch at DPS for auto population feature.

Reviewing information obtained at TRF this year regarding diagramming tools. Staff also “surveying” local PDs on use and need for new drawing tool.

Report Start

06-02-2014

Report End

07-20-2014

Provided By

Mary Spicer

Activity UCR done and running; paper forms are still flying out the door not sure why. A new standard report being created to be HSIP compliant.

Report Start

07-21-2014

Report End

09-17-2014

Provided By

Mary Spicer

Activity Much of the UCR work has been completed.

Some of the UCR form changes which were delayed pending approval have been approved, so that the completion work will need to carry forward into FY15. The amount carrying forward is a total of $119,030. Approved.

Report Start

09-18-2014

Report End

11-12-2014

Provided By

Mary Spicer

Activity ADFS (security umbrella for Microsoft applications – single log-in for multiple applications) upgrade is still ongoing; Hartford is field-testing, generally positive – out of state from NH an issue, but the issue is being addressed for both NH and NY. VSP has too few crashes to adequately test; looking for some additional placements. Need to get some urban sites; ultimately scanning of license plates might be a good solution potentially for eCitation too.

Report Start

11-12-2014

Report End

01-21-2015

Provided By

Mary Spicer

Activity Mary will be sending an email to TRCC for final go ahead of the UCRF changes as previously approved. Bristol PD: Chief agreed to use Web Crash and requested training session in Bristol. Morristown continues to waffle between electronic reporting and paper reporting.



Report Start

01-22-2015

Report End

04-22-2015

Provided By

Mary Spicer

Activity Pushing out testing of Web Query tool, secure sign on to Web Crash and auto-population (DMV) improvements/adjustments are ongoing (due to updating issues in an older system started in 2008).

Report Start

04-23-2015

Report End

07-22-2015

Provided By

Mary Spicer

Activity AOT Crash Data Reporting System is continuing with upgrades to the platform behind the scenes. As part of the changes that will result, Mary Spicer requested that proposed changes for the Uniform Crash Report be submitted in advance of the scheduled October TRCC meeting so that decisions can be finalized at that meeting. Similar to the last UCR review process, a date will be set by which submissions will be due to Mary Spicer and Mandy White. All proposals will be scanned into a single document and posted to the Sharepoint site prior to the meeting.

Report Start

07-23-2015

Report End

10-21-2015

Provided By

Mandy White

Activity Mandy White gave an update on the AOT Crash Data Reporting system. The Active Directory Federation Services (ADFS) is nearly complete. It has been rolled out to AOT and testing in that environment has started. It’s almost ready to test with super users and DPS users. Mandy will talk to the barrack clerks who do a lot of these on a near-daily basis. Mandy will schedule a meeting with Valcour to work with them on the details for ADFS. Bristol PD is now submitting crashes to WebCrash. The auto population feature is a huge success. They have access to DMV data from Vermont, New York, and Massachusetts. Mandy started training the VSP troopers to enter from their cars. The troopers are very receptive; however, Mandy will be putting together a list of their concerns. Bob Thigpen mentioned that the application has been upgraded from the first version of .Net (nine years ago) to the most current version. This should take care of problems with users getting cut off on the old system.

Report Start

10-22-2015

Report End

01-20-2016

Provided By

Mandy White

Activity Working to move all internal crash applications onto Web Crash. This is a heavy coding project that is nearly complete. We are also working on expanding the new Web Crash to DPS with a handful of officers, troopers and clerks testing first. Coming in early February. Then we will expand to Valcour users. Mandy trained Williston VSP as well as the Traffic Operations at VSP to use Web Crash at the trooper level. Suggestion to make an email pre-defined with the data needed to email operators instead of having to fill out a paper form. Implementing a CDIP recommended report that will show crash reporting timeliness by reporting agency.



Report Start

10-22-2015

Report End

01-20-2016

Provided By

Mandy White

Finalized three updates to the form. This includes adding Vehicle Color, Saliva Test to the Drug Test list and we will be adding a place of collecting email on the paper forms.

Report Start

01-21-2016

Report End

04-20-2016

Provided By

Mandy White

Activity Bob Thigpen gave an update; Crash Data is now running on 3.0. Have rolled out the upgraded application for the Spillman users. Still working on how to accommodate the Valcour Users, have options.

Report Start

04-21-2016

Report End

07-13-2016

Provided By

Mandy White

Activity Mandy White gave the following update:

Began to roll out New Web Crash. Two VSP barracks are fully switched over to New Web Crash as well as 6 barracks clerks and 2 municipal police departments. Nine departments have been contacted but only two have responded as of the date of this report.

Pulled together the bicycle/pedestrian changes to the crash report form as well as the email and vehicle color changes. These will be presented to Appriss for next steps. Once we decide the right placement & TRCC approves the changes will be sent to the VCI for paper form changes.

Contract Amendment 6-time extension was approved.

Bob Thigpen has come up with a way to get the Valcour users back to single sign on, but we need the support of the Valcour board/users. Working on an email to their key players.

Report Start

07-14-2016

Report End

10-11-2016

Provided By

Mandy White

Activity Bike/Ped changes were approved and finalized. Awaiting a good time to print new forms. New Web Crash is fully implemented. Crash RFP is final and posted by DII. VSP training continues.

Report Start

10-12-2016

Report End

01-18-2017

Provided By

Mandy White

Activity Crash Forms were finalized and sent to the printer. Once I have the word they have arrived at DMV we will update Web Crash and I will send out a memo explaining the changes to law enforcement. The significant changes are the collection of Alcohol/Drug information for all drivers, pedestrians & bicyclists. We also needed to



Report Start

10-12-2016

Report End

01-18-2017

Provided By

Mandy White

move the injury codes to the KABCO scale for federal reporting by July 1, 2017 so this was the best time to do so. Only two of the existing 7 codes changed. Incapacitating Injury changed to Suspected Serious Injury and Non-Incapacitating Injury will now be Suspected Minor Injury. The Crash RFP proposals received & reviewed. We have chosen a vendor and references have been checked. The next step is to do the negotiations with the vendor. Reached out to Derby, Royalton and Westminster barracks to get Web Crash set up for troopers. I have already begun training Royalton VSP and will be setting up Westminster very soon. I have been receiving emails from individual troopers looking to use the program, so it only makes sense to set them up by barracks. I also have a training scheduled with Essex PD for later this month. Sat down with a Valcour representative and we went through the program to see if there are any data elements that could be added to the export to Crash using the interface between the two. We came up with a short list that I need to put together

Report Start

01-18-2017

Report End

04-19-2017

Provided By

Mandy White

Activity Form changes were implemented and forms were provided to law enforcement. The online manual is nearly complete. A number of other updates to Web Crash have also taken place. The Map tool was upgraded to allow law enforcement the ability to autofill nearly all of the location box based on the location selected in the map. The Search function “Full Text Search” was refined to only search “Last Name/Street”. I have trained Royalton VSP, Westminster VSP and will finish training Derby VSP on April 21, 2017. I also trained Essex PD.

Report Start

04-19-2017

Report End

07-19-2017

Provided By

Mandy White

Activity

The Crash RFP is still in negotiations.

Public Query Tool – I went to Williston VSP to show the staff there how to use the new version of the public query tool. We also spent time going over the reporting tools in Web Crash to also help them with requests for information.



Report Start

04-19-2017

Report End

07-19-2017

Provided By

Mandy White

Message Switch – our new vendor is working through the notes on how to add new states to the message switch. I have also contacted DPS IT about adding a few more states.

Chief’s & Sheriff’s Meeting – awarded timeliness award based on first submittal date and crash date. There were 17 municipal departments that were recognized for submitting their crashes in an average of less than 20 days.

Traffic Incident Management (TIM) Workshop Attended – There is a desire to collect data related to the crash scene and whether a crash is related to another crash (secondary crash).

HSP Data – Data & maps created for the Governor’s Highway Safety Program. The crash data is instrumental in the awarding of grants by the program.

Report Start

07-19-2017

Report End

10-11-2017

Provided By

Mandy White

Activity The Crash RFP is still in negotiations. Conducted Web Crash trainings at Essex PD, New Haven VSP & Shaftsbury VSP. Waiting on Crash Vendor to get DPPA approval so they can work with DPS on adding another state to our message switch.

Report Start

10-11-2017

Report End

01-17-2018

Provided By

Mandy White

Activity The Crash RFP is still in negotiations. Conducted Web Crash trainings at Killington PD, Rutland VSP & Derby VSP. Heard from the crash vendor that they will not sign the DPPA form so they can work with DPS on adding another state to our message switch.



5.1.8 Performance Measures

Crash Timeliness

Label: C-T-01B Status of Improvement: No Improvement Active Status: Active Last Updated: 3-May-2018 Narrative

This performance measure is based on the C-T-01B model.

Vermont will improve the Timeliness of the Crash system as measured in terms of a Decrease of:

The average number of days from the crash date to the date the crash report is entered into the crash database within a period determined by the State.

The state will show measurable progress using the following method: The average number of days from the crash date to the date the crash report is entered into the crash database using a baseline period of April 1, 2016 to March 31, 2017 and a current period of April 1, 2017 to March 31, 2018.

Numbers in this performance measure represent all crashes entered into the state crash database from all state reporting agencies.

There were 10,371 crash reports during the baseline period with an average timeliness of 27.89 days. There were 9,901 crash reports during the performance period with an average timeliness of 31.75 days.

Measurements

Start Date End Date Total Reports Average Number of Days

April 1, 2014 March 31, 2015 11,850 34.58

April 1, 2015 March 31, 2016 9,975 26.86

April 1, 2016 March 31, 2017 10,371 27.89

April 1, 2017 March 31, 2018 9,901 31.75



5.2 DUI Data Integration

5.2.1 Contact

Mr. Skyler Genest Title: Chief, Vermont Department of Liquor Control Investigator’s Agency: State of Vermont, Vermont Department of Liquor Control Address: 13 Green Mountain Drive City, Zip: Montpelier, VT 05602 Phone: 802-477-2429 Email: [email protected]

5.2.2 Lead Agency

Vermont Department of Liquor Control

5.2.3 Status

New for October 2018

5.2.3 Budget


NHTSA 405c 2019 $17,360.00


Vermont Law Enforcement is collecting Point of Last Drink (POLD) data on a very rudimentary level in the state, however this is done predominately on paper DUI processing forms which certainly doesn’t lend itself to any effective means of analysis.

DLC wishes to have a question added to the DMT Datamaster software by the State Forensic Labratory / Department of Public Safety, asking the arresting officer: “Did your investigation determine that the place of last drink for this arrest was a licensed liquor establishment or permitted event?”. An answer in the affirmative this question would serve as an initiator for DLC Liquor Investigators to begin a separate source investigation.

The outcome of the source Investigations triggered by a yes answer to the DMT Datamaster question would identify specific licensed establishments who served "last drink". This would be warehoused in a DLC database and used to drive education and enforcement actions across the state. This is done by the use of a national database developed by the National Liquor Law Enforcement Association and a Microsoft Power BI application.

Sharing of POLD data could occur via the VJISS portal.

Problem Statement: Licensed drinking establishments have long been recognized as high-risk locations for contributing to impaired driving. Among adults who self-report binge drinking, about 54% of all binge drinking episodes take place at a bar, club, or restaurant, compared to 36% in homes and 10% elsewhere. A recent study identified enforcing over service laws at on-




premise licensed establishments as a key strategy for preventing alcohol-related tragedies. While the Department of Liquor Control (DLC) has historically conducted enforcement activities designed to prevent over service at licensed establishments, these types of operations have been done randomly and without objective data to identify which establishments should receive focused law enforcement resources.

DLC has implemented a data driven approach to resource allocation and wishes to collect arrest level data during DUI processing to better quantify problem licensed establishments in the realm of highway safety.

Countermeasures: Data recommendations indicated in the 2012 TR Assessment.

Strategies: Vermont DLC will integrate the DataMaster information on POLD to be able to produce in-depth analysis of POLD data to be used by local/state law enforcement, local control commissioners, community coalitions, and potentially via the VJISS portal.

Goals: To collect information on what percentage of DUI arrests in the state originate from a licensed liquor establishment, to reduce number of DUI arrest that stem from licensed liquor establishments.

5.2.5 Schedule

October 1, 2018 through September 30, 2019


Report Start

Report End

10-21-17

Provided By

Skyler Genest

Activity Vermont Department of Liquor Control Chief Skyler Genst gave a demonstration of the data collected from the DataMaster’s statewide in reference to Point of Last Drink (POLD) and how this can be used to target locations to focus DUI patrols by LEA statewide.



5.3 SIREN

5.3.1 Contact

Ms. Chelsea Dubie Title: EMS Data Manager Agency: Vermont Department of Health Office: Division of Emergency Preparedness Response, and Injury Prevention Address: 108 Cherry Street City, Zip: Burlington 05401 Phone: 802-951-5824 Email: [email protected]

5.3.2 Lead Agency

Vermont Department of Health Emergency Medical Services

5.3.3 Status

Active


The Vermont Department of Health Emergency Medical Services ongoing completion of the SIREN data system implementation involves the following key components for FFY 2017:

Data Manager: The Vermont Department of Health EMS office requires a data manager to coordinate the collection, analysis, and reporting of EMS incident data and to provide technical assistance and training for SIREN, Vermont’s statewide electronic EMS incident reporting system. The EMS data manager is necessary to maintain functionality of the SIREN program, increase the number of Vermont EMS agencies entering data into SIREN, and to ensure accurate, complete, timely, and uniform EMS incident reports. One of the primary roles for the data manager in FFY 2017 will be to enhance the integration of EMS data with injury and illness surveillance efforts by working to establish linkage between SIREN and hospital electronic medical record databases. This integration of information will allow for a more comprehensive assessment of motor vehicle, bicycle and pedestrian crashes in the State.

Contracted Services: The contract for Field-Bridge, (the laptop-based software for real-time EMS data entry), will be continued. Field-Bridge is essential for ongoing SIREN implementation and enhancements, including the CRASH-SIREN data linkage development. A data linkage host will also be established for an efficient, cost effective approach to the hospital data linkage effort.

Training: System users and administrators will require additional targeted training to implement and fully utilize SIREN. Specific planning and training will also be required with the contractor hired to develop the SIREN- hospital data linkage implementation.

Problem Statement: The run time data system for emergency medical services needs to further transition from its implementation phase to development of interface with both the Crash system and hospital medical records databases.




Countermeasures: Data improvement recommendations indicated in the 2016 TR Assessment.

Strategies: Software development and upgrades; continuous monitoring of EMS data reporting and analysis of data for completeness and accuracy.

Goals: To continue improvement of completeness and timeliness of data submission from EMS agencies and to develop initial testing of Crash and hospital linkages.

The data component description for this project remains the same as in the previous federal fiscal year. Based on NHTSA recommendations as a result of the 2016 Vermont Traffic Records Assessment, this project aims to establish a data linkage between Vermont’s pre-hospital electronic patient care reporting system (SIREN – Statewide Incident Reporting Network) and hospital electronic medical record databases. This integration of information will allow for a more comprehensive assessment of motor vehicle, bicycle and pedestrian crashes in the State.

Providing medical outcomes and other injury related information from the SIREN-hospital data linkage will enable traffic safety partners to more accurately identify the level of crash severity beyond the typical five-point scale utilized on most crash reports. As a result, SIREN-hospital data linkage will have the capacity to inform and lead highway safety programs in order to ultimately reduce deaths, injuries and economic losses resulting from motor vehicle crashes. A contractor will provide the resources necessary to successfully link the two databases, including but not limited to data matching software, database design, and testing/beta sites.

Although SIREN-hospital data linkage is not yet fully implemented in the State, a data sharing agreement between the Vermont Department of Health and the Level 1 Trauma hospital in Vermont demonstrates incremental progress from the previous federal fiscal year. The Health Department will begin receiving hospital spinal injury outcome data for patients who were documented in SIREN with motor vehicle crash related injuries. Having access to these data will provide us with the ability to evaluate the effects of roadway motor vehicle crashes and have the capacity to inform and lead highway safety programs. Evaluating the processes of receiving these hospital data will also help to guide SIREN-Hospital Data Linkage project plans and objectives.

5.3.5 Schedule


5.3.6 Budget


NHTSA 405c 2019 $207,721.00




Report Start

07-01-2011

Report End

09-30-2011

Provided By

Raymond Walker

Activity Approximately 10% of the EMS agencies are reporting electronically. Many of the larger service providers are included in the 10% submission agencies so they are probably capturing 10% to 20% of the runs in the state.

Vermont has mandated all agencies submit EMS data electronically by January 1, 2013.

Plans Continue roll out of the SIREN system statewide.

Comments Vermont EMS has selected Image Trend to be their software vendor.

Report Start

10-01-2011

Report End

12-31-2011

Provided By

Raymond Walker

Activity Added 12 new reporting agencies using statewide Incident Reporting Network (SIREN) system. Currently 34 EMS agencies reporting their PCR data using SIREN.

Plans Have EMS Statewide Incident Reporting Network (SIREN) Data Manager in place by January or early February 2012.

Continue statewide roll out of the SIREN system.

Provide Squad Administrator training to 4 more agencies in February and March 2012.

Report Start

01-01-2012

Report End

03-31-2012

Provided By

Raymond Walker

Activity SIREN EMS Provider Supervisory Training for end-users has been completed.

Increased SIREN usage from 6 to 48 EMS Providers.

Every EMS Provider has been mandated to use SIREN by January 01, 2013.

Plans Have EMS Statewide Incident Reporting Network (SIREN) Data Manager in place by January or early February 2012.

Continue statewide roll out of the SIREN system.

Report Start

04-01-2012

Report End

09-30-2012

Provided By

Jenna Protzko

Activity Jenna Protzko has been hired for the SIREN Data Manager position.

Attended and provided SIREN status at TRCC meetings.

Increased statewide SIREN usage to approximately 65%.

Plans Continue to roll our SIREN to new EMS providers.



Report Start

04-01-2012

Report End

09-30-2012

Provided By

Jenna Protzko

Review and update SIREN Patient Care Run reports (PCR).

Begin planning for Vermont NEMSIS 3 compliance.

Begin work on EMS Data Dictionary.

Report Start

10-01-2012

Report End

12-31-2012

Provided By

Jenna Protzko

Activity Attended and provided SIREN status at TRCC meetings; Increased statewide SIREN usage to approximately 75%; Standardized ePCR on NEMSIS Version 2; Completed work on EMS Data Dictionary, NEMSIS, Version 2; Prepared SIREN training materials; Provided SIREN training to approximately 14 EMS services; Prepared Field Bridge proposal; Reviewed Laptop proposal.

Plans Continue to roll our SIREN to new EMS providers.

Continue providing SIREN training to EMS services.

Procure and distribute laptops to EMS providers.

Procure Field Bridge for EMS providers.

Report Start

01-01-2013

Report End

05-01-2013

Provided By

Jenna Protzko

Activity Attended and provided SIREN status at TRCC meetings.

Increased statewide SIREN usage to approximately 86%.

Provided SIREN training to remaining EMS services.

EMS reallocation of training funds to purchase laptops. $28,000 was originally allocated in current year funding for training. The training needs are met to date, and there is about $18,000 remaining. VDH is requesting $15,000 be reallocated for each of the 90 EMS agencies to get at least one Toughbook. The TRCC approved this reallocation.

Plans Continue to roll our SIREN to remaining EMS services.

Attend and provide SIREN status at TRCC meetings.

Continue to provide SIREN training to EMS services as needed.

Procure and distribute laptops to EMS providers.

Report Start

05-01-2013

Report End

08-01-2013

Provided By

Jenna Protzko

Plans The field bridge contract is awaiting finalization pending the VDH business office review with DII. NEMSIS version 3 will hopefully be ready to go live in fall 2014.



Report Start

08-01-2013

Report End

11-01-2013

Provided By

Jenna Protzko

Plans Continue training of administrators on Field Bridge use and upgrading all the EMS sites. Jenna Protzko and Mary Spicer are continuing to consult about the development of Crash/Siren bridge building.

Report Start

11-01-2013

Report End

02-01-2014

Provided By

Jenna Protzko

Activity 44% users are reporting on Field Bridge.

97% of licensed agencies are reporting into SIREN.

Plans Continue to use a train the trainer model with administrators at the user agencies, and evaluating additional training needs.

Continue discussion with vendor for data-bridging costs for SIREN/Crash.

Report Start

02-01-2014

Report End

06-01-2014

Provided By

Jenna Protzko

Activity 95% of agencies are able to provide data right into SIREN with no need to convert from a difference software.

45 agencies now doing transport run time data (up to 12).

New agreement (pilot) to receive outcome data from FAHC ED for preliminary analysis with SIREN data.

Plans Continuing to use a train the trainer model with administrators at the user agencies, and evaluating additional training needs.

Report Start

06-02-2014

Report End

09-17-2014

Provided By

Jenna Protzko

Activity There are connectivity challenges for users – need to be able to use FieldBridge – users are using a mix of web-based and FieldBridge, some Districts have specific protocols relative to hospital systems. Jenna reviewed an implementation timeline for the updated EMS Data Dictionary being built into the system. She is also currently working on the first data interface project with a hospital data system (FAHC).

Report Start

09-18-2014

Report End

11-12-2014

Provided By

Jenna Protzko

Activity At national association meeting – reviewing NEMSIS updates implementation, and at large annual state conference for EMS, too. Jenna and colleague conducted training for EMS agency administrative users. CRASH –SIREN bridge project proposal is under



Report Start

09-18-2014

Report End

11-12-2014

Provided By

Jenna Protzko

review with DII and partnership pilot with FAHC (UVM Medical Center) for EMR/SIREN data interface is moving slowly forward with basic stakeholder conversations.

Report Start

11-13-2014

Report End

01-21-2015

Provided By

Jenna Protzko

Activity Working with updating NEMSIS current version and experiencing minor delays with vendor, continuing Vermont compliance with codes; other states experiencing similar delays. She is continuing to work, on CRASH/SIREN data bridge, pending completion of DII required paperwork.

Report Start

01-22-2015

Report End

04-22-2015

Provided By

Jenna Protzko

Activity Completing transition to NEMSIS 3 – most current data dictionary for EMS, MMUC incorporated, all in the interest of more detail/precision. Also continuing data sharing pilot with UVM Medical Center ER.

Report Start

04-23-2015

Report End

07-22-2015

Provided By

Jenna Protzko

Activity Jenna Protzko provided a SIREN update with information about NEMSIS compliance and preliminary CRASH-SIREN data linkage planning. In the coming year the upgraded NEMSIS compliant version will go live with training for users and VDH expects to be fully using NEMSIS 3 for all users by March 2016. Questions arose about multiple identifiers for coding in different systems; is there a way to cross –reference, clarify the terminology; the set of terms is definitely health oriented. Drop down lists make for ease of user access to choices as they fill in the info; often initiated at the crash scene and completed after delivery to the hospital. There was a lot of good interest and discussion of the value of CRASH-SIREN linkage, with some concerns about how to make sure that a single, shared record identifier be used across the systems.

Report Start

07-23-2015

Report End

10-21-2015

Provided By

Jenna Protzko

Activity No status.

Report Start

10-22-2015

Report End

01-20-2016

Provided By

Jenna Protzko

Activity SIREN is working to upgrade to the SIREN Elite software. Emma is also working on a data bridge to Web Crash with the VDH IT. SIREN Elite software is NEMSIS 3 compliant.



Report Start

01-21-2016

Report End

04-20-2016

Provided By

Emma Gause

Activity Moving over to the new Siren Elite system this summer, Nemesis data compliance is good, still waiting on some codes from image Trend to finalize this part. Working with a workgroup made up of EMS Field providers to design a new EMS run report format, this will improve data accuracy and ease of use. Liking crash with SIREN, working with Mandy White, slight stall, with elite transitions. Next step to link data under testing - Summer to Fall.

Siren elite will have a portion for hospital access. This will give ER staff real-time access to patient data from the field for treatment. EMS Staff is working on building relations with hospital ED staff for this project. Emma is working with UVM to link stats on Vehicles / Ped crashes. 2015 study.

Report Start

04-21-2016

Report End

07-13-2016

Provided By

Emma Gause

Activity Emma Gause gave a report with her demonstration at the end of the meeting. • March 31 – First Run Form Workgroup Meeting • June 10 – Run Form Completed • July 5 – Validation Rules Completed • July 7 (expected) – Schematrom XML generated

Dedicated all of my time working to implement the new EMS ePCR system (Elite). I formed a workgroup of about 27 individuals from agencies around the state, both volunteer and paid, ambulance and first response, urban and rural, and with varying drive times to the closest hospital.

Report Start

07-14-2016

Report End

10-11-2016

Provided By

Emma Gause

Activity Training DEMO sites now. Hoping to go live in December 2016 with new site.

Report Start

10-11-2016

Report End

01-18-2017

Provided By

Emma Gause

Activity Emma Gause gave the following status: -Making progress with the transition from SIREN to SIREN Elite -Shutting down V2 end of March -Data looks good…a lot of overdose data that is helpful -Emma spent a lot of time on training EMS Agencies either in person or via webinar -No issues with billing or gaps in data -More compatible with Firefox, Chrome, etc. -IE is being phased out but moving to MS Edge



Report Start

01-19-2017

Report End

04-19-2017

Provided By

Emma Gause

Activity March 31, 2017 - 100% moved to Version 3/Elite (Version 2 has been turned off). A lot of education to get them onto the new setup and teach them the new data elements. More specific and tailored to VT. Working with hospitals - create portals. Project to connect SIREN & Crash data - can start testing linking this data.

Report Start

04-19-2017

Report End

07-19-2017

Provided By

James Baraw

Activity No Report, Vermont Department of Health is in the process of Hiring a new SIREN Project Director.

Report Start

07-19-2017

Report End

10-11-2017

Provided By

James Baraw

Activity No Report, Vermont Department of Health is in the process of Hiring a new SIREN Project Director. Interviews are ongoing with hopes of hiring a new PD this month

Report Start

10-11-2017

Report End

01-17-2018

Provided By

James Baraw

Activity Chelsea was hired for the EMS Data Manager position and started in October 2017.

Schedule (please include dates of the start and end of the project and any major milestones):

October 2017 – ImageTrend came to Vermont to provide SIREN trainings to the EMS Office and to EMS providers.

November 2017 – Chelsea went to ImageTrend to receive in-depth training on SIREN.



Report Start

10-11-2017

Report End

01-17-2018

Provided By

James Baraw

November 2017 – December 2017: Created sentinel and syndromic reports for ongoing monitoring and situational awareness.

December 2017 – Ongoing: Partnering with colleagues in infectious disease epidemiology to work on quarterly syndromic surveillance reports using hospital ED data and SIREN EMS data

January 2018 - Finishing electronic 10-93 form. Hope to go live in February.

January 2018 – Ongoing: Working with colleague in the emergency preparedness division to advance the Hospital Hub project.

January 2018 – Ongoing: Lindsey (EMS Training Administrator) and collaborating on documentation trainings for EMS providers (online, in-person, documents, etc.)

Future projects: Onboarding guide for first response agencies wanting to join SIREN, data briefs for website, interactive data dashboard for website, map data using GIS for strategic planning, create shared reports and report writing instructions, research…


See Section 3.1.3 EMS Uniformity for performance measure.

EMS Integration

Label: I-I-1 Status of Improvement: Planned Active Status: Planned Revision Date: 09-APRIL-2015

This performance measure is based on the I-I-1 standard performance measure from NHTSA document “Model Performance Measures for State Traffic Records Systems”.



Vermont will improve the Integration of the EMS system as measured in terms of an increase of:

The percentage of appropriate records in the EMS file that are linked to another system or file. Specifically, the percentage of records linked between Vermont’s pre-hospital electronic patient care reporting system (SIREN – Statewide Incident Reporting Network) and hospital electronic medical record databases with spinal injury outcomes reported.

The state will show continue to measure progress using the following method: The percentage of hospital spinal injury outcome records from the hospital electronic medical record database that were linked with records in SIREN with motor vehicle crash related injuries.

Measurable progress for the previous year was unavailable, due to staffing changes, and a new project director for SIREN. The previous Project Director departed the Vermont Department of Health in April 2017, with the new Project Director coming on board October 2017.



EMS Timeliness

Label: I-T-1 Status of Improvement: Demonstrated Improvement. Status: Active Last Updated: 10-May-2018

Narrative

This performance measure is based on the I-T-1 model.

Vermont will improve the timeliness of the Vermont EMS Statewide Incident Reporting Network (SIREN) as measured in terms of a decrease in the average number of days from the occurrence of an EMS Run to the date the EMS Patient Care Report is entered into the EMS database within a period determined by the State.

The state will show measurable progress using the following method: The average number of days from the occurrence of an EMS Run to the date the EMS Patient Care Report is entered into the EMS database using a baseline period of April 1, 2015 to March 31, 2016 and a current period of April 1, 2016 to March 31, 2017.

There were 80 reporting services during the baseline period with an average timeliness of 6.06 days. There were 109 reporting EMS agencies during the current performance period with an average timeliness of 4.90 days. As detailed in the supporting documentation, there has been an increase in timeliness.

Measurements

Start Date End Date Number of Reporting

Services

Average Number

of Days

April 1, 2013 March 31, 2014 86 14.62

April 1, 2014 March 31, 2015 86 5.23

April 1, 2015 March 31, 2016 80 6.06

April 1, 2016 March 31, 2017 109 4.90

The result is an increase in timeliness of 1.16 days.


Listed below are the report outputs used to obtain the values for this performance measure:



Baseline Period: April 2014 through March 2015

Apr-14 May-14 Jun-14 Jul-14 Aug-14 Sep-14 Oct-14 Nov-14 Dec-14 Jan-15 Feb-15 Mar-15

April 2014 to March

2015

Avg Days To Enter Response













45th Parallel Emergency Medical Services 34.3 3.8 10.4 5.3 4.8 0 4.8 0.8 0.7 2.7 2 4.5 6.18

ALBURGH RESCUE 3.9 5.3 2 1.8 6.8 0.8 0.9 2.2 5.7 11.7 9.3 1.8 4.35

ARLINGTON RESCUE SQUAD, INC. 0.1 0.2 0.3 0 0.1 0.1 0.1 0.1 0.2 0.3 0.1 0.1 0.14

BARRE CITY FIRE AND AMBULANCE No Data 16.5 3.1 3 1.6 1.9 0.9 1.6 1.5 2.3 1.8 1.6 3.25

BARTON AMBULANCE SQUAD, INC. 2.8 1.4 1.1 1.4 4 1.6 1.3 1.3 2 0.8 1 1.8 1.71

BENNINGTON RESCUE SQUAD, INC 0.6 1.1 1.7 4.8 2.4 4.5 2.7 4.8 2.4 30 13.6 3.7 6.03

BRANDON AREA RESCUE SQUAD, INC. 0.4 0 0.8 0.1 0.3 0.3 0.1 0.2 0.1 0 0 0.8 0.26

BRISTOL RESCUE SQUAD, INC. 0 0 0.3 0.2 0 0.1 0.4 0 0 0.1 0 0.4 0.13

BURLINGTON FIRE DEPT. AMBULANCE 0 0.5 0.8 1.1 0.5 0.2 1.1 0.5 0.3 2.6 2.8 0.7 0.93

Cabot Emergency Ambulance Service, Inc. 0.9 1.5 3.5 2.4 1.4 0.3 2.5 0.9 1.7 1.1 0.3 0.4 1.41 CALEDONIA ESSEX AREA AMBULANCE SERVICE, INC. 5.1 1.6 3.8 1.6 1.4 3.1 0.9 1.2 1.4 3.9 1.3 0.7 2.17

CAMBRIDGE RESCUE SQUAD, INC. 2.7 5.9 7.3 2.3 3.1 5.4 7.5 3.2 3.5 2.3 1.8 2.6 3.97

CAREPLUS AMBULANCE SERVICE, INC. 18.6 14.7 41.4 33.6 25 22.5 26.8 24.2 21 24.7 No Data 25.25

CHARLOTTE VOLUNTEER RESCUE SQUAD 0.7 1.4 1.1 0.2 3.8 5.2 3.4 5.1 1.7 2.2 0.3 3.3 2.37

CHESTER AMBULANCE SERVICE 0.8 1 1.6 1 0.2 4 3.4 0.5 1.6 6.3 1.1 1.1 1.88

COLCHESTER RESCUE SQUAD 2.3 1.4 1.4 0.7 0.7 0.6 1.7 1.4 1.1 0.8 2.4 2.2 1.39

DANVILLE RESCUE SQUAD, INC. 1.4 0.7 0.9 0.6 0.3 0.5 0.3 0.3 10.1 2.1 0.4 3.1 1.73

DEERFIELD VALLEY RESCUE, INC. 7.2 10.3 9 5.7 3.2 3.3 1.7 5.9 3.5 2.8 4.3 4.2 5.09

DERBY LINE AMBULANCE INC. 0.7 2.7 2.3 0.5 0.8 18.9 11 13.5 15.6 5.7 0.7 4.7 6.43 EAST MONTPELIER VOLUNTEER FIRE DEPT. INC. No Data 0.2 0.3 2 1.2 2 0.2 1.4 0 0.2 1.7 0.92

ENOSBURGH AMBULANCE SERVICE 0.7 0.2 0.1 0.1 1.2 0 0.1 0.2 0 2.8 3.8 0.5 0.81

ESSEX RESCUE, INC. 1 1.5 0.1 0.7 0.9 2 0.8 0.1 1.1 0.6 1.2 0.7 0.89

FAIR HAVEN RESCUE SQUAD 2.3 0.9 0.5 0.7 0.5 0.8 1.9 1 1 0.8 1 1.1 1.04



FAIRFAX EMS, INC. 0.1 0 0.1 0.3 0 0.3 0.5 0.3 0.1 0.2 0.6 0.5 0.25

FIRST BRANCH AMBULANCE 1.1 9 6.9 1.3 8.2 3.6 0.5 1.9 1 0.3 0.7 0.7 2.93

GLOVER AMBULANCE SQUAD, INC. 0.3 0.3 0.3 1.6 0.6 0.3 0.5 1.5 0.1 0.2 0.3 1.8 0.65

GRAFTON RESCUE No Data 1 2.3 3 1 5.5 0 2.13

GRAND ISLE RESCUE, INC. 5.3 13.3 0.4 10.9 3.3 3.8 19.3 3.3 2.3 3 2 2.2 5.76

GROVETON AMBULANCE SERVICE 60 51 13 5 15.8 22.3 25 8 6.2 29.3 38 24.87 HANOVER FIRE DEPT AMBULANCE SERVICE 72 39.5 12 No Data 41.17 HARDWICK EMERGENCY RESCUE SQUAD, INC. 0.1 0 0 0 0.1 0 0 0 0.2 0 0.2 1.1 0.14

HARTFORD FIRE DEPARTMENT 1.5 1.8 3.6 1.8 2.3 1.2 1.4 3.5 1 2.1 2.6 2.1 2.08

KER AMBULANCE SERVICE 2.3 23 13.2 0.9 2.5 2.7 2 4.3 4.1 5.7 6.1 8.6 6.28

LAMOILLE AMBULANCE SERVICE 0.9 2.3 1.6 2.6 3.8 32.4 2.6 3.8 1.9 4.8 2.4 1.1 5.02

LANCASTER FIRE DEPARTMENT 23.1 20.4 25.6 3.3 18.7 8.6 44.9 38.6 63.6 30.2 17.7 17.6 26.03 LONDONDERRY VOLUNTEER RESCUE SQUAD 2.4 1.1 0.7 0.6 1.2 2.3 0.3 0.4 0.5 0.7 0.8 0.3 0.94

LUDLOW AMBULANCE SERVICE 0.3 0.6 4.5 0.9 1 1.5 1.3 0.7 0.1 1.4 1.5 0.2 1.17

LYNDON RESCUE, INC. 1 3.8 1.2 1.3 1.2 8.7 1.9 1.1 3.2 13.8 16.2 6.8 5.02

MAD RIVER VALLEY AMBULANCE SERVICE 1 1.7 1.2 0.7 4 2.6 1.5 1.9 1.5 0.2 3.3 0.4 1.67

MANCHESTER RESCUE SQUAD, INC. 1.1 1.1 1.1 1.1 1.4 1.3 1.1 1.2 1.8 1.4 1.4 1.1 1.26

Middlebury Regional EMS 1.2 1.3 0.6 0.6 0.7 1 1.9 2.3 1.4 1.8 0.7 0.9 1.20

MILTON RESCUE 1.1 0.1 1.4 1 0.4 0.1 0.5 0.5 0.5 1.4 2.1 0 0.76 MISSISQUOI VALLEY AMBULANCE SERVICE 0.5 0.4 0.3 0.3 0.4 3.2 0.4 0.1 0.1 0.6 0.4 0.8 0.63

MISSISQUOI VALLEY RESCUE, INC. 0.2 0.3 2.6 0.3 0.3 0.2 0.2 1.2 0.5 0.3 0.8 0.3 0.60

MONTGOMERY RESCUE SQUAD 0.2 0 0.2 0 5.5 0 0 6.6 2.2 5.6 0 0 1.69

Montpelier Ambulance Service No Data 0.1 0.1 0.1 0 0 0 0 0.1 0.1 0.1 0.06

MORRISTOWN RESCUE 3.6 1.8 2.8 1.9 2.6 1.1 10.5 6.3 3 1.4 4 3.1 3.51

Mount Holly Volunteer Rescue Squad 115 47.5 33.3 75 15.6 58.6 103 43 13.8 17.7 4.3 31.5 46.53

NEWPORT AMBULANCE SERVICE, INC. 0.2 0.3 1.6 0.4 1.3 1.8 0.3 0.1 0.1 0.1 0.1 0.2 0.54 NEWPORT AMBULANCE SVC. - NORTHERN EMS DIV. 0.8 0.4 0.2 0.3 0.7 0.2 0.2 0.3 0.2 0.2 0.5 0.3 0.36

NORTHFIELD AMBULANCE SERVICE 2.2 2.1 2.8 4 4.6 4.4 3.1 8.3 4 6.4 4.8 6.9 4.47

ORLEANS EMERGENCY UNIT, INC. 1.7 1.7 1.4 0.7 1 3.3 0.5 0.7 0.8 0.9 1 0.9 1.22



POULTNEY RESCUE SQUAD, INC. 0.2 0.8 0.3 0.1 0.2 0.3 0.2 0 0 0.8 0.2 0.1 0.27

POWNAL RESCUE SQUAD, INC. 2.6 7.5 4 1 1.4 0.2 0.7 0.1 0 0.3 0.2 1.1 1.59

RESCUE INC. 0.4 1 1.4 2 0.5 1.3 1.6 1.1 0.3 0.7 4 1.4 1.31

RICHFORD AMBULANCE SERVICE 1 1.8 0.7 0.8 0.8 1 1.1 4.3 1.2 5.1 1.6 4 1.95

RICHMOND RESCUE, INC. 11.8 18.3 28.3 30.2 22.8 15.7 17.1 13.9 17.9 21.4 16.2 9.1 18.56 SAINT MICHAEL'S COLLEGE FIRE & RESCUE, INC. 1.9 1.6 2.4 2.4 2.8 1.7 3.1 2.3 2.2 3.5 2.5 2.1 2.38

SOUTH BURLINGTON FIRE DEPARTMENT 0.1 0.1 0 0 0.1 0 0.1 0.1 0.3 0 0.1 0.1 0.08

SOUTH HERO RESCUE 0.4 2.8 0.7 0.9 0 0.5 0 0.4 0 0.1 0.9 0.4 0.59

SOUTH ROYALTON RESCUE SQUAD 6.4 3.3 15.3 9.5 3.1 9.8 26 11.2 4.1 4.9 3.8 5.2 8.55

SPRINGFIELD FIRE DEPT. AMBULANCE 10.2 5.5 3.6 5.2 4.9 9 4.1 2.3 2.3 2 4.6 1.8 4.63

STRATTON MOUNTAIN RESCUE 0.5 No Data 1 0 1 0.3 0.3 0.1 0.5 0.2 0.3 0.3 0.41

TOWN OF BARRE DEPT. OF EMS 0.6 0.7 0.6 0.6 0.3 0.5 0.4 0.7 0.5 0.5 0.6 0.7 0.56

TOWN OF PUTNEY FIRE DEPARTMENT 7.8 3.3 1.1 1.2 0.7 1.5 No Data 1.5 0.5 0 3.5 3 2.19

Town of Shelburne - Rescue Squad 0.3 0.3 0.8 0.6 1.2 2.3 1.9 0.8 0.9 1.4 1.3 2.5 1.19 TOWN OF STOWE - EMERGENCY MEDICAL SERVICES DEPT. 0.1 0.5 0.4 0.3 0.3 0.5 0.4 0.4 0.2 0.2 0.2 0.3 0.32 UNIVERSITY OF VERMONT RESCUE SQUAD 0.1 0.1 0 0 0.3 1.7 2 1.1 0.9 0.9 0.2 0.1 0.62

UPPER VALLEY AMBULANCE, INC 0.9 1.4 1.8 0.9 1.4 1.1 1.8 1.8 1.1 1.2 1.3 1 1.31

VERGENNES AREA RESCUE SQUAD, INC. 0.9 1.3 0.9 0.9 3.3 0.9 1 1.2 0.6 0.7 1 0.7 1.12

VERNON FIRE DEPARTMENT 84 30 41.4 36.8 35.7 34.8 58.1 23.4 8.8 7.3 3.6 23 32.24

WALLINGFORD RESCUE, INC. 0.3 0 4.2 5.4 1.5 0 0 0.6 0 0 0 0.3 1.03

WATERBURY AMBULANCE SERVICE, INC. 0.6 2.4 0.6 0.6 0.9 0.6 0.9 1.3 0.4 0.7 2 0.8 0.98

WHITE RIVER VALLEY AMBULANCE 1.4 2.1 4.1 2.1 0.8 0.8 1.1 0.6 0.6 1.2 0.9 1.43

WILLIAMSTOWN AMBULANCE 0.9 3.5 0.9 1 0.3 1.6 1.8 1.2 0.3 0.8 0.6 0.5 1.12

WILLISTON FIRE DEPARTMENT 0 0.1 0.3 0.2 0.1 0.1 0.1 0 0 0.1 0.9 0.1 0.17

WINDSOR AMBULANCE SERVICE 0.9 0.8 1.1 1.3 2 0.9 0.7 0.7 0.9 0.9 3.3 1.3 1.23

WOODSTOCK AMBULANCE SERVICE 2 0.6 0.6 3 1.8 0.1 0.2 0.5 1.5 0 1.6 0.2 1.01 WOODSVILLE RESCUE AND AMBULANCE SERVICE 24.8 15.3 9.7 38.9 83.3 61.1 10.1 11.5 11.3 7.4 6.6 5.7 23.81

Overall average days to respond for all services using an ImageTrend ePCR 4.78



Agencies submitting to SIREN from a 3rd party ePCR vendor:

AMCARE AMBULANCE SERVICE 2.7 2.3 2.9 2.2 7.7 2 2.1 2 2.1 2.2 3.5 2.5 2.85

FLETCHER ALLEN COORDINATED TRANSPORT 10.9

No Data 32 11.8 No Data 18.23

GOLDEN CROSS AMBULANCE INC. 18.8 2.3 8.8 3.3 3.3 2.6 3 2.9 10.7 5.5 2.5 2.3 5.50

GOLDEN CROSS AMBULANCE, INC. (WESTMINSTER) 16.8 1.5 12 3.5 2.8 3.2 2.3 1.4 10.2 6.4 1.7 2 5.32

GRANVILLE RESCUE SQUAD 36.3 42.4 17.7 No Data 32.13

REGIONAL AMBULANCE SERVICE 5 1.6 1.6 1.6 1.6 1.5 1.6 1.7 1.7 1.7 1.5 1.4 1.88

VILLAGE AMBULANCE SERVICE, INC. 1 1 1 1 1 1 1 1 1 1 21.2 36.5 5.64

Overall average days to respond for all 3rd party users 10.22

Overall average days to respond for all services: 5.23 days



Current Period: April 2015 through March 2016

Apr-15 May-15 Jun-15 Jul-15 Aug-15 Sep-15 Oct-15 Nov-15 Dec-15 Jan-16 Feb-16 Mar-16

April 2015 to March

2016














45th Parallel Emergency Medical Services 3.7 1.9 9.2 1.4 4.6 4.3 4.3 3.1 8.2 10.8 3.5 No Data 4.5

ALBURGH RESCUE 2.5 4.7 1.6 3.8 1.2 6.5 3 3.8 3.5 1.9 4.9 0.6 3.4

ARLINGTON RESCUE SQUAD, INC. 0.1 0 0.1 3.6 0.1 5.2 0 0 0 0.1 0.1 0 0.8

BARRE CITY FIRE AND AMBULANCE 0.6 0.2 0.4 0.2 0.8 0.2 0.6 0.7 0.7 0.2 0.6 0.2 0.4

BARTON AMBULANCE SQUAD, INC. 1.5 4 1.3 2.4 3.9 9.1 4.9 8.1 11.1 8.2 19 10.3 6.5

BENNINGTON RESCUE SQUAD, INC 1.1 2.8 0.9 1.5 0.6 0.3 0.2 0.3 0.6 0.2 0.5 1.3 0.9

BRANDON AREA RESCUE SQUAD, INC. 5 21.7 13 9.6 3.2 1.2 3.9 0.5 0.7 1.2 0.7 0.3 5.8

BRISTOL RESCUE SQUAD, INC. 0.1 0 0.1 0.1 0.1 0.4 0.5 0.1 0 0.1 0.1 0.2 0.2

BURLINGTON FIRE DEPT. AMBULANCE 0.7 4.5 4.1 3.5 0.6 1.8 1.5 2.8 17.4 9 3.1 3 4.2

Cabot Emergency Ambulance Service, Inc. 3 0.5 1.4 0 2.4 1.2 9.8 12.5 22 3.7 7.9 6.5 6 CALEDONIA ESSEX AREA AMBULANCE SERVICE, INC. 1.1 1.2 2.4 1.1 2.1 3.2 0.8 1.9 0.7 1.4 1.1 1.9 1.6

CAMBRIDGE RESCUE SQUAD, INC. 5.6 2.8 5.2 4.3 5.1 3.9 1.9 4 2.2 2.3 1.7 3.6 3.5

CAREPLUS AMBULANCE SERVICE, INC. 95.8 74 43.1 77.7 64.2 30.7 18 58.3 29.8 12.8 58.9 38.7 53.6

CHARLOTTE VOLUNTEER RESCUE SQUAD 5.1 1.4 4.2 3.6 0 0 0 0.1 0.1 0 0.8 0 1.4

CHESTER AMBULANCE SERVICE 1.1 0.8 1.6 3.1 8 1.1 1.1 3.3 2.4 2 1.6 0.8 2.2

COLCHESTER RESCUE SQUAD 1.7 1.2 1.3 2.9 1.1 2.9 21.1 35.3 33.9 22.4 23.7 14 13.2

DANVILLE RESCUE SQUAD, INC. No longer an Ambulance Agency – Now First Response

DEERFIELD VALLEY RESCUE, INC. 9.5 8.3 3.2 11.9 8.4 6.4 7.1 10 7.7 8.7 4.6 6.9 7.7

DERBY LINE AMBULANCE INC. 6.1 6.7 22.5 13.5 11.1 7.5 5 3.4 3.8 2.5 2.1 2.6 7.1 EAST MONTPELIER VOLUNTEER FIRE DEPT. INC. 1.2 2 0.9 1.2 0.4 1.2 1.6 0.1 0.5 0.3 0.2 0.8 0.9

ENOSBURGH AMBULANCE SERVICE 1.2 4.9 0.4 3.1 0 0.1 0 0 0 0 0.1 0 0.9

ESSEX RESCUE, INC. 2.5 1 2.2 0.5 0.6 0.5 1.4 0.7 1.1 0.4 0.5 0.5 1

FAIR HAVEN RESCUE SQUAD 1.3 1.6 0.8 2.4 2 2 2 1.3 2 1.2 0.9 1.1 1.5



FAIRFAX EMS, INC. 0.6 0.1 0.9 1 0.2 3.4 0.8 0.8 0.2 1 0.3 0.4 0.8

FIRST BRANCH AMBULANCE 17 15.5 2.5 7.3 2 1.8 0.9 2.3 1.2 1.2 4.9 2 4.3

GLOVER AMBULANCE SQUAD, INC. 0.5 2.5 0.6 0.5 1.2 3.9 1.4 0.2 0.2 1.5 1 0.1 1.2

GRAFTON RESCUE First Response Agency

GRAND ISLE RESCUE, INC. 0.8 3.4 0.2 6.5 9.9 1.9 6.3 2.9 2.1 1.7 1.3 0.8 3.9

GROVETON AMBULANCE SERVICE No Data 63.7 34 6 41.7 No Data 69 39.8 No Data 118.3 88 56.3 54 HANOVER FIRE DEPT AMBULANCE SERVICE

No Data

HARDWICK EMERGENCY RESCUE SQUAD, INC. No Data 63.7 34 6 41.7 No Data 69 39.8 No Data 118.3 88 56.3 54

HARTFORD FIRE DEPARTMENT 0.1 0 0 0 0.1 0.3 0.1 0.2 0.3 0.1 0.3 0.6 0.2

KER AMBULANCE SERVICE 1 1 1.9 1.5 2.8 3.3 2.3 1.4 2.6 2.1 1.9 1.4 1.9

LAMOILLE AMBULANCE SERVICE Switched to Third Party Vendor – See Below

LANCASTER FIRE DEPARTMENT 20.7 15.9 15.3 8.4 15.9 15.3 20.6 19.1 19.1 13.9 20.8 No Data 16.3 LONDONDERRY VOLUNTEER RESCUE SQUAD 0.3 1 6.5 0.4 2 0.4 6.8 0.4 1.1 0.8 0.4 0.3 1.4

LUDLOW AMBULANCE SERVICE 4.6 0.1 1.4 2.8 0.6 0.3 0.2 0.4 0.6 2.8 1.4 0.5 1.4

LYNDON RESCUE, INC. 4.7 4.1 6.2 2.5 7.3 2.3 1.9 2 2.1 2.2 2.2 1.9 3.4

MAD RIVER VALLEY AMBULANCE SERVICE 0.7 1.6 0.6 1 1.9 1.1 0.9 3.8 1.2 0.8 1.3 0.2 1.2

MANCHESTER RESCUE SQUAD, INC. 1 1.1 1 1.1 1.2 47.6 1.2 1.1 1.1 1.3 1.1 1.1 6

Middlebury Regional EMS 1.4 1.8 4.8 0.7 0.8 0.8 1 0.8 1.2 1.5 1.5 0.8 1.4

MILTON RESCUE 5.4 3.9 26.8 16 3 2.4 4.4 1.2 0.2 0.5 7.1 9.5 6.4 MISSISQUOI VALLEY AMBULANCE SERVICE 1.5 0.1 0.6 1.4 1.1 0.1 1.4 1.2 3.1 3.6 1.3 1.6 1.7

MISSISQUOI VALLEY RESCUE, INC. 0.7 0.6 0.7 2.8 5.2 0.4 1.7 2.1 0.2 1 4.5 6.4 2.2

MONTGOMERY RESCUE SQUAD 0 0 0 2.5 0 0.9 0 7.5 0.2 0 0 6.5 1.1

Montpelier Ambulance Service 0.1 0.1 0.2 0.1 0.1 0.1 0 0 0.1 0.1 0.1 0.1 0.1

MORRISTOWN RESCUE 0.3 3.1 1 1 1.6 5.8 5.5 3.7 3.9 3.4 7.6 4.9 3.6

Mount Holly Volunteer Rescue Squad 14 10 2.8 73.3 24 0.3 10.5 13.9 16.4 17.3 2.4 1 14.1

NEWPORT AMBULANCE SERVICE, INC. 0.5 0.4 0.2 0.5 0.1 0.2 0.2 0.2 0.1 0.2 0.4 0.8 0.3 NEWPORT AMBULANCE SVC. - NORTHERN EMS DIV. 0.1 0.2 0.3 0.3 0.3 0.7 0.2 0.4 0.5 0.2 0.6 0.8 0.4

NORTHFIELD AMBULANCE SERVICE 7.3 5.6 3.1 7.9 7.4 14.4 41.8 25.5 12.7 6.4 15 2.7 13.1

ORLEANS EMERGENCY UNIT, INC. 0.9 0.9 0.6 0.9 1.4 1.1 1.1 1.7 1.8 2.9 1.3 1.4 1.3



POULTNEY RESCUE SQUAD, INC. 0 0.1 1.1 0.5 0.2 0.2 0.9 0.2 0.3 0.1 0 0.8 0.4

POWNAL RESCUE SQUAD, INC. 0.6 0.5 2.2 0.1 9 6.7 0.5 2.8 2.3 1.1 0.6 0.9 2.1

RESCUE INC. 8.5 3.9 6.2 2.1 0.4 0.8 0.6 0.9 0.7 1.1 1.7 1.4 2.3

RICHFORD AMBULANCE SERVICE 1.8 3 2 4.7 0.7 8.1 8.8 3.7 2.4 4.1 8.6 0.8 4.2

RICHMOND RESCUE, INC. 10.3 19.3 20.1 19.6 20.2 20 26.4 26.5 17.1 21.8 21.4 14.3 20.2 SAINT MICHAEL'S COLLEGE FIRE & RESCUE, INC. 2.1 2.5 2.6 3.4 3.2 4.8 2.4 2.5 2.8 2.6 2.4 2.7 2.8

SOUTH BURLINGTON FIRE DEPARTMENT 0 0 0.1 0 1.3 0 0 0 0.1 0 0.2 0.2 0.2

SOUTH HERO RESCUE 0.5 0.8 0 0 1.8 2 0.1 0 3.5 0.5 13.4 3.8 2.7

SOUTH ROYALTON RESCUE SQUAD 0.9 1 22.3 8.1 12.9 9.6 12.1 14.3 16 3.8 7.5 2.9 9.2

SPRINGFIELD FIRE DEPT. AMBULANCE 2.5 4.4 3.3 2.7 7.3 5.5 3.2 3.1 3 3 2.7 6 3.9

STRATTON MOUNTAIN RESCUE 0.4 28 1.4 1 0.3 0.3 0.5 0 0.4 0.3 0.6 0.9 0.8


TOWN OF PUTNEY FIRE DEPARTMENT First Response Agency

Town of Shelburne - Rescue Squad 1.3 2.6 2.8 5.3 1.1 4.5 2.1 1.2 0.9 1.2 0.4 0.9 2.1 TOWN OF STOWE - EMERGENCY MEDICAL SERVICES DEPT. 0.3 0.1 0.4 0.7 0.6 13.5 0.4 0.3 0.6 0.6 0.5 No Data 1.5 UNIVERSITY OF VERMONT RESCUE SQUAD 0 0 0.1 0 0 1.6 0 0 0 0.1 0 0 0.2

UPPER VALLEY AMBULANCE, INC 0.6 0.7 1.2 0.7 0.6 1.1 0.7 0.5 0.7 0.7 1 1.1 0.8

VERGENNES AREA RESCUE SQUAD, INC. 0.4 1.9 3.2 1.5 1.5 1.5 1.4 1.2 1.8 1.2 0.9 0.9 1.5

VERNON FIRE DEPARTMENT 23.6 14.2 14.5 21.6 9.4 30.1 64.3 71.7 11 22 21.3 8 21.3

WALLINGFORD RESCUE, INC. 0.2 0 0.7 4.6 1.8 0 0.1 0.9 0.1 0.8 0 0 1

WATERBURY AMBULANCE SERVICE, INC. 0.8 0.9 0.9 0.5 0.7 3.6 2.6 0.9 1 0.6 0.6 0.9 1.2

WHITE RIVER VALLEY AMBULANCE 1.3 2.5 2.6 1.4 1.5 0.9 1 0.5 1.2 1.2 0.3 1.1 1.3

WILLIAMSTOWN AMBULANCE 1 1.1 0.6 0.6 0.6 0.5 0.4 0.4 0.4 0.6 0.1 0.5 0.6

WILLISTON FIRE DEPARTMENT 0 0 0 0 0 0.2 0.6 19.2 17.8 22.1 19.3 21.7 8.7

WINDSOR AMBULANCE SERVICE 1.1 1.8 0.9 1.4 1.7 1.7 1.9 3 2.6 1.2 1 1.1 1.6

WOODSTOCK AMBULANCE SERVICE 0.3 0 0 0.6 2.5 0.2 0.3 0.2 1.3 1 0.5 0.8 0.6 WOODSVILLE RESCUE AND AMBULANCE SERVICE 12.3 14.1 21.3 17.9 12.5 7.3 10 7.3 8.2 10.8 14.5 10.2 12

Overall average days to respond for all services using an ImageTrend ePCR 5.2



Agencies submitting to SIREN from a 3rd party ePCR vendor:

AMCARE AMBULANCE SERVICE 2.5 2.7 1.8 1.7 1.7 2 4.5 2.4 4 4 1.9 1.9 2.6

GOLDEN CROSS AMBULANCE INC. 2.2 5.4 4.8 3 2 3.3 5.6 7.7 3.6 8.4 5.2 2.8 4.5

GOLDEN CROSS AMBULANCE, INC. (WESTMINSTER) 1.2 2.6 4.8 1.6 2.7 1.5 3.8 5.5 2.4 3.5 2.5 2.2 2.8

GRANVILLE RESCUE SQUAD No Data – No longer licensed by Vermont

LAMOILLE AMBULANCE SERVICE 2.7 1.5 0.9 0.6 2.4 4 5.1 3.5 6.9 4.7 1.3 3.3 2.9

REGIONAL AMBULANCE SERVICE 1.5 1.4 1.4 1.5 1.5 1.9 1.5 1.7 1.6 1.6 1.5 1.5 1.6

UVM Critical Care Transport No Data – Critical Care Only

VILLAGE AMBULANCE SERVICE, INC. 246.6 213.9 182.8 126.9 76.5 94.3 65.2 38.2 8.6 2.3 1.6 3.9 87.7

Overall average days to respond for all 3rd party users 17




Current Period: April 2016 through March 2017

Apr-16 May-16 Jun-16 Jul-16 Aug-16 Sep-16 Oct-16 Nov-16 Dec-16 Jan-17 Feb-17 Mar-17 Apr 2016 to Mar 2017














45th Parallel Emergency Medical Services 9.8 5.7 No data No data No data No data No data No data No data No data No data No data 7.8

ALBURGH RESCUE 9.3 6.6 2 5 3.3 4.2 19.8 16 8.9 5.7 1.96 0.72 7.0

AMCARE AMBULANCE SERVICE 2.2 2 2 2 2.2 2.7 2.4 2.7 2.5 2.4 2 0.37 2.1

ARLINGTON RESCUE SQUAD, INC. 0.1 0 0 0 0 0 0 0 0.08 0.09 0.09 0.08 0.0

BARRE CITY FIRE AND AMBULANCE 0.6 0.3 0.5 0.5 0.7 0.4 0.4 0.2 0.18 0.08 0.41 0.14 0.4

BARTON AMBULANCE SQUAD, INC. 12.1 11.4 25.9 18.1 56.5 30.2 25.1 14.7 33.1 17.4 13.6 8.3 22.2

BENNINGTON RESCUE SQUAD, INC 1 0.8 0.7 0.3 0.2 0.6 1.5 0 0.12 0.13 0.13 0.14 0.5

BENSON FIRST RESPONSE No data No data No data No data No data No data No data No data No data No data No data 0.05 0.1

BRADFORD FAST SQUAD 0.3 0.5 No data 1 4 3 No data No data No data 19.48 0.36 0.26 3.6

BRANDON AREA RESCUE SQUAD, INC. 5.2 4 8.7 4.8 0 0.1 0.1 4.8 1.5 0.1 0.12 0.1 2.5

BRATTLEBORO FIRE DEPARTMENT 0.3 0.1 0.3 0.6 0.2 1.7 0.2 0.2 0.22 1.37 0.49 0.37 0.5

BRISTOL RESCUE SQUAD, INC. 5.1 0.1 0.6 1.8 0.4 0.4 0.3 0.4 0 0.2 0.1 0.21 0.8

BURLINGTON FIRE DEPT. AMBULANCE 23.2 15.5 27.5 21.6 35.7 18.3 24.6 15.8 4.8 0.51 0.19 0.12 15.7

Cabot Emergency Ambulance Service, Inc. 1.9 5.9 5 7 4.9 1 3.4 3 3.9 0.6 3.79 1.59 3.5 CALEDONIA ESSEX AREA AMBULANCE SERVICE, INC. 10.9 13.3 5.4 5.3 6.1 2 2.8 1.7 1.6 1.3 0.12 0.47 4.2

CAMBRIDGE RESCUE SQUAD, INC. 2.4 1.9 2.8 3.3 4.3 9.1 4.2 3.8 1.6 6.7 No data 1.7 3.8

CAREPLUS AMBULANCE SERVICE, INC. 23.9 29.5 No data No data No data No data No data No data No data No data No data No data 26.7

CHAMPLAIN VALLEY EXPOSITION FIRST RESPONSE 0 No data 0 No data 0.2 1.3 0 No data No data No data No data 0.06 0.3

CHARLOTTE VOLUNTEER RESCUE SQUAD 0.1 9.7 0 0.1 0.2 0.1 0.3 3.7 0.2 0.05 0.93 0.08 1.3

CHESTER AMBULANCE SERVICE 4.4 3.1 1.2 5.3 0.8 2.9 1 0.7 2 0.1 0.8 0.36 1.9

COLCHESTER RESCUE 28.9 29.4 26.8 15.2 8.6 6.3 5.6 7.9 5.2 0.05 0.04 0.05 11.2

DANVILLE RESCUE SQUAD, INC. No data No data No data 1 0 0 No data No data No data No data No data No data 0.3

DEERFIELD VALLEY RESCUE, INC. 48.1 26.9 33.6 31.3 18.2 15.6 18.1 8.4 5.4 1.09 2.11 1.01 17.5

DERBY LINE AMBULANCE INC. 4.2 6.2 5.9 6.7 10 5.5 7 8.2 7.9 6 2.6 3.17 6.1

EAST MONTPELIER VOLUNTEER FIRE DEPT. INC. 1.6 0.2 1.4 0.8 0 6.5 0.4 1.6 1.6 0.14 0.15 1.29 1.3

ENOSBURGH AMBULANCE SERVICE 0 0.1 0.1 0.1 0 0 0.1 0 0.1 0 0 0.67 0.1

ESSEX FIRE DEPARTMENT 0.1 0.5 0 0 0 0 1 0 0 0.5 0.1 0.07 0.2

ESSEX RESCUE, INC. 0.2 0.5 0.7 1.1 1.6 0.7 1.9 0.3 0.1 0.7 0.4 0.57 0.7

FAIR HAVEN RESCUE SQUAD 1.9 0.9 0.5 0.6 1.1 0.8 1.6 1.3 1.8 1.05 2.06 1.49 1.3

FAIRFAX EMS, INC. 0.3 0.9 0.4 0.3 0.4 0.9 2.1 1.1 0.2 0.26 0.13 0.13 0.6

FAIRLEE FAST SQUAD No data No data No data No data No data No data No data No data 0.22 4.8 4.12 No data 3.0

FAST AID SQUAD OF THETFORD No data No data No data No data No data No data No data No data No data 0.51 3.79 4.61 3.0

FIRST BRANCH AMBULANCE 19.5 52.4 24.7 16.5 12.5 15.7 3.5 0.3 0.76 1.57 0.77 1 12.4

GEORGIA FIRST RESPONSE No data No data No data No data No data No data No data No data No data No data 0.09 2.68 1.4



GLOVER AMBULANCE SQUAD, INC. 4.6 0.3 0.9 4.4 0.9 2.9 0.9 2.3 5.7 0.5 0.8 0.1 2.0

GOLDEN CROSS AMBULANCE INC. 4.4 1.4 1.6 2.2 2 1.9 2.1 1.5 1.9 1.5 1.7 2 2.0 GOLDEN CROSS AMBULANCE, INC. (WESTMINSTER) 2.1 1.3 1.4 1.3 1.3 1.2 1.2 1.4 1.3 1.1 1.5 1.5 1.4

GRAFTON RESCUE 15 43.3 6 2.5 2.6 13.1 11.2 12.5 2.49 7.4 16.92 0.77 11.1

GRAND ISLE RESCUE, INC. 2.2 2.8 0.1 17.5 5.5 2.4 11.1 19.4 7.2 2.3 0.28 0.17 5.9

GRANVILLE VOLUNTEER FIRE DEPARTMENT, INC No data No data No data No data No data No data No data No data No data 4.24 No data No data 4.2

GROTON-RYEGATE EMS No data No data No data No data No data No data No data No data No data 1.25 0.59 4.72 2.2

GROVETON AMBULANCE SERVICE 15.5 5 No data No data No data No data No data No data No data No data No data No data 10.3

GUILFORD VOLUNTEER FIRE DEPARTMENT 1 1 1.3 No data 0.8 4 3.28 No data 0.06 4.46 19.73 0.78 3.6

HARDWICK EMERGENCY RESCUE SQUAD, INC. 2.1 0 0.1 1.8 0.3 3.5 0.7 0.2 0.2 0.1 0.3 0.34 0.8

HARTFORD FIRE DEPARTMENT 3.2 1.9 1.8 1.4 2.3 1.5 1 0 0.11 0.22 0.17 0.11 1.1

HINESBURG FIRE DEPARTMENT No data No data No data No data No data No data No data No data No data No data No data 0.3 0.3

JAMAICA VOLUNTEER FIRE RESCUE 6.5 11.3 1 10 No data 0 No data No data No data 5.78 2.02 4.19 5.1

KER AMBULANCE SERVICE 12.3 16.2 13.8 18 21 24 33.8 21.7 14 15.82 15.69 8.1 17.9

LAMOILLE AMBULANCE SERVICE 0.3 7.6 0 1.5 8 3.1 0 0.5 0 0.56 0.48 0.46 1.9

LANCASTER FIRE DEPARTMENT 16.9 17.4 No data No data No data No data No data No data No data No data No data No data 17.2

LONDONDERRY VOLUNTEER RESCUE SQUAD 0.6 1.2 0.4 1.4 0.3 2.7 2.9 0.4 0.2 1.83 0.59 1.1 1.1

LRI-North No data No data No data No data No data No data No data No data 1 1 1 0 0.8

LUDLOW AMBULANCE SERVICE 0.8 0.3 0.2 0.5 0.8 1.4 130.3 0.9 1.8 0.52 0.74 0.33 11.5

LYNDON RESCUE, INC. 0 0 0 0 0 0 0 0 0 0 0 0 0.0

MAD RIVER VALLEY AMBULANCE SERVICE 1 0.5 5.8 0.2 1.1 0 0.4 1.4 1.4 0.2 4.6 0.13 1.4

MANCHESTER RESCUE SQUAD, INC. 1 0.5 1 0.9 0.7 0.8 1 193 365 No data No data No data 62.7

MARLBORO VOLUNTEER FIRE COMPANY, INC. 0 0 0 0.5 0.3 0 No data 0 0 0.3 No data No data 0.1

Middlebury Regional EMS 1.1 1.2 1.1 1.3 1.4 2 1.4 1.2 1.7 1.85 1.57 1.7 1.5

MILTON RESCUE 12.8 19 20.5 5.6 0.2 1.8 0.6 3.5 0.3 0.26 0.5 0.29 5.4

MISSISQUOI VALLEY AMBULANCE SERVICE 1.7 0.6 1.5 2.8 3.3 5 5.1 0.8 0.9 0.86 0.53 0.5 2.0

MISSISQUOI VALLEY RESCUE, INC. 2.9 1 1 1 1 0.9 2.8 1.1 1.5 0.8 0.2 0.18 1.2

MONTGOMERY RESCUE SQUAD No data 0.5 0 1 0.4 0 0 0.5 0 0.3 0.09 0.16 0.3

Montpelier Ambulance Service 0 0.1 0.1 0.1 0.1 0.1 0.1 0 0.1 0.5 0.12 0.1 0.1

MORRISTOWN EMS 8 4.7 8.1 4.6 3.7 3.6 3.2 4.3 6.4 0.16 1.59 1.6 4.2

Mount Holly Volunteer Rescue Squad 2.7 3.7 8.8 4.3 7 5 4.4 5 5.4 5.1 2.2 0 4.5

NEWBROOK FIRE DEPT 1ST RESPONSE No data 3 No data No data No data No data No data No data No data 0.34 No data No data 1.7

NEWPORT AMBULANCE SERVICE, INC. 0.2 0.2 0.2 0.7 0.2 0.6 0.3 0.3 0.1 0.29 0.41 0.69 0.3 NEWPORT AMBULANCE SVC. - NORTHERN EMS DIV. 0.6 0 0.2 0.4 1.4 0.2 0.2 0.2 0.1 0.39 0.15 0.24 0.3

NORTHFIELD AMBULANCE SERVICE 8.3 7.7 8.6 6.7 6.4 8.3 3.4 1.72 2.19 0.31 0.14 0.11 4.5

ORLEANS EMERGENCY UNIT, INC. 1.8 0.8 1.2 1.5 1.9 1.7 2.3 1.9 2 3.1 1.67 1.28 1.8

PEACHAM VOLUNTEER FIRE DEPARTMENT No data No data No data No data No data No data No data No data No data 25.01 41.3 No data 33.2

PITTSFORD FIRST RESPONSE SQUAD No data No data No data No data No data No data No data No data No data No data 0.04 0.01 0.0

PLYMOUTH FIRST RESPONSE TEAM No data No data No data No data No data No data No data No data No data No data 0.08 No data 0.1

POULTNEY RESCUE SQUAD, INC. 0.4 1.9 2.3 0.7 0.8 0.8 0.9 1.2 1.3 0.43 0.27 0.29 0.9

POWNAL RESCUE SQUAD, INC. 2 2 7.6 5.1 4 3 4.3 6.9 5.5 3.5 1.65 1.09 3.9



READING RESCUE SQUAD No data No data No data No data No data No data 0.5 0 0 No data No data No data 0.2

REGIONAL AMBULANCE SERVICE 1.5 1.5 1.5 1.6 1.4 1.6 1.4 5.1 11.3 0.07 0.08 0.07 2.3

RESCUE INC. 6.7 4 3 7.9 4.4 4.8 21.97 1 0.89 2.39 2.71 1.84 5.1

RICHFORD AMBULANCE SERVICE 5.3 3.3 3.8 4.9 8 11.9 28.1 7.7 3.2 2.1 0 No data 7.1

RICHMOND RESCUE, INC. 20.4 24.8 18.1 33.6 29.7 11.4 0 1.32 0 0 5.07 1.61 12.2

SAINT MICHAEL'S COLLEGE FIRE & RESCUE, INC. 2 1.6 2.3 2.7 2.9 2.4 2.3 2.6 0.17 0.19 0.09 0.11 1.6

SAXTONS RIVER FIRST RESPONSE No data No data No data No data No data No data No data No data No data No data No data 0.58 0.6

SOUTH BURLINGTON FIRE DEPARTMENT 0 0 0 0.1 0 0.2 0.8 0.3 0 0.06 0.06 0.06 0.1

SOUTH HERO RESCUE 0.9 0.1 38.8 0.2 0.3 0.2 0.1 0.7 1.1 49.4 1.11 5.11 8.2 SOUTH HERO VOLUNTEER FIRE DEPARTMENT FIRST RESPONSE No data No data No data No data No data No data No data No data No data No data No data 0.04 0.0

SOUTH ROYALTON RESCUE SQUAD 2.9 9.5 32.9 6.8 1.9 3.6 8.6 3.3 2 3.9 0.3 0.25 6.3

SPRINGFIELD FIRE DEPT. AMBULANCE 9 6.7 4.8 2.4 1.8 1.4 1.6 2.4 2.1 0.9 2.45 2.73 3.2

STRAFFORD FIRST AID SQUAD No data No data No data No data No data No data No data No data No data No data 9.1 0.2 4.7

STRATTON MOUNTAIN RESCUE 0.4 0 0.1 0.4 10.7 0 2.3 0.2 0.2 0.1 0.3 0 1.2

TOWN LINE FIRST RESPONSE No data No data No data No data No data No data No data No data 0 No data 0.09 0.09 0.1


TOWN OF PUTNEY FIRE DEPARTMENT 3 No data 0.8 14.7 No data No data No data 3 No data No data 5 No data 5.3

Town of Shelburne - Rescue Squad 0.4 0.4 7.7 6.4 1.3 2.1 1.5 1.4 1 0.11 0.12 0.53 1.9 TOWN OF STOWE - EMERGENCY MEDICAL SERVICES DEPT No data No data No data No data No data No data No data No data No data No data No data 16.37 16.4

UNIVERSITY OF VERMONT RESCUE SQUAD 0 0 0 0.1 0.1 0 2.1 0 0.1 0.05 0.14 0.07 0.2

UPPER VALLEY AMBULANCE, INC 1 1.6 1.5 1 1.2 4 3.2 0.5 0.19 0.32 0.18 0.16 1.2

VERGENNES AREA RESCUE SQUAD, INC. 2.4 0.9 0.5 1 2 1.7 1.1 0.9 0.3 1 0.9 0.87 1.1

VERNON FIRE DEPARTMENT 6 16.7 57.5 4 26.8 69 26 12.8 14.4 3 5.3 6 20.6

VILLAGE AMBULANCE SERVICE, INC. 2.2 3.3 1.1 6.6 1.9 4.8 7.1 4.8 4 4.5 1.9 2.7 3.7

VT AIR NAT'L GUARD FIRE DEPT 0 0 0.1 0 0 0.1 0.3 0.7 1.5 0.48 0.14 0.3 0.3

WALLINGFORD RESCUE, INC. 0 0 0 0.4 0 0.2 0 0 0 1.11 20.03 0.08 1.8

WATERBURY AMBULANCE SERVICE, INC. 3.5 0.6 1.3 0.8 1.7 1 0.7 0.4 0.7 0.15 0.33 0.14 0.9

WEST FAIRLEE VOLUNTEER FIRE DEPARTMENT 0 No data No data No data No data No data No data 0 No data 1 No data No data 0.3

WHITE RIVER VALLEY AMBULANCE 1.5 8.4 5.7 2.2 1.3 3.6 2.5 6.3 7.6 9.7 0.75 0.15 4.1

WHITINGHAM FIRST RESPONSE No data No data No data No data No data No data No data No data No data 5.78 6.45 7.11 6.4

WILLIAMSTOWN AMBULANCE 0.5 0.5 0.8 0.9 0.4 0.4 0.4 0.7 0.7 0.69 0.53 0.23 0.6

WILLISTON FIRE DEPARTMENT 20 23.9 18.8 30.4 18 19.2 23.6 9.1 0.8 0.08 0.06 0.06 13.7

WINDSOR AMBULANCE SERVICE 1.9 1.4 6.2 1.7 1.7 0.7 0.9 0.8 0.6 1.5 0.59 0.52 1.5

WOODSTOCK AMBULANCE SERVICE 0 0.9 0.7 0.1 1 2 0.1 0.3 1.7 1.18 0.29 0.38 0.7

WOODSVILLE RESCUE AND AMBULANCE SERVICE 9.1 10.8 No data No data No data No data No data No data No data No data No data No data 10.0




5.4 Web Crash Auto Populate

5.4.1 Contact

Ms. Mary Spicer Title: AOT Manager I Agency: Vermont Agency of Transportation Office: PPAID Policy, Planning, and Intermodal Development Address: 1 National Life Building, Drawer 33 City, Zip: Montpelier 05633 Phone: 802-828-2681 Email: [email protected]

5.4.2 Lead Agency


5.4.3 Status

Complete


Law Enforcement (LE) continues to communicate their desire for as many auto population features as possible when filling out a crash report in Web Crash.

Any time we can offer LE a way to speed up the data entry process, the better. Filling out the form is already not a #1 priority for LE nor is this task their favorite activity. It is in our best interest to accommodate LE as much as possible in order to maintain the progress we have made with timely, accurate, and complete crash reporting. The demand continues for more timely and accurate information.

Possible Auto Population services (but not limited to): – SIREN data (EMS run number, EMS Agency, Destination Hospital) – Weather services information. – DMV Person “Restrictions” data (i.e., corrective lenses, mechanical device, hand operations,

etc.) – Provide a GPS coordinate auto-load from Streets/Trips or other application or web service. – Date (used if in the field filling out form at the scene). – DMV Person license and address information. – Pictures from VTrans videolog/VisiWeb and/or Google street type online tools. – Vehicle information. – Other?

5.4.5 Schedule

Complete




Report Start

10-01-2012

Report End

12-31-2012

Provided By

Mary Spicer

Activity Identified the application tool (Messenger) needed to work with DPS message switch to allow access to DMV data for LE to fill in related Crash fields.

Obtained ORI from DPS for VTrans Crash access to switch.

Plans Continue working with DPS IT on virtual server to implement Messenger tool.

Report Start

01-01-2013

Report End

05-31-2013

Provided By

Mary Spicer

Activity We were unable to use the DPS contract “piggyback” and had to go Sole Source. The request has made it through the paperwork process and I am only awaiting the Secretary’s signature. Once I get this (expected this week) I can get PPAID Business Office to request the PO.

Plans Implement Messenger tool.

Virtual server.

Report Start

06-01-2013

Report End

11-01-2013

Provided By

Mary Spicer

Activity Contract is fully executed.

Held kickoff meeting held October 24, 2013.

FS has DPPA approval.

Web Crash read only user accounts provided.

Plans Implement Messenger tool: install, test, and put into production.

Mary working to identify public Joint Application Development (JAD) team.

Report Start

11-01-2013

Report End

02-01-2014

Provided By

Mary Spicer

Activity CPI provided scripts and service work from Deep River.

Plans CPI reviewing material provided by Deep River.

Implement Messenger tool: install, test, and put into production.



Report Start

02-01-2014

Report End

06-01-2014

Provided By

Mary Spicer

Activity CPI provided VT data sample to Crash vendor (Appriss aka Deep River).

Plans Appriss staff working on data sample.

Bob Thigpen working to get contact at DPS to provided Appriss access to message switch.

Report Start

06-02-2014

Report End

07-20-2014

Provided By

Mary Spicer

Activity Progress is being made – web interface being resolved with DMV.

Report Start

07-21-2014

Report End

09-17-2014

Provided By

Mary Spicer

Activity The message switch component is in good shape and being tested; brief demo of the message switch will be scheduled at the next TRCC meeting.

Report Start

09-18-2014

Report End

01-21-2015

Provided By

Mary Spicer

Activity The Auto Population work is done and in a warranty period.


Crash Integration

Label: C-T-1 Status of Improvement: No Improvement Status: Active Last Updated: 3-May-2018

Narrative

This performance measure is based on the C-I-1 model.

Vermont will improve the integration of the AOT Crash Data Reporting System as measured in terms of the percentage of reports in the crash database that are linked to driver/owner and vehicle information from NLETS and DMV data via the message switch for auto-population.

The state will show measurable progress using the following method: The percentage of crash reports linked to person and vehicle data using a baseline period of April 1, 2016 to March 31, 2017 and a current period of April 1, 2017 to March 31, 2018.



Measurements

Start Date End Date Number of Auto-populate Queries

Number of Crash Reports

Percentage Linked

April 1, 2013 March 31, 2014 0 11,515 0%

April 1, 2014 March 31, 2015 737 11,070 6.66%

April 1, 2015 March 31, 2016 19,669 10,537 186.66%

April 1, 2016 March 31, 2017 27,823 10,371 268.28%

April 1, 2017 March 31, 2018 26,613 11,717 227.13%

The result is a decrease in integration of 41.15%. (Since crash reports can contain multiple vehicles and persons, the percentage linked can be greater than 100 percent).


Listed below are the report outputs used to obtain the values for this performance measure:

Message Switch Queries

2014

select COUNT(*)

From MessageSwitch

where messagecalldate between '04/01/2013' and '03/31/2014'

2015

select COUNT(*)

From MessageSwitch


2016

select COUNT(*)



From MessageSwitch


2017

select COUNT(*)

From MessageSwitch


2018

select COUNT(*)

From MessageSwitch




5.5 Local Road LRS

5.5.1 Contact

Mr. Johnathon Croft Title: Mapping Engineer Agency: Vermont Agency of Transportation Office: Technical Services Division Address: National Life Building City, Zip: Montpelier 05633 Phone: 802-828-2600 Email: [email protected]

5.5.2 Lead Agency


5.5.3 Status

Complete


The goal of Geo-spatial Network All Public Roads is to create a linear reference system (LRS) that will contain all the highways included in the Certified Public Highway Mileage (includes the Federal Aid Highway System and local roads). This project will create the ability to run algorithms on the full highway network using the linear reference system, such as high crash locations, and provide a common architecture for the collection of linear referenced inventory data. This project assists the State in laying the foundation for complying with 23 U.S.C. 148, which requires States to advance their capabilities for traffic records data collection, analysis and integration with other sources of safety data, such as road inventories. The development of the Geo-spatial Network for All Public Roads, which includes the LRS for the local roads, will meet the requirements set forth for the Highway Performance Monitoring System (HPMS) and provide geometry for the “Transportation for the Nation” (TFTN) highway network.

5.5.5 Schedule

Complete


Report Start

08-01-2013

Report End

11-01-2013

Provided By

Sarah Kepchar

Activity The project is progressing, challenged in part by the start-up work that involves required input by non-project funded staff.

Plans Continue working to get input by non-project funded staff.



Report Start

11-01-2013

Report End

02-01-2014

Provided By

Sarah Kepchar

Activity Sarah reported that staff have built a draft model and are troubleshooting rules/process/structure. At the moment, they don’t anticipate any problems.

Plans Continue troubleshooting rules/process/structure on draft model.

Report Start

02-01-2014

Report End

06-01-2014

Provided By

Sarah Kepchar

Activity Should have mid-summer meeting demo of the initial version that will be submitted to feds.


Report Start

02-01-2014

Report End

06-01-2014

Provided By

Sarah Kepchar


Report Start

06-02-2014

Report End

07-20-2014

Provided By

Sarah Kepchar

Activity Successful submission of data product to FHWA, may need to request carry forward in September for some additional work. This is a relatively small project with huge overall federal implications for the data involved.

Report Start

07-21-2014

Report End

09-17-2014

Provided By

Sarah Kepchar

Activity Sarah will be attending a national local roads conference to learn national/other states’ progress on the nationwide rollout.

Report Start

09-18-2014

Report End

01-21-2015

Provided By

Sarah Kepchar

Activity Currently on hiatus due to loss of state temp employee who had been doing the work.

Report Start

01-22-2015

Report End

07-22-2015

Provided By

Sarah Kepchar

Activity Currently on hiatus due to loss of state temp employee who had been doing the work.



Report Start

07-23-2015

Report End

10-21-2015

Provided By

Jonathan Croft

Activity Johnathan Croft gave an update on the Local Road LRS project. He’s been working on the project for over the last two years. It’s on the local road linear reference system. This is part of the geographic information system where they pulled together the road centerline data for all public highways that receive state and federal aid, essentially class 3 town highways that are not on our federal aid highway system. For the federal highway system, we have a linear reference system where we have a route that’s defined and we know the beginning mile post and ending mile post and have a series of calibration points along the middle. We can define a route by its route and mile posts -- like what you see on the interstate. We don’t have anything like that on the local road linear reference system or local road system on town highways. Through this process, we built a process to pull the existing road center line data. We run it through a series of scripts (there are 25 individual steps) that take the data and applies a unique linear reference code statewide; looks at the official mileage for the section; runs calibrations; and creates that route system for the local roads. We have refined the process to make the data better and more calibrated. We do have an existing linear referencing system right now for all the local roads. We need to take that and infuse it with the federal aid system and then apply all the attributes that we have on our regular road centerline data so we have very discrete, unique attributes of linear reference code for both the federal aid and the local road and then all the attributes we have on our road centerline data.

Second part of the project is pulling the e-911 data. The data that VTrans has on each of those arcs looks at the classification of the road, a road name (which may or may not be correct), the surface type, the federal aid codes whether it’s a functional class of local road or one of the other functional classes. We have a bunch of metrics that we keep on each of the arcs internally, but e-911 also has a road centerline data set. They have all the official addressing, road names, one way speed limits, and other pieces of information that applies to that data set that we don’t have in our data set. We have been working to conflate those two data sets into one. Our geometry has been refined over the course of years for public highways, and we feel that is quite good. Some of the e-911 geometry for the private roads are excellent, but the public roads are not as good. There are trying to fuse their attributes into are data. Through this project, we set a metric of having 37,000, of nearly 75,000 arcs to conflate over and those are metrics. That is our performance measure. We missed that and hit 46%, 34,000 were able to be conflated over the last year. We worked hard to make sure our schema and their schema the same between the two road centerline data sets. E-911 is going through a whole upgrade with Fairpoint and will be revising their data set, and we will be revising our data set to match. At this moment, they are the same and the underlining attributes are the same. All of our attributes use the same domains and the same scheme which is major step. We nearly have 50% of the arcs conflated so our attributes match their attributes. You can click on one of our arcs and see all the e-911 attributes for address range, their names, and all the rich content that VTrans has. At this point, the local road linear referencing system has been built and moving forward.



Report Start

10-22-2015

Report End

01-20-2016

Provided By

Jonathan Croft

Activity Johnathan Croft gave a presentation showing the group how the new LRS will allow for better location of crash data and other data elements.



5.6 TRCC Consultant

5.6.1 Contact

Mr. James H. Baraw, MPA Title: Highway Safety Program Coordinator Agency: Vermont Agency of Transportation Office: Office of Highway Safety, Governor’s Highway Safety Program Address: One National Life Drive, 5th Floor City, Zip: Montpelier 05633 Phone: 802-760-9222 Email: [email protected]

5.6.2 Lead Agency


5.6.3 Status

Active


LexisNexis Coplogic Solutions Inc. served as the TRCC Consultant for Vermont up to October 30th 2017. Vermont sent out an RFP for a TRCC Consultant. No bid was accepted, and the RFP was sent out a second time with updated specifications, no bids were received as of April, 2018.

The preparation of the meeting agendas in consultation with the co-chairs, monitoring statewide data program compliance, coordinating sharing data between agencies, all record-keeping to assist in developing Vermont’s annual 405c application and general TRRC technical assistance is being done in house at this time by the States TRCC Coordinator.

Problem Statement: The scope of facilitating the work of the TRCC, tracking the NHTSA application/project reporting and regular strategic planning of traffic records projects requires expertise and dedicated time beyond the staffing at the GHSP.

Countermeasures: Data improvement recommendations indicated in the 2016 TR Assessment.

Strategies: Facilitation of TRCC meetings, monitoring progress reports and preparing and filing the IPR/annual TR application materials.

Goals: To maintain regular and accurate compliance with TRCC and TR project reporting requirements.

5.6.5 Schedule




5.6.6 Budget


NHTSA 405c 2019 $65,000.00


Report Start

05-01-2011

Report End

09-30-2011

Provided By

Dave Sistare

Activity Prepared 2011 Vermont Section 408 Grant Application.

Implemented 2011 Vermont Section 408 Grant Application into NHTSA TRIPRS.

Provided expert assistance prioritizing Vermont Traffic Records programs.

Coordinated bi-monthly TRCC meetings.

Provided TRCC meeting agenda, PowerPoint presentation and minutes.

Plans Continue to provide expert assistance to all Vermont Traffic Records programs.

Continue to assist monitoring approved data improvement programs.

Provide support for Quarterly Report submissions.

Manage all Vermont 408 information using NHTSA approved TRIPRS.

Coordinate TRCC meeting. Prepare meeting Agenda, PowerPoint presentation and minutes.

Report Start

10-01-2011

Report End

12-31-2011

Provided By

Dave Sistare

Activity Prepared 2011 Vermont Section 408 Grant Application.

Implemented 2011 Vermont Section 408 Grant Application into NHTSA TRIPRS.

Provided expert assistance prioritizing Vermont Traffic Records programs.

Coordinated bi-monthly TRCC meetings.

Provided TRCC meeting agenda and minutes.





Coordinate TRCC meeting. Prepare meeting agenda and minutes.



Report Start

01-01-2012

Report End

03-31-2012

Provided By

Dave Sistare

Activity Prepared and submitted Vermont Interim Progress Report.

Prepared Traffic Records Assessment Questionnaires.

Identified team to represent Vermont at Traffic Records Assessment.

Coordinated monthly TRCC meetings.

Provided meeting agenda and minutes for TRCC meetings.





Coordinate TRCC meeting. Prepare meeting agenda and minutes.

Report Start

04-01-2012

Report End

06-30-2012

Provided By

Dave Sistare

Activity Coordinated monthly TRCC meetings.


Completed coordination of NHTSA Assessment in Burlington, Vermont.





Coordinate TRCC meeting. Prepare meeting agenda and provide meeting minutes.

Update Vermont Strategic Highway Safety Plan.

Report Start

07-01-2012

Report End

09-30-2012

Provided By

Dave Sistare

Activity Coordinated TRCC meetings.








Report Start

07-01-2012

Report End

09-30-2012

Provided By

Dave Sistare

Coordinate TRCC meeting. Prepare meeting agenda and provide meeting minutes.

Continue work to update Vermont Strategic Highway Safety Plan.

Report Start

10-01-2012

Report End

12-31-2012

Provided By

Dave Sistare


Provided meeting agenda for TRCC meetings.




Manage all Vermont 405c information using NHTSA approved TRIPRS.

Coordinate TRCC meeting. Prepare meeting agenda.

Continue work to update Vermont Strategic Highway Safety Plan.

Report Start

01-01-2013

Report End

05-31-2013

Provided By

Dave Sistare



Prepared and submitted NHTSA 405c Application.






Prepare and submit NHTSA 405c Application.

Report Start

06-01-2013

Report End

08-01-2013

Provided By

Dave Sistare



Submitted NHTSA 405c Application.



Report Start

06-01-2013

Report End

08-01-2013

Provided By

Dave Sistare






Report Start

08-01-2013

Report End

11-01-2013

Provided By

Dave Sistare








Report Start

02-01-2014

Report End

06-01-2014

Provided By

Dave Sistare








Report Start

06-02-2014

Report End

07-20-2014

Provided By

Dave Sistare

Activity Assisted with completion of HSP FY15 TRCC application through TRIPRS. Note that the GHSP posted the RFP for the TRCC consultant and will shortly be reviewing proposals received with a decision well before October 1.




Report Start

06-02-2014

Report End

07-20-2014

Provided By

Dave Sistare





Report Start

07-21-2014

Report End

04-22-2015

Provided By

Dave Sistare

Activity The new contract from GHSP has been offered, signature pending.






Report Start

04-23-2014

Report End

06/16/2015

Provided By

Patricia Topalis

Activity Preparing the HSP FY16 TRCC application.






Report Start

06-17-2015

Report End

06-22-2016

Provided By

Patricia Topalis





Manage all Vermont 405c information to be included in the Strategic Plan.

Coordinate TRCC meetings. Prepare meeting agenda.



Report Start

06-23-2016

Report End

06/15/2017

Provided By

Patricia Topalis


Traffic Records Assessment Support:

The vendor worked with Vermont to facilitate the Traffic Records Assessment. Vendor worked with the data system owners and stakeholders to develop responses that demonstrate the progress that Vermont has made in developing the State’s traffic records data systems. Vendor used prior assessment experiences and lessons learned to facilitate full and completed answers to assessment questions.

Responsibilities included:

• Attended 1-month call prior to Assessment kick-off meeting.

• Identified respondents for each data system: o TRCC Management & Strategic Planning o Crash o Roadway o Vehicle o Driver o Citation/Adjudication o Injury Surveillance o Data Use and Integration

• Entered all respondent contact info into online assessment system (STRAP).

• Assigned all 391 questions to respondents in the STRAP system.

• Attended Assessment Kick-off Meeting.

• Worked with the State Assessment Coordinator and NHTSA Assessment Facilitator.

• Collected and organized supporting documentation from all respondents and upload into the STRAP system.

• Provided respondents with the workshop results prior to Round 1 of the Assessment.

• Provided assessment support to respondents in using the STRAP system, answering questions, coordinating responses, and troubleshooting problems.

• Monitored Assessment for all three rounds of data collection.

• Downloaded all answers and Assessor’s findings after each round.

• Reviewed assessors’ findings after each round of data analysis. Assisted respondents in disputing findings where necessary.

• Attended Final Assessment Meeting (NHTSA report-out).




Report Start

06-23-2016

Report End

06/15/2017

Provided By

Patricia Topalis



Manage all Vermont 405c information to be included in the Strategic Plan.

Coordinate TRCC meetings. Prepare meeting agenda.

Report Start

04-19-2017

Report End

07-19-2017

Provided By

Patricia Topalis







Report Start

07-19-2017

Report End

10-11-2017

Provided By

James Baraw

Activity Continue to provide support assistance to all Vermont Traffic Records programs.





Report Start

10-11-2017

Report End

01-17-2018

Provided By

James Baraw

Activity Continue to provide support assistance to all Vermont Traffic Records programs.






Report Start

01-17-2018

Report End

04-19-2017

Provided By

James Baraw

Activity Preparing the 405c FY19 TRCC application.

Plans Continue to provide support assistance to all Vermont Traffic Records programs.






5.7 End User Crash Data Query Tool

5.7.1 Contact

Ms. Mary Spicer Title: AOT Manager I Agency: Vermont Agency of Transportation Office: PPAID Policy, Planning, and Intermodal Development Address: 1 National Life Building, Drawer 33 City, Zip: Montpelier 05633 Phone: 802-828-2681 Email: [email protected]

5.7.2 Lead Agency


5.7.3 Status

Complete


The goal of this project is to build a user friendly, interactive, online data query tool that can be used by the general public to access the non-personal motor vehicle crash data house at the Vermont Agency of Transportation (VTrans). The tool will provide for simple filtering, sorting, and grouping on standard reports as well as an option for ad-hoc report creation using a fixed set of parameters.

Reports will be available via listings, tables, charts, and maps.

5.7.5 Schedule

Completed September 2015.


Report Start

07-01-2011

Report End

09-30-2011

Provided By

Mary Spicer

Activity Created an OLAP data processing engine to analyze all crashes in VCSG.

Created sample web reports based upon the GHSP reports.

Created Excel 2010 spreadsheets so that power users may be trained on and provided with the query and charting tools for the processing engine.

Created a data dictionary on the intranet for our users.

Created a data profiling tool to help identify inaccurate data.

Plans Prepare to demonstrate this technology to IT technical staff in November 2011.



Report Start

07-01-2011

Report End

09-30-2011

Provided By

Mary Spicer

Investigate implementation strategies.

Report Start

10-01-2011

Report End

12-31-2011

Provided By

Mary Spicer

Activity Demonstrated End User Crash Data Query Tool to staff in December 2011.

Plans Continue work on End User Crash Data Query Tool and incorporate changes based on user feedback at demonstration.

Schedule meeting with SHSP data team after product release (February 2012).

Report Start

01-01-2012

Report End

03-31-2012

Provided By

Mary Spicer

Activity End User Crash Data Query Tool was reviewed by the SHSP Data Team.

Plans Continue work on End User Crash Data Query Tool and incorporate changes based on user feedback at demonstration.

Working on putting together an RFP for this tool.

Report Start

04-01-2012

Report End

06-30-2012

Provided By

Mary Spicer

Activity Incorporated changes based on user feedback at demonstration.

Problems NHTSA rep indicated they would provide NE state contacts and SOW examples for us to review. Awaiting those contacts and documents. Once we get the examples, the team will work on a draft SOW.

Plans Continue to work on putting together and RFP for this tool.

Report Start

07-01-2012

Report End

09-30-2012

Provided By

Mary Spicer

Activity Met SHSP Data team on September 26, 2012 to discuss project.

Held conference call with UCONN re: Connecticut’s public query tool.

Plans Plan to pull all comments together from SHSP meeting into one document and provide back to the team prior to the next meeting.

Attend next data team meeting: November 14, 2012. Agenda: SOW and discuss next step.

Get Rob Craver (IT) to provide IT language for SOW document.



Report Start

07-01-2012

Report End

09-30-2012

Provided By

Mary Spicer

Send out rough draft of SOW to Data team.

Identify who will be in the “Contact Us” link for tool.

Report Start

10-01-2012

Report End

12-31-2012

Provided By

Mary Spicer

Activity Attended on November 14, 2012 and December 20, 2012 meetings.

Plans Have VTrans IT look into standards requirements.

Working on rough draft of SOW items for Data Team.

Identify who will be in the “Contact Us” link for tool.

Report Start

01-01-2013

Report End

05-31-2013

Provided By

Mary Spicer

Activity Using VTrans’ Simplified Bid process.

Four vendors identified.

Vendor questions received and responded to.

Two vendors proposing: Proposals received May 10th and bid opening was May 13, 2013.

Plans Await VTrans Audit review of financials.

Distribute Technical proposals to review team.

Review based on evaluation grid.

Schedule vendor evaluation team.

Compare and discuss proposals.

Identify vendor for the project.

Obtain necessary approvals for vendor, if needed.

Write up contract and distribute for signatures.

Contract starts upon execution of contract.

Report Start

06-01-2013

Report End

08-31-2013

Provided By

Mary Spicer

Activity Vendor chosen to perform the tasks is Fountains Spatial, Inc.

Plans Complete VTrans’ in-house contract review process.

Write up contract and distribute for signatures.



Report Start

08-01-2013

Report End

11-01-2013

Provided By

Mary Spicer

Activity Contract is fully executed.

FS has DPPA approval.

Plans Mary working to identify public Joint Application Development (JAD) team.

Evaluate existing system and review current data publications and data users.

Report Start

11-02-2013

Report End

07-20-2014

Provided By

Mary Spicer

Activity Making slow, but steady progress. Vendor still building and testing components and AOT team providing feedback.

Report Start

07-21-2014

Report End

09-17-2014

Provided By

Mary Spicer

Activity There is ongoing vendor interface and testing underway with a launch anticipated later this fall.

Report Start

09-18-2014

Report End

11-12-2014

Provided By

Mary Spicer

Activity Last two standard reports are being reviewed with the vendor and then the VHSA Data and Outreach/Marketing teams will be consulted for how to publicize official website portal launch.

Report Start

11-12-2014

Report End

01-21-2015

Provided By

Mary Spicer

Activity Challenge of interaction with local LEs where there are no longer IT points of contact who can discuss technical details. A hairline away from public launch – have been giving system demos to various user audiences and have been finalizing the public launch publicity.


C-X-1 – Crash Accessibility

Status of Improvement: Planned Status: Planned Revision Date: 16-June-2015



This performance measure is based on the C-X-1 model.

Vermont will improve the accessibility of the crash system and its data.

The state will show measureable progress using the following method:

Identify the principal users of crash data, query the users to assess their ability to obtain the data and record their satisfaction with the timeliness of the response to their request.

The State will also document the method of data collection and the principal users’ responses.



5.8 DPS E-Citation Implementation

5.8.1 Contact

Mr. Christopher Herrick Title: Deputy Commissioner Agency: Vermont Department of Public Safety Office: Deputy Commissioners Office Address: 103 South Main Street City, Zip: Waterbury, 05671-2101 Phone: 802-839-0660 Email: [email protected]

5.8.2 Lead Agency

Vermont Department of Public Safety

5.8.3 Status

Active


eTicket is a pilot based on the implementation proposal in the 2012 Master Business Plan. Regular review and evaluation of all aspects of the effort will be conducted by the eTicket interagency advisory work group with regular reports provided to the TRCC.

The Vermont Department of Public Safety will continue to lead this project, and work closely with the Vermont Agency of Digital Services to continue to build the electronic ticket platform and expand the test pilot program (test pilot #3) of the TraCS e-Ticket software in FFY 2018. This 3rd Pilot would build on the proof in concept and a learning experience from the previous test pilots for the improvements and fixes to the electronic traffic ticket system. The e-Ticket system will be tested at roadside by a sampling of all three branches of the Vermont Law Enforcement Community (VSP, County Sheriffs, Local (Municipal)). Valuable feedback from these law enforcement agencies will help improve and shape the application to be a better roadside data gathering solution. Lessons learned from this pilot would be evaluated and used to help shape the finally state-wide roll out phase (FY19).

Problem Statement: The current non-standard, error-prone paper system for traffic tickets impedes the state’s ability to have complete and accurate citation data available for traffic records data improvement.

Countermeasures: Data recommendations indicated in the 2016 TR Assessment.

Strategies: Implementation and evaluation of all phases of a three phase eTicket pilot.

Goals: Continue to test and refine an eTicket model for statewide use.




5.8.5 Schedule


5.8.6 Budget


NHTSA 405c 2019 $505,140.00


Report Start

07-01-2011

Report End

09-30-2011

Provided By

Gary Nowak

Plans Once the eCitation Business Plan Consultant contract begins, a national survey of electronic ticketing best practices will be conducted. This survey will become part of the master eCitation Business Plan for the State of Vermont. The master plan will be used to develop the statewide eCitation program.

Report Start

10-01-2011

Report End

12-31-2011

Provided By

Gary Nowak

Plans Once the eCitation Business Plan Consultant contract begins, a national survey of electronic ticketing best practices will be conducted. This survey will become part of the master eCitation Business Plan for the State of Vermont. The master plan will be used to develop the statewide eCitation program.

Report Start

01-01-2012

Report End

03-31-2012

Provided By

Gary Nowak

Plans This project is on hold until completion of the eCitation Business Plan Consultant contract and award of eCitation contract.

Report Start

01-01-2013

Report End

05-31-2013

Provided By

Gary Nowak

Plans This project is on hold until award of eCitation contract.

Report Start

06-01-2013

Report End

07-20-2014

Provided By

Gary Nowak

Activity The Independent Review has been completed. As a result of the review, DII has recommended the planning phase continue with the following four primary risks to be further addressed prior to moving to the next phase:



Report Start

06-01-2013

Report End

07-20-2014

Provided By

Gary Nowak

• The impact of significant stakeholders choosing Valcour versus those using Spillman, including the uncertainty in choices yet to be made by VSP.

• The cost analysis over the proposed lifecycle is not adequately funded to cover expected expenses.

• Many of the primary stakeholders do not appear to be appropriately represented in the project team and therefore the assumptions and priorities of the project plan may not be representative or complete.

• The project management structure does not leverage best practice for a project of this size and complexity.

DPS is in the process of preparing a response; likely completion in the next three to four weeks. There was some brief discussion about the meaning of “significant stakeholders” and how the TRCC might help to engage some Valcour owner/user agencies to participate.

Report Start

07-21-2014

Report End

09-17-2014

Provided By

Gary Nowak

Activity DPS management is reviewing aspects of the IR, focus on budget (self-sustaining expectation) and records collection details – see above request for need to fill Project Manager position.

Report Start

09-18-2014

Report End

11-12-2014

Provided By

Gary Nowak

Activity Dean reported that Jen Minkoff hired as a short-term contracted Project Manager to thoroughly respond to the Independent Review so that decisions can be made re next steps in implementation. Need to be confident of the adequacy of the step-by-step viability and sustainability of the project moving forward.

Report Start

11-13-2014

Report End

01-21-2015

Provided By

Gary Nowak

Activity Below is the summary of the TREC report regarding the next steps for the E-Ticket project:

JUNE 2014

Independent Review of the eTicket project identified 12 financial questions and risks:

• Will the system be self-sustaining?

• Project sponsorship & representation



Report Start

11-13-2014

Report End

01-21-2015

Provided By

Gary Nowak

• Integration with other systems

• Policy and governance

DECEMBER 2014

A positive business case presented:

• Fully mitigated risk register

• DII CIO gave approval to proceed with the 2 Test Pilots (2 yrs.)

• Pilot Yr. 1 & Yr. 2 fully funded without revenue recovery

• Project Sponsor: DPS Commissioner Keith Flynn

NEXT STEPS

Hire e-Ticket Project Manager

Establish vendor contract to build eTicket application (Late Winter 2015)

eTicket vendor contract business review by State (Spring 2015)

Pilot #1, 20 Cars, Washington CSD, VSP TOPS (Summer 2015)

Pilot #2, 40 Cars (Summer 2016)

DECISION POINT

Assess pilot performance and lessons learned

Determine long-term funding strategy

Report Start

01-22-2015

Report End

07-22-2015

Provided By

Gary Nowak

Activity Gary reported that DPS is finalizing the contract details with TEG; DII, and then the AG’s office and BGS will be reviewing and signing off. Equipment for all 18 cars for the pilot is close to ready; user agreements will be reviewed with the DPS financial team to be ready to go for the pilot start scheduled for early fall. Mike Driscoll spoke about the productive meeting at DPS with Valcour users re E-Ticket capacity. The Valcour vendor is currently working on data interface with VJIS and interaction with the Judiciary so that they can test with the VTADS legacy system. Everyone was pleased to hear about the progress and happy to have Valcour user representation at the table.

Report Start

07-23-2015

Report End

10-21-2015

Provided By

Gary Nowak

Activity Gary Nowak gave a presentation on the e-ticket implementation project. E-Ticket was a major recommendation from the 2012 Vermont Traffic Records Assessment. The project consists of Pilot 1 (year 1) and Pilot 2 (year 2), which have only been



Report Start

07-23-2015

Report End

10-21-2015

Provided By

Gary Nowak

approved so far by DII and the Commissioner. Under Pilot 1, testing will begin in 20 cars across three agencies: Vermont State Police, South Burlington PD, and Washington Country Sheriff’s office. Testing for both Valcour e-ticket and Spillman e-ticket will be done in the Pilot 1. Part of the project is not just implementing e-ticking, but moving it to the courts electronically. It is not just a Spillman or TraCS solution.

The architecture or process flow is as follows:

1. Officer Scans License and Registration or manually inputs data into TraCS or Valcour

2. Spillman users, TraCS (ticket) information goes to Spillman 3. Once information is in Spillman or Valcour, data flows to VJISS 4. Ticket information goes to Courts 5. Ticket information goes to WebCrash (Pilot 2)

The architecture has been approved and the interface design work has started. Valcour is ready to go. The target date for e-ticket in the cars is 4/1/16. All of the hardware (printers, bar code readers, and mounting brackets) have been installed in the cars, just waiting for the software and the paper to get things rolling. There are some technical challenges that still need to be worked through. At first, we anticipate sending e-tickets to VJISS every couple of hours. Once things are working smoothly, more tickets will be sent electronically.

Funding for 2016 is still being worked out and the procurement review and approval process is slow going. Jen Mincar stated that the contractual processes are confusing and slow. They gave the vendor the win over a year and half ago. She started the contracts process back in March and it still hasn’t been approved.

Pilot 2 will start sometime in 2016/2017. This pilot will integrate the lessons learned from Pilot 1; adding 40 more cars and agencies in the pilot; integration with WebCrash; and the use of barcodes on VT Vehicle Registration and eventually insurance cards

Report Start

10-22-2015

Report End

01-20-2016

Provided By

Gary Nowak

Activity Gary reported that the scope hasn’t changed or the architecture. On track for April still. There are three contracts pending and one is nearly complete. Attorney General is holding up contracts with requirements. Expect the contract with Crosswind to be signed by 2/1/16. Judiciary has removed the requirement for a ticket to be notarized. Question about whether the actual paper ticket will change once this project starts. Dean talked about how there needs to be some leniency or reasonable review of smaller projects with small contracts. Suggested that we call a TREC meeting. Tim Charland and Dean are also going to look into a meeting with the AG’s office, DII and BGS. Angie Byrne raised questions on timeline of April.



Report Start

10-22-2015

Report End

01-20-2016

Provided By

Gary Nowak

Jen Mincar explained that TEG will be delayed but is confident Crosswind will come through.

Report Start

01-21-2016

Report End

04-20-2016

Provided By

Gary Nowak

Activity Gary Nowak covered all phases of the E-Citation. Pilot set to Launch 4/30 (Valcour) and 7/1 (Spillman). -Demo for Valcour, moved a ticket in Valcour to VJISS then flow to the Judiciary Bureau (JB). -Spillman: Launch currently planned for 7/1 based on the contract, but we are working to pull that date in. -Ten cars Valcour, ten cars Spillmen, twenty cars in the first pilot. 2nd phase to have 40 cars. -Waiting on Spillman contract to enable flow from TraCS to Spillman (and on to VJISS and JB). -They have three of the four contracts complete, Spillman still in contract negotiations.

Report Start

04-21-2016

Report End

07-13-2016

Provided By

Jen Mincar

Activity Jen gave a computer demonstration on the program. E-Ticket: Scanning doesn't work in Valcour yet. Pilot 1 still 20 cars and still planned to finish in September. DMV cannot handle 8 digit ticket numbers. Went back to 7 digits. Went to traffic court in WRJ to view how that process goes. Spillman is just about finished…waiting on DPS Commissioner to sign. All connections are set up. Now need to start pilot. Have 10 cars started and officer training is all done. Scanning issue - Spillman runs on USB and TrACS runs on ComPort(?). Will scan but cannot get the "mailing" address in many cases. LE will need to review and fix. TEG contract ends 8/1 but need them to talk to Spillman and they cannot until the contract is fully executed. This contract should be amended.

• Sean Thompson has left, position is covered. • Scanning not working, focusing on that to get working. • Key process running fine, some issues with number of digits for DMV. • All signatures in for Spillmen, All contracts are good to go. • Upcoming key dates:

• Officer training 6/2 • 7/18 : Valcour launch • 10 cars ready to roll • 7/15-9/15 : Create TraCS/Spillmen exchange • 7/13 : TRCC meeting



Report Start

04-21-2016

Report End

07-13-2016

Provided By

Jen Mincar

• August: Stakeholder meeting • By 8/1 : TraCS launch (warnings only) • 10/1/16 : Start of Pilot 2 (will need to pick pilot agencies)

• Fall 2016 : NHTSA project audit.

• Budget looking good. No rollover funds this year. On track.

• Open risks - Issue

• Spillmen procurement delay impacts TEG contract,

• Bar coding issues.

• Celebrations for eTicket…

• Valcour front end is ready

• Valcour / VJISS / JB readiness

• TraCs Readiness

• User community ready and wanting this up and running.

Report Start

07-14-2016

Report End

10-11-2016

Provided By

Jen Mincar

Activity Went live with E-Ticket. Had over 170 e-tickets issued and about 20 e-warnings by VSP. Officer feedback is pretty good. Continue to rollout to about 10 additional agencies. Working on commercial violations next. Spillman contract was signed but now they cannot work with us until May 2017. MDT set up is taking longer than expected.

Report Start

10-12-2016

Report End

01-18-2017

Provided By

Jen Mincar

Activity Jen Mincar gave the following status: • Starting Pilot 2, stakeholder meeting to approve agencies to be involved. • Looking at what they need to get up and running. • 750+ eTickets submitted so far. Great feedback from agencies. • Working on TraCS/Spillman implementation - planned to start in May 2017. • TraCS has been received by VSP and they want to move ahead quickly

Problems Contracting - 3 contracts coming up for extension, one hasn't been started and one needs to be created. DPS - VTrans agreement needs to be set up. DMV Barcodes on Vehicle Registration scanning not available in Spillman yet DMV has not put the barcodes on registrations but plans to. Fear putting them on registrations because they cannot recall them. Have they sent it through to check to see if it meets the AAMVA standards? Program sustainability? What happens if the funding goes down? How do they self-sustain that?



Report Start

01-19-2017

Report End

04-19-2017

Provided By

Jen Mincar

Activity Average of 5-10 tickets or warnings issued per day. Pilot 2 is going to bring on more agencies so this will increase ticket/warning numbers. Additional 40 vehicles total - 10 of them are VSP, others from another CSD, Barre City, Vergennes. Budget - given $366k, spent $38k Doing homework on making this a self-sustaining project eventually. Looked at fees on tickets, but politically not a good time. Valcour currently issuing the tickets. Moving to TraCS next. Contracting is a challenge. TEG has signed, awaiting DPS signatures. Connectivity is a significant roadblock. It costs about $800 per setup. Some agencies said if they had to pay for it they wouldn't do it. DMV moving forward with putting barcodes on registrations. (Donna Attig) Spillman cannot accept barcodes currently. Unknown when this would happen. How do you handle driver changes? Updating is a by-machine change. Brad is changing remotely, but he has to do it for each machine.

Report Start

04-19-2017

Report End

10-11-2017

Provided By

Jen Mincar

Activity

Contracting

• Issues: Procurement does not align with technical schedule needs

• Spillman amendment for Pilot 2 - still not executed; Started March 2017

• PM contract expires 9/30/17

• Recommendation

• FY18 Planning session with Procurement

• Streamline the amendment process

Spillman/TraCs architecture

• Issue: Additional internal support required



Report Start

04-19-2017

Report End

10-11-2017

Provided By

Jen Mincar

• Recommend Move to .5 PM and .5 Tech Support

Program Sustainability long-term

• Issue: FY18 Grant funded, but Fy19 Grant not guaranteed; need to find

a long term self- sustaining model

• Recommendation: pursue fee on Tickets

Sponsorship and Admin support

• Issue: Low level of support/low prioritization

• Recommendation:

• Monthly project review with Sponsor & admin OR

• Find a new sponsor OR

• Move the project to ADS or Judiciary OR

• Cancel the project.

Report Start

10-11-2017

Report End

01-17-2018

Provided By

Jen Mincar

Activity • 450 eTickets issued in TraCS and sent electronically to JB (started 11/1/17)

• 3600+ eTickets issued in Valcour and sent electronically

• 14 of 74 agencies have eTicket (20%)

• 0 dismissals/voids of eTickets

• Increase in Ticket volume and revenue in 2016

• TECHNICAL SOLUTION FOR SPILLMAN AGENCIES: Testing is ongoing on the Spillman interface. We loaded a TraCS citation into Spillman automatically and are crawling through the data for accuracy. There are two additional fields that we will need to add to the vcvc form that are required by our Spillman dB. We expect this full electronic solution to be in place by 2/15/18, possibly sooner.

• PILOT 2: eTicket training for three Valcour agencies occurred on 12/27/17. They will be starting to issue eTickets soon. 7 additional agencies have equipment and will start eticket soon. Need to put together PO for the next batch of hardware.

• eTICKET CONTRACT FOR COMMERCIAL VIOLATIONS : For Valcour users: DMV is in the final stages of testing and expect to deploy commercial violations in mid January.



Report Start

04-19-2017

Report End

10-11-2017

Provided By

Jen Mincar

Report Start

01-18-2018

Report End

04-19-2017

Provided By

Jen Mincar

Activity FY19 and Beyond

Scope to finish the rollout:

• A total of 450 LE vehicles need to be outfitted. 64 of 450

are currently outfitted with eTicket equipment (printers,

scanners, paper).

o VSP – 180 additional vehicles left to bring online

after FY17 (20 of 200 are currently deployed)

o Additional LE agencies – 200 vehicles left to bring

on line (44 of 244 vehicles deployed)

• 380 Vehicles left to outfit with equipment

One Time Cost: $380K+

• Equipment and Supplies: $380K

o 380 vehicles left to deploy

o Program requires $1K per car for equipment and

supplies.

• Note that there could be additional functionality required

by certain agencies prior to implementation. This

additional functionality could cost some money but has

not been definitively scoped out yet. For example, Fish &

Wildlife utilizes VCVC forms but could require some

additional offenses added to our solution front-ends. The

cost for this and other functionality could be between

$50-$100K and is not figured into this financial projection.

• Cost projections do not include equipment repair or

replacement costs. To date the costs have been $0 and

we expect the equipment to last 10 years.

Yearly Costs/Ongoing Costs: $140K

• Contract Maintenance: $90K/year

o State of Iowa/National Model Fee - $70K/year

o TraCS Support - $15K/year

o Valcour Support - $0K/year (included in master

support contract)



Report Start

04-19-2017

Report End

10-11-2017

Provided By

Jen Mincar

o Spillman Support - $0K/year (included in master

support contract)

o VJISS - $5K/year

• Resource: $50K/year

o (Internal or external) tech support and program

manager

o $10K of additional cost if it’s grant funded (indirect

costs)

Remaining Financial Schedule (Years 4-10 of 10 years):

• Currently Rolling out at 40 cars per year will take the full 10

years to deploy


See Section 3.1.1 Citation Completeness and Section 3.1.2 Citation Uniformity for performance

measures.



5.9 Horizontal Curve Data Inventory on Local Roads

5.9.1 Contact

Mr. Mario Dupigny-Giroux Title: Traffic Safety Engineer Agency: Vermont Agency of Transportation Office: Office of Highway Safety, Governor’s Highway Safety Program Address: One National Life Drive, 5th Floor City, Zip: Montpelier 05633 Phone: 802-828-0169 Email: [email protected]

5.9.2 Lead Agency


5.9.3 Status

Complete


Vermont’s roadway files contain information on horizontal curves for state maintained roads only (state maintained roads represent approximately 17% of all road miles in Vermont). However, Vermont’s roadway files do not contain data on horizontal curves for non-state maintained roads. Using the data elements available in the crash data alone, VTrans is currently capable of doing a very simplistic crash risk factor analysis on the local roads system. For example, considering specifically rural local roads, VTrans can tell that 59% of all the crashes are single vehicle crashes, and that of the 59% single vehicle crashes, 57% are taking place on horizontal curves. But this is where the analysis ends.

Because Vermont roadway data on the local roads system does not include any information on curves, VTrans is not able to continue the analysis to the next level and identify the curves on the local road network that are most at risk and were resources should be spent.

To be able to perform more advanced analyses, an inventory of horizontal curves on the local road network that would contain location and other relevant characteristics element is needed.

There are several ways that an inventory of horizontal curves on non-state maintained roads could be done, varying in cost and efforts. As was done for the state maintained system, curve data could be obtained from records plans or by traveling the entire network using a roadway data collection van. However, a more practical and cost-effective way would be to automatically extract curve features from GIS maps.

Such a fully automated method for the extraction of horizontal curve data from GIS roadway maps was developed by the Traffic Operations and Safety Lab at the University of Wisconsin. The University of Wisconsin has worked with a number of state department of transportations and



has successfully applied this process (90 to 95% curve detection) in Delaware, Florida, Iowa, Michigan, New Hampshire, New Jersey, Wisconsin, and Wyoming.

VTrans’ Office of Highway Safety seeks funding to contract with the University of Wisconsin to apply this process to Vermont local roads classified as Class 2 (2,775 road miles), Class 3 (8,537 road miles) and Class 4 (1,634 road miles). This program would work with a contracted lab -- to be determined, not specifically the University of Wisconsin.

The objective of this project is to create an inventory of highway horizontal curve data on non-state maintained roads from Vermont’s GIS roadway map that will include the following data elements: curve location, curve length, radius, degree of curvature, curve direction, and curve type. The project will be accomplished through the performance of three tasks, and it is anticipated that the project will take eight months to complete.

The three tasks proposed to accomplish the project consist of Preprocessing the Highway GIS Data (preprocessing/dissolving roadway segments by road name, road direction, and highway class and verifying the processed centerline shapefile for breaks of curves at nodes dividing two consecutive dissolved segments), Calibrating the Algorithm to Vermont Data (calibrating the algorithm using a sample of 200 plus curves based on ground-truth curve data and the preprocessed GIS centerline data. To find the optimal parameter values that maximize the accuracy of curve detection) and Extracting the Data.

The deliverable will be a curve layer/shapefile that can be easily integrated with VTrans’ existing asset management and roadway inventory datasets. The creation of this inventory of horizontal curves and data elements will improve the completeness of the roadway data file by providing data that currently does not exist on the local network of class 2, class 3 and class 4 roads. The project is anticipated to provide the identification of at least 90% of all the horizontal curves on over 12,946 miles of roads.

Because the curve inventory will be conducted on the entire universe of class 2, class 3 and class 4 roads using the same methodology, uniformity in the data elements for this category of roads will be achieved. This data collection effort is a task that is listed in the 2012-2016 Vermont Strategic Highway Safety Plan as one of the strategies to improve the completeness of highway data for the interest of safety.

5.9.5 Schedule

Complete




Report Start

10-11-2016

Report End

10-11-2016

Provided By

Mario Dupigny-Giroux

Activity RFP went out and they had two respondents. Picked one and plan to start on this soon.

Report Start

10-12-2016

Report End

01-18-2017

Provided By


Activity Extracting GIS curve data from: - December 19, 2016: The contract was executed. - December 23, 2016: A zipped file geodatabase containing the LRMs that VTrans generates, the master road centerline data layer in its native format, and the curve events on the last TWN LRM, was provided to the consultant. - January 4, 2017: Web kick-off meeting. Discussed GIS geodatabase. Not a lot that needs to be fixed (5 cutbacks, 7 dangles, 403 loops). VTrans will set up a computer for direct access to master data. VTrans will send the algorithm used to generate route names. Talked about how to prioritize work.

Report Start

01-19-2017

Report End

04-19-2017

Provided By


Activity The synchronization process between Vermont and the Consultant’s local copy of the centerline file was fully streamlined by March 14, 2017. The Consultant lead a web training session on March 28, 2017 with VTrans staff to demonstrate the use of Curve tools and explain how to perform centerline reviews and edits. Video of the training was recorded and has been provided to VTrans for reference and use in training others.

Report Start

01-17-2018

Report End

04-19-2018

Provided By


Activity Presentation to the TRCC on the Horizontal Curve Data Inventory on Local Roads. This demonstration of the data was able to show the increase in accuracy of the current mapping and increase the completeness of the data.



5.10 Model Inventory of Roadway Elements Collection at Intersections

5.10.1 Contact

Mr. Mario Dupigny-Giroux Title: Traffic Safety Engineer Agency: Vermont Agency of Transportation Office: Office of Highway Safety, Governor’s Highway Safety Program Address: One National Life Drive, 3th Floor City, Zip: Montpelier 05633 Phone: 802-828-0169 Email: [email protected]

5.10.2 Lead Agency


5.10.3 Status

Planned


Data collection is underway for an estimated number of 16,314 intersections. This work is being done in an office setting using tools such as Google Earth, video log and GIS. The FDEs listed in FAST Act will be the primary focus of this project. It is possible that other elements could also be collected based on the MIRE, Version 1.0 guidance.

Problem Statement: There are about 16,314 intersections on the Vermont Federal Aid Road Network. The roadway inventory file currently maintained by VTrans contains information for only 9% of the intersections on this network. VTrans does not have a complete comprehensive database of intersections. This lack of data availability in Vermont prevents engineers and transportation planners from using systemic safety approaches and state-of-the-art tools such as the Highway Safety Manual predictive models, SafetyAnalyst and IHSDM in performing highway safety analyses.

VTrans received TRCC funding for a project to collect MIRE data at intersections on the Federal Aid Road Network for FFY18. In Feb 2018, a consultant was hired. This consultant will populate the inventory file for 4,000 intersections by the end of Sept 2018. At that time, VTrans’ roadway file will have complete information for 25% of the intersections on the Federal Aid Road Network. Complete data will be missing for 75% of the intersections.

Strategies: The Federal Highway Administration (FHWA) developed a list of elements critical to safety management and analysis called Model Inventory of Roadway Elements (MIRE). FHWA established a subset of the MIRE as part of the HSIP Final Rule changes to 23 CFR Part 924, effective April 14, 2016. This subset is referred to as the fundamental data elements (FDEs).



The intent of this project is to complete the collection of the FDEs and of other MIRE elements of interest to VTrans based on the MIRE, Version 1.0 guidance for all intersections on the Federal Aid Network.

Goals: Improve the completeness of intersection data on the Vermont Federal Aid Road Network.

Objectives: Collect 100% of the FDEs and the other MIRE data listed previously for 12,341 intersections on the Federal Aid Road Network by end of FFY19 to give VTrans a complete inventory of intersections covering 100% of the intersections on this network.

5.10.5 Schedule


Report Start

10-11-2017

Report End

01-17-2018

Provided By


Activity VTrans completed the evaluation and testing of Esri Roads & Highways to create intersections and determined that this tool was not suitable as originally anticipated.

Other means to generate a database of intersections were pursued and over the course of the last quarter, there has been significant work in developing an intersection database, and defining the schema based on internal VTrans, MIRE, and Safety Analyst requirements. The data is in a format that can be supplied to a consultant for updates and will be initially populated with as many fields as VTrans has data for. The development of the data model for the intersections required a search of other State DOT models, acquiring some of this DOT data, inquiry to GIS staff at other DOTs, and assessing a workable schema that can be maintained by VTrans. The data model includes each node from the road centerline data layer and a layer that reflects each leg or approach to each node, which comprise the intersections.

VTrans will continue to populate as much of the intersection data model with data that currently exists which will aid in identifying gaps in the attributes for the consultant to update. To aid in this data population process, efforts are being made to leverage intersection data and select fields from other Sections in the Agency to augment the contents of the fields within the intersection data for both nodes and legs.

VTrans plans to issue a RFP by the end of January 2018 to seek a consultant that will help with the data collection of the elements that are missing.

Report Start

01-17-2018

Report End

04-19-2018

Provided By


Activity VTrans completed a scope of work and contracted with one of its retainer consultants.


July 1, 2018 Page 100

Report Start

01-17-2018

Report End

04-19-2018

Provided By


VTrans reached out to support staff for SafetyAnalyst and IHSDM to further discuss the determination of Minor and Major Roads. VTrans completed a data model by leveraging the existing road centerline data layer at VTrans and building out the necessary fields to support the Minimum Inventory of Roadway Elements (MIRE) and fields to support the Safety Analyst application. VTrans completed a data dictionary to aid in defining each field. VTrans held a kick off meeting with the consultant on March 15, 2018. VTrans provided the data dictionary and intersection schema to the consultant

5.10.6 Budget


NHTSA 405c 2019 $179,000.00


July 1, 2018 Page 101

5.11 AOT Statewide Reporting System Upgrades

5.11.1 Contact

Ms. Mandy White Title: Crash Technician Agency: Vermont Agency of Transportation Office: Highway Research Address: 1 National Life Building, Drawer 33 City, Zip: Montpelier 05633 Phone: 802-595-9341 Email: [email protected]

5.11.2 Lead Agency


5.11.3 Status

Planned


Problem Statement: The online data entry system for law enforcement crash reporting and the VTrans legacy data records system require periodic evaluation for upgrades and improvements.

Countermeasures: Data improvement recommendations contained in the 2016 Traffic Records Assessment.

Strategies: Hardware and software upgrades and development of a plan with recommendations to improve run-time field loss of law enforcement connectivity in rural areas of the state.

Goals: This is a project for ongoing enhancement to the crash data interface. The FFY2018 goal is to complete the following three components:

1. Review the new MMUCC standards recently released along with the Uniform Crash Report Form and implement any necessary changes.

2. Add three additional states to the auto population section in Web Crash. Currently, Web Crash has three state. This tool has proved useful to law enforcement in documenting driver and vehicle data, expediting traffic stop time and validating the data point of entry.

3. Build a Crash Collection Stand Alone Client Application. The client application will

provide law enforcement with the ability to create and submit crash reports from the field. When connectivity is lost, law enforcement will be able to continue with crash reporting and submit at a time when connectivity is re-established. The Client App was a recommendation in both the Vermont 2012 Crash Data Improvement Program



July 1, 2018 Page 102

(CDIP) review as well as in the 2012 Traffic Records Assessment. This feature will provide for improved timeliness in reporting, per the CDIP and TR Assessment.

5.11.5 Schedule


5.11.6 Budget


NHTSA 405c 2019 $0.00


July 1, 2018 Page 103

6. Traffic Records Data Standards Compliance

6.1 Model Inventory of Roadway Elements (MIRE) Compliance

In this section, Vermont has incorporated specific quantifiable and measurable anticipated improvements for the collection of MIRE fundamental data elements.

6.1.1 Mire Data Collection Status

Which MIRE fundamental data elements are currently being collected and which MIRE fundamental data elements are not being collected? On which functional classes of roads are/are not they being collected?

The listing of the MIRE FDEs with collection status is in process of being developed as an inventory of existing data sources is being created across a series of sections within the Vermont Agency of Transportation.

Which business office(s) in the State DOT collect, receive, and maintain the MIRE fundamental data elements? How are the data stored and managed?

MIRE fundamental data elements are collected, received, and maintained by several sections and units within the Vermont Agency of Transportation (VTrans), including the following:

• Policy, Planning & Research - Mapping Section

• Asset Management & Performance - Data Management Section

• Transportation Systems M Management & Operations - Traffic Research Unit

The data steward is subject to the core business function and data need of the section, thus the AADT and traffic data is collected by Traffic Research, Mapping maintains the road centerline, functional class, and linear reference, and AMP – Data Management maintains HPMS data, which is leveraged for the MIRE fields.

Data is stored in GIS format in ArcSDE as features or event tables. Current data may not be stored in the MIRE schema and may require translation to meet MIRE requirements.

Who can access the MIRE fundamental data elements for safety analyses, and what steps are necessary to access the data? Are systems planned or already implemented to facilitate access to the data (e.g. online portals)?

Data is currently open to VTrans staff that has access to GIS tools and some data is available through an open data portal. As noted, the data may not be in the exact schema or have domains that match the MIRE requirements and would need to go through an extract, transform, and load (ETL) process to be leveraged by some systems. Systems to exist at VTrans to provide open data and more data is being added to this system when needed, with an informal plan to make more data accessible.


July 1, 2018 Page 104

Which agency/office/individual/committee(s) have authority and responsible for determining the improvements needed to achieve compliance with the MIRE fundamental data elements requirement?

The VTrans Office of Highway Safety has this authority and responsibility.

6.1.2 Data Collection Methodology

For the MIRE fundamental data elements that are already being collected:

• What methods are being used to collect the MIRE fundamental data elements?

Annually road centerline data is updated with known changes from municipalities. This data forms the base of the MIRE and covers many of the core fields. Traffic data is collected for some higher functional classes on an annual basis, if not more frequently, whereas lesser functional class, such as major collectors and minor collectors may have infrequent updates and local roads may not have any dated collected, but may have traffic estimates. The Traffic Research Section needs to provide details on frequency and completeness of the count data.

Road centerline data collection is typically done via use of the GIS and orthophotography and lidar for proper alignments. Some field inventory is performed in cases where questions may arise. VTrans has mapped all public highways to at least 1:5,000 with much of the centerlines digitized at higher resolutions.

Traffic data collection is typically collected via tube counters or permanent counters at various frequencies.

VTrans needs to define the collection methodology for each element better, but this has not been done due to time and resources.

• How often do they collect the data?

Some data is collected annually and some data is not collected at the moment.

Intersection data is not collected yet. AADT is collected on a defined cycle, which needs to be provided by the Traffic Research Section.

• What Quality Control/Quality Assurance processes are performed before the data is entered into the database.

The road centerline data goes through a series of quality assurance processes to insure correct attribution, topological validity and mileage assessments. A defined quality control and quality assurance process needs to be defined for each element, but this has not been done at this time.


July 1, 2018 Page 105

6.1.3 Coordination with Other Agencies

For MIRE fundamental data elements that are NOT currently being collected:

• Who owns the roads where the elements are not being collected (e.g., State, local government agencies, Trial Governments, Federal Land Management Agencies, etc.)?

Some elements are not being collected on state and municipal highways, but there is coordination with regional planning commissions, who work directly with towns, cities, the gores and grant within Vermont. As a plan is formulated, there will be an initiative to move forward in data collection, with coordination with the RPCs and locals as needed. Vermont does have federal highways, under several federal agencies, which will need to be coordinated to gain this data.

• Do the agencies that own those roads collect any of the MIRE fundamental data elements?

It is uncertain as this time to what extent the other agencies will collect MIRE FDEs at this time and an assessment of this may be done as part of the planning process for the FDEs collection.

• What mechanisms are needed to share data among those agencies that collect, store, maintain, and use the MIRE fundamental data elements?

This has not been fully defined at the moment, but a system exists for GIS within the Agency of Transportation, and this may provide storage for the MIRE FDEs and the existing GIS portal may be used to allow access to the data for others. Due to resources, a full plan of who data will be shared, collected, stored, used, and maintained has not been fully defined or articulated in a defined document.

6.1.4 Prioritization of MIRE Fundamental Data Elements Collection

For additional data that needs to be collected to meet the MIRE fundamental data element requirement:

• What data elements will be collected in the short (1-3 years), medium (4-6 years), and long (7-9 years) term?

There are some FDEs that already exist on the federal aid system due to HPMS requirements, or existing collection to support other programs within VTrans. These can be updated and process to defined to meet the MIRE data schema within the short term. Intersection data and other segment data may take time to develop and require medium term, and AADT collection and data on the more rural local roads may be a longer term process. A data acquisition plan needs to be defined as part of the assessment of what data already exists and a gap analysis within VTrans.

• What collection technologies and/or methodologies are anticipated to be used?


July 1, 2018 Page 106

This is not defined at the moment, other than VTrans uses GIS technology and this would provide a technology solution for the MIRE FDEs. Additional technology and methodologies have not been defined.

• Who is responsible for collecting the data?

This has not been defined at the moment.

• How will it be made available to the State DOT?

If VTrans collects the data, it would be accessible, if collected by the RPCs or locals, a process will need to be defined for the data exchange.

• What will be the update cycle for the collection of the data?

This is not defined at the moment, but would be dependent on each element or grouping of elements and subject to the type of system that is being inventoried.

6.1.5 Costs and Resources for MIRE FDE Data Collection

What are the estimated costs, staffing, and other resource requirements to collect and maintain the MIRE fundamental data elements?

Estimates of cost, levels of staffing, or resource requirements have not been defined for collection of the MIRE FDEs.

Who will incur those costs?

Funding of the collection, storage, and maintenance of the MIRE FDE data has not been assessed, other than there are not currently adequate funds or staffing for the level of effort that is expected.


July 1, 2018 Page 107

6.2 Model Minimum Uniform Crash Criteria (MMUCC) Compliance

Vermont has been approved for a NHTSA Go Team MMUCC V5 compliance review of the crash form. Once review is complete, Vermont will form a working group to address compliance improvements.

Vermont is currently in compliance with the definition for “Suspected Serious Injury (A)” from the MMUCC 4th edition. Compliance includes the following:

• Collecting and accurately aggregating MMUCC v4 attribute “Suspected Serious Injury (A)”

• The State’s crash database, data dictionary, and crash report user manual employs the verbatim terminology and definitions for this attribute from the MMUCC v4 standard.

• The State’s crash form employs the verbatim MMUCC v4 “Suspected Serious Injury (A)” attribute

• Ensure the seven serious injury types covered by the attribute are not included in the other attributes listed in the State’s injury status data elements.

6.3 National Emergency Medical Services Information System (NEMSIS) Compliance

Vermont’s EMS run reporting system (SIREN) is NEMSIS V3 compliant.


July 1, 2018 Page 108

7. Traffic Records Assessment Update

7.1 State of Vermont Traffic Records Assessment Update

The State completed a NHTSA Traffic Records Assessment on February 2, 2017. The State’s response to each recommendation is listed below. If a project plans to address a recommendation within the next FFY plan year, the related project is listed. See related project for performance measures.

7.1.1 Crash Recommendations

1. Improve the procedures/process flows for the Crash data system that reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: Vermont plans to continue to train more law enforcement officers to use Web Crash electronically in the field as well as researching technologies that could make this easier when connectivity is a problem. We will plan a MMUCC review to see where we are at with our most current crash report form. Since the Traffic Records Assessment, we changed the injury codes on the crash report form to reflect the new MMUCC elements and the manual reflects the same definition as well. We will also continue to explore new interfaces with other traffic records programs such as EMS and enhance those we currently have.

Related Project: AOT Crash Data Reporting System

2. Improve the data quality control program the Crash data system to reflect best practices

identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: Vermont will explore possible ways

to track errors that make it through to the database. Crashes are not “rejected” in Web

Crash because they cannot be submitted without a minimum amount of data. We will

also look for ways to institute a more formal performance measurement monitoring

program.

Related Project: AOT Crash Data Reporting System

7.1.2 Data Use and Integration Recommendation

1. Improve the traffic records systems capacity to integrate data to reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: The State of Vermont Department of Information and Innovation will continue existing efforts to implement a formal data governance process.

The TRCC continues to promote the development of a Traffic Records Inventory of the

State’s traffic records data systems (i.e. crash, roadway, ISS, citation, vehicle, driver, etc.).


July 1, 2018 Page 109

The inventory will contain or reference the data dictionaries, ownership, and business

rules for each of the constituent data systems

Related Project: No related project.

7.1.3 Driver Recommendations

1. Improve the description and contents of the Driver data system to reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: The VT TRCC will promote the development of a State of Vermont Driver Data Dictionary containing data element definitions, validations, and links to other data sets (e.g. vehicle, crash).


2. Improve the data quality control program for the Driver data system to reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: The VT TRCC will emphasize the

importance of data quality control programs to each of the traffic records data

component systems, including the Driver data system.


7.1.4 Roadway Recommendations

1. Improve the data dictionary for the Roadway data system to reflect best practices


State Accepts Recommendation. State Response: VTrans understands the

recommendation and can see the benefits of a single data dictionary. There are currently

different data systems and processes, each with specific data schemas that may not be

able to be pulled together into a single dataset, but could have their schemas defined in

a single data dictionary. This could be done provided adequate resources are available.

Related Project: VTrans will need to define a specific project to address this issue,

provided resources can be allocated.

2. Improve the data quality control program for the Roadway data system that reflect best

practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: Quality assurance and quality control

are important to the integrity of any data system, and VTrans needs to review the

recommendation and evaluate to what extent this can be implemented within the

existing system.


July 1, 2018 Page 110

Related Project: VTrans will need to define projects associated with this recommendation, which has not happened at this time.

There are limited resources and staffing available to perform all the necessary tasks to

support collection, storage, and analysis of the roadway data elements and as much as

we may want to implement certain solutions, resources may not be available to do so.

7.1.5 Vehicle Recommendations

1. Improve the description and contents of the Vehicle data system to reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: Vermont believes that NMVITS, once implemented, will instituted many best practices.

Related Project: No related TRCC project; however, NMVITS is an ongoing project within

the Vermont Department of Motor Vehicles.

2. Improve the applicable guidelines for the Vehicle data system to reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: Vermont believes that NMVITS, once implemented, will instituted many best practices.



3. Improve the data quality control program for the Vehicle data system to reflect best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: Vermont believes that NMVITS, once

implemented, will instituted many best practices.



7.1.6 Citation/Adjudication Recommendations

1. Improve the applicable guidelines for the Citation and Adjudication systems to reflect best

practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: The Vermont Judiciary has embarked

on a multi-year initiative to implement a Next Generation Case Management System (NG-

CMS). This initiative, currently in pilot phase II, and moving into Phase III; a statewide

implementation plan. This will drive and enable the transformation of the Judiciary’s case

management process from a paper-driven to an electronic-focused business model that

will improve access to justice for our citizens, strengthen inter-agency communication,


July 1, 2018 Page 111

and enable more efficient court operations through faster court case initiation, more

accurate electronic case files, and improved document availability and accessibility.

Additionally, this initiative will facilitate improvements to the E-Ticket Upgrade project.

Related Project: DPS E-Citation Implementation

2. Improve the interfaces with the Citation and Adjudication systems to reflect best practices


State Accepts Recommendation. State Response: The Vermont Judiciary has embarked

on a multi-year initiative to implement a Next Generation Case Management System (NG-

CMS). This initiative, currently in its planning phase, will drive and enable the

transformation of the Judiciary’s case management process from a paper-driven to an

electronic-focused business model that will improve access to justice for our citizens,

strengthen inter-agency communication, and enable more efficient court operations

through faster court case initiation, more accurate electronic case files, and improved

document availability and accessibility. Additionally, this initiative will facilitate

improvements to the E-Ticket Upgrade project.

Related Project: DPS E-Citation Implementation

7.1.7 EMS/Injury Surveillance Recommendations

1. Improve the interfaces with the Injury Surveillance systems to reflect best practices


State Accepts Recommendation. State Response: The TRCC will review and evaluate

integration opportunities of the various traffic records data sets.

Related Project: SIREN

2. Improve the data quality control program for the Injury Surveillance systems to reflect

best practices identified in the Traffic Records Program Assessment Advisory.

State Accepts Recommendation. State Response: The TRCC will promote the use of

completeness and accuracy performance measures for Vermont’s Injury Surveillance data

systems.

Related Project: SIREN

Vermont Traffic Records Strategic Plan for FFY2018 · 2018-12-21 · Vermont Traffic Records...

Documents

Transcript of Vermont Traffic Records Strategic Plan for FFY2018 · 2018-12-21 · Vermont Traffic Records...