5.0 - GENERAL

A major goal of research is to provide results that can be implemented. Planning starts with the drafting of problem statements, which will have at least a conceptual implementation plan. Proposals are required to have preliminary implementation plans that address the requirements, limitations, benefits, and costs. Final reports include drafts of policy statements, specifications, standard drawings, test procedures, etc. needed for implementation.

Actual implementation does not need to be delayed until the research is totally complete nor the final report prepared. At any stage where a project is close to producing results, the Technical Liaison/Project Panel should evaluate any findings for possible early implementation. If deemed feasible, the Technical Liaison/Project Panel should work with the researcher and/or technical experts to prepare an implementation plan to ensure effective and timely application of the research results throughout ODOT.

Results of research projects will be monitored and evaluated by the Technical Liaison/Project Panel and Office Administrator. A record of implementation activities will also be made as activities occur. Progress reports will be provided to R&D, who in turn will inform interested parties.

A flow chart showing the research implementation process is included in Figure 5.1.

 

5.1 - PROPOSAL STAGE

Each researcher's proposal will include a preliminary implementation plan that describes the activities anticipated to promote application of the results of the research. While actual implementation of the results is the responsibility of ODOT, each research project must include recommendations for how to facilitate implementation. It is expected that the implementation plan will evolve during the project; however, proposals must address at least the following:

  1. identification of factors that will influence the decision to implement results (see Figure 5.2 for benefits to be considered),

  2. a list of the "products" expected from the research, e.g., a proposed specification, a design manual or guide, field or laboratory procedures, a training manual, hardware for demonstration, software and instructions for computer application, etc.,

  3. the audience or "market" for this product, and

  4. a realistic assessment of impediments to successful implementation.

The researcher should solicit ideas from the Technical Liaison(s) as the final proposal is being drafted. Failure to address these items may render the proposal non-responsive.

 

5.2 - IMPLEMENTATION PLAN

As a research project progresses, the Technical Liaison/Project Panel must periodically evaluate the research, the validity of the methods used, and the results achieved. The Technical Liaison/Project Panel should, before that time, adapt Figure 5.2 to the specific project under review. Adaptation of the assessment form to a specific research project should detail exactly what improvement is expected. For example, instead of "Increased public safety", the assessment form might say "Accidents at intersections should be decreased by 50%." The assessment should take into consideration the end users and stakeholders. Some factors may not be applicable due to the nature of the research.

If the project recommendations, products, etc. are to be implemented, the Technical Liaison/Project Panel will determine if it would be best implemented by ODOT, or by the researcher. When it is determined that value may be achieved by implementing any of the results, be they interim or final, a detailed implementation plan should be developed. The format for a standard implementation plan is presented in Figure 5.3. If the implementation will be handled internally, the plan will be developed by the responsible Program Office(s). If the implementation will be part of the research contract, the researcher will develop the implementation plan. The plan will include the following:

 

  • Project title

  • The names of the research agency and PI

  • The name of the Technical Liaison (and Project Panel members' names, if applicable)

  • Anticipated applications or potential uses

  • User group(s) and principal contact(s)

  • A sponsor(s), e.g., Deputy Director or Assistant Director

  • A narrative description of each step of the process and estimated time frame (i.e., changes in policy, procedures, practice, trial installations, pilot projects, etc.), and the responsible individual(s)

  • Costs of labor, facilities, training, or other resources that need to be expended

  • Funding source(s)

  • Benefit(s)

  • Risk(s)

  • Anticipated barriers and strategies to overcome them

  • Technology transfer methods to be used.

  • Time frames and milestones to measure progress

  • Evaluation time frames and reporting requirements.

  • Other Offices who should be consulted on the changes

  • The implementation plan is to be reviewed and approved by the responsible program Office Administrator(s) and Deputy Director(s). It is the responsibility of the lead or sponsoring Office/Division to coordinate with all other affected offices and divisions for reviews and approvals. If an Expert Task Group or TAC is operative, the implementation plan should be forwarded by the Office Administrator to the Group for its review and recommendation.

     

    5.3 - MONITORING

    Implementation activities are to be tracked by the responsible program Office Administrator(s) and the Technical Liaison/Project Panel. The Technical Liaison/Project Panel will submit a progress report to the Office Administrator and R&D quarterly. The report will list the approved implementation actions (step-by-step), the responsible parties, the status of each step, and date each action was completed. The format of an implementation progress report is presented in Figure 5.4.

     

    5.4 - ANNUAL SUMMARY

    At the end of each fiscal year, R&D and the program Office Administrators will prepare a summary of implementation progress. This summary will include the last quarterly progress report for each project, and a commentary on:

     

  • Accomplishments and the details of associated benefits (e.g., cost/time savings, improved performance, longer life, etc.)

  • Problems (lack of progress, unexpected costs or results, etc.)

  •  

    The annual summary will be distributed to the Assistant Directors, Deputy Directors, FHWA, Office Administrators, and researchers.

    Annual summary reporting will continue for a minimum of three years after all changes have been accomplished to measure performance and determine if the implementation has achieved the anticipated goals.