APPENDIX A

Implementation Roadmap

CONTENTS

Objective

Implementation Roadmap Steps

Implementation Work Plan

Task A. Identify Implementation Champions

Task B. Submit Request for Funded Roadmap Option

Task C. Undertake Roadmap Steps 1 to 4

Task D. Refine Roadmap Activities (if funded)

Task E. Undertake Roadmap Steps 5 to 9 (if funded)

Task F. Submit Report Documenting Process and Outcomes (if funded)

Task Schedule

Objective

The goal of the implementation roadmap is to facilitate implementation of the Project 17-109 research results in the AASHTO Highway Safety Manual (HSM) and in the FHWA Crash Modification Factors Clearinghouse (CMFC). The objective of this document is to describe a roadmap that will achieve the aforementioned goal in a cost-effective and timely manner.

The roadmap documented herein identifies specific steps and timeframes that are intended to encourage persons overseeing the HSM and CMFC to implement the Project 17-109 findings in their respective reference works. The roadmap is envisioned to be implemented at the end of Project 17-109. No project resources will be used to undertake the specified roadmap tasks.

The Implementation Roadmap is intended to complement the implementation guidance to be prepared in Task 10 of Project 17-109. The roadmap will not duplicate the implementation guidance.

The tasks identified for the roadmap have resource requirements. Given the uncertainty of securing funds to remunerate these resources, a scalable roadmap has been developed to accommodate two funding options. A “funded” roadmap option is described to address the case where external implementation funds can be obtained for roadmap implementation. In addition, a “pro bono” roadmap option is described to address the case where external funds are not available.

The next section describes the steps (and associated timeframe) of the implementation roadmap. Then, the subsequent section describes a series of tasks associated with an implementation project that manages the execution of the roadmap.

Implementation Roadmap Steps

The implementation roadmap consists of the nine (9) steps identified in Table 1. The first four steps represent the “pro bono” roadmap option. These steps entail identification of (a) key HSM and CMFC

oversight persons and (b) HSM and CMFC stakeholder groups. The implementation team will then meet with the oversight persons and stakeholder groups to inform them of the Project 17-109 products that are suitable for implementation in the HSM and CMFC. These four steps are envisioned to be undertaken during the last few months of Project 17-109.

If implementation funding is obtained, then steps 5 to 9 will be undertaken. In this regard, the nine-step sequence represents the “funded” roadmap option. It includes the first four steps described in the previous paragraph. Steps 5 to 7 involve more in-depth interaction with the HSM and CMFC oversight persons and stakeholders for the purpose of identifying and resolving specific issues and challenges foreseen in implementing the Project 17-109 products. For example, the HSM oversight persons may be concerned about where and how the Project 17-109 products could be portrayed in the HSM. To allay this concern, the implementation champions may prepare (in step 7) proposed draft HSM content (i.e., text, tables, and figures in HSM format) that is focused on describing the correct use of the Project 17-109 CMFs in one or more existing HSM chapters. Steps 5 to 9 of the roadmap are planned for completion by the 13^th month of the implementation project (which should equate to about nine months after the end of Project 17-109).

Table 1. Activities associated with the implementation roadmap.

^a – time by which the step is to be completed, relative to the start of the implementation activities.

Implementation Work Plan

This section describes a work plan for executing the Implementation Roadmap submitted in Task 10 of Project 17-109. It is envisioned to consist of six tasks. The first three tasks will describe the work to be undertaken to implement steps 1 to 4 of the roadmap. The last three tasks will describe the work to be undertaken to implement steps 5 to 9 of the roadmap. These latter tasks will require funding to execute. A schedule for these tasks is provided in the last section.

Task A. Identify Implementation Champions

The objective of this task is to identify candidate members for the implementation team, finalize the composition of this team, and coordinate work assignments among team members. The team members will serve as Project 17-109 implementation champions. They should include members of the research team, project panel, and project partners (e.g., individuals that supported the Project 17-109 data collection activities).

Early activities by implementation team members will be to (a) identify candidate sources of funding for the “funded” roadmap option and (b), if needed, refine the scope of the two roadmap options (i.e., “pro bono” roadmap and “funded” roadmap). These refinements may be needed to tailor the implementation work plan tasks and roadmap steps to meet the criteria of identified funding sources. Candidate implementation funding sources that will be considered include, but are not limited to, NCHRP (e.g., Project 20-44 Implementation Support Program) and FHWA (e.g., Transportation Pooled Fund Program TPF-5[516, HSM 2^nd edition Implementation]).

Task B. Submit Request for Funded Roadmap Option

During this task, one request for implementation funds will be prepared for each viable funding agency identified in Task A. The request is envisioned to be in the form of an implementation project application. It will likely require the identification of a state DOT or FHWA employee to submit the application and serve as a project champion during the agency’s application review process.

Task C. Undertake Roadmap Steps 1 to 4

The objective of this task is to complete steps 1 to 4 of the implementation roadmap (as shown in Table 1). During step 1, the implementation team will identify the key people providing oversight into the content of the HSM and the CMFC. For the HSM, this step will entail contacting the chairperson of the AASHTO HSM Steering Committee. For the CMFC, this step will entail contacting the CMFC contract manager with the FHWA Office of Safety.

In step 2, the implementation team will identify the HSM and CMFC stakeholder groups. For the HSM, this step will entail contacting the chairperson of the TRB’s Standing Committee on Safety Data, Analysis and Performance. For the CMFC, this step will entail contacting the manager of the CMFC at the University of North Carolina Highway Safety Research Center.

During steps 1 and 2, the implementation team will provide the contacts with a copy of the draft Project 17-109 Technical Brief for Use of ATSPM and CMFs. They will also inform the contacts of Project 17-109’s implementation objectives and seek advice on the appropriate process. Finally, the team will offer to make a presentation to the oversight persons and stakeholders at the next annual TRB meeting. The implementation team will make these presentations during step 3.

During step 4, the team will submit the research products to the appropriate oversight persons. Specifically, they will submit the draft ATSPM Evaluation Methodology to the HSM oversight persons. The team will highlight the specific sections and paragraphs in this document that should be incorporated into

a future edition of the HSM. The team will also formally submit the CMFs developed for Project 17-109 to the CMFC website.

Task D. Refine Roadmap Activities (if funded)

This task will be undertaken if implementation funding is secured. The main objective of this task is to meet with the contract manager of the funding agency to review the work scope for the remaining tasks. Reporting requirements will be identified and scheduled.

A second objective of this task is to assess the feedback obtained during Task C and determine if the implementation roadmap needs to be refined. For example, the feedback may indicate a need to alter the roadmap steps to be undertaken in Task E, or a need to revise the Project 17-109 products to enhance their implementation potential.

Task E. Undertake Roadmap Steps 5 to 9 (if funded)

The objective of this task is to complete steps 5 to 9 of the implementation roadmap (as shown in Table 1). This task will be undertaken if implementation funding is secured.

During step 5, the implementation team will organize and host an interactive webinar for the oversight persons and stakeholders. One webinar will be hosted for the HSM representatives, and one webinar will be hosted for the CMFC representatives. The objective of the webinar will be to (a) explain the details of the Project 17-109 technology intended for implementation in the HSM and CMFC, and (b) gather feedback from the participants regarding perceived implementation issues and challenges.

During step 6, the implementation team will use the step-5 feedback to develop a plan to resolve the confirmed implementation issues and challenges. This plan will be documented in a technical memorandum that is submitted to the implementation contract manager and NCHRP.

During step 7, the team will execute the approved plan to resolve the implementation issues and challenges. One possible activity in this regard is the preparation of proposed draft HSM content (i.e., text, tables, and figures in HSM format) that is focused on describing the correct use of the Project 17-109 CMFs in one or more existing HSM chapters. Once the revisions have been completed, the team will resubmit the implementation materials to the appropriate oversite persons.

During step 8, the implementation team will organize and host an interactive webinar for the oversight persons and stakeholders. One webinar will be hosted for the HSM representatives, and one webinar will be hosted for the CMFC representatives. The objective of the webinar will be to present the revised implementation materials—focusing on the changes made to the materials to address the issues and challenges identified in step 6.

During step 9, the implementation team will monitor and support the implementation process managed by the key oversight persons. In this regard, the team will periodically connect with the HSM and CMFC oversight persons to inquire about implementation progress, answer questions, provide supplemental project-related materials, and review draft descriptions of the implemented technology.

Task F. Submit Report Documenting Process and Outcomes (if funded)

The objective of this task is to prepare and submit a report that documents (a) the activities undertaken during the implementation project, (b) the people, agencies, and groups involved in the process, (c) the issues that were identified and the resolutions undertaken, and (d) the outcomes obtained. The report will also describe potential research needs that were identified during the project.

Task Schedule

The implementation activities described in the previous sections are planned for completion according to the schedule shown in Table 2.

Table 2. Task schedule.