5
IMPLEMENTATION PROJECT PROPOSAL MnDOT Research Services wants your ideas for the Research Implementation Program. Successful proposals for implementation projects typically involve the application of previous research results through a pilot project, proof-of-concept validation, new method testing or innovative equipment evaluation (not simply an equipment purchase). Implementation projects may also be aimed at development of a practitioner guide, manual of best practices or training materials. Before completing this form, please review the MnDOT Implementation Project Guidelines and Process. After you have completed a draft of this form Research Services will assist you in finalizing it for review by the Transportation Research and Innovation Group. Please click on each information icon for further instructions. All fields outlined in red are required fields. Form will not be accepted with uncompleted required fields. 1. PROJECT AND PROPOSER INFORMATION Proposal Date: Project Title: Requested Budget: Project Duration (months): Proposed by: Name Office or District Email Phone Management Champion (Office Director or District Engineer): Name Office or District Email Phone Signature of Office Director or District Engineer Signature Date 2. RESEARCH CONNECTION 1 _____________________________________ What research project is being implemented? Please give identifying information below. Title: Project Number: Other identifying information of research being implemented:

Implementation Project Proposal - dot.state.mn.us you have completed a draft of this form Research Services will assist you in finalizing it for review by the Transportation Research

  • Upload
    lydiep

  • View
    215

  • Download
    2

Embed Size (px)

Citation preview

IMPLEMENTATION PROJECT PROPOSAL

MnDOT Research Services wants your ideas for the Research Implementation Program. Successful proposals for implementation projects typically involve the application of previous research results through a pilot project, proof-of-concept validation, new method testing or innovative equipment evaluation (not simply an equipment purchase). Implementation projects may also be aimed at development of a practitioner guide, manual of best practices or training materials.

Before completing this form, please review the MnDOT Implementation Project Guidelines and Process. After you have completed a draft of this form Research Services will assist you in finalizing it for review by the Transportation Research and Innovation Group. Please click on each information icon for further instructions. All fields outlined in red are required fields. Form will not be accepted with uncompleted required fields.

1. PROJECT AND PROPOSER INFORMATIONProposal Date:

Project Title:

Requested Budget: Project Duration (months):

Proposed by:

Name

Office or District

Email

Phone

Management Champion (Office Director or District Engineer):

Name

Office or District

Email

Phone

Signature of Office Director or District Engineer

Signature Date

2. RESEARCH CONNECTION

1

_____________________________________

What research project is being implemented? Please give identifying information below.

Title: Project Number:

Other identifying information of research being implemented:

3. SUMMARIZE YOUR IMPLEMENTATION IDEA AND PROJECT GOALS

4. PROPOSED CONSULTANT AND PROCUREMENT PROCESSProposed Consultant or Proposed University

5. SUMMARIZE THE KEY TASKS AND DELIVERABLES OF YOUR PROJECT

Task #1:

Deliverable #1:

MnDOT Implementation Project Proposal

2

How many tasks are in your project? Select total:

1 2 3 4 5 6

3

Task #2:

Deliverable #2:

Task #3:

Deliverable #3:

Task #4:

Deliverable #4:

Task #5:

Deliverable #5:

Task #6:

Deliverable #6:

MnDOT Implementation Project Proposal

1.

2.

3.

4.

5.

6.

6. ESTIMATE COST OF PROJECT BY FISCAL YEAR

FY____ (7/1/____ – 6/30/____)

FY____ (7/1/____ – 6/30/____)

FY____ (7/1/____ – 6/30/____)

7. EQUIPMENT TO BE PURCHASED FOR THE PRODUCT

8. PROPOSED TECHNICAL ADVISORY PANEL MEMBERS FOR YOUR PROJECTNAME TITLE ORGANIZATION

4

MnDOT Implementation Project Proposal

9. WHICH OF THE FOLLOWING DEPLOYABLE PRODUCTS DO YOU ANTICIPATEWILL RESULT FROM THIS IMPLEMENTATION PROJECT? (Must select at least one. Select all that apply.)

New or improved technical standard, plan or specification

New or improved manual, handbook, guidelines or training

New or improved policy, rule or regulation

New or improved business practice, procedure or process

New or improved tool or equipment

New or improved decision support tool, simulation, model or algorithm (software)

Evaluation of new commercial products to determine if they meet MnDOT needs

Processed data/database

Other

5

10. WHAT ARE THE EXPECTED BENEFITS FROM THIS IMPLEMENTATION PROJECT?

11. WHO WILL APPLY OR USE THE IMPLEMENTATION PRODUCTS?

12. COMMUNICATION PLAN

Please save this form with a filename corresponding to your unique project title. Email the completed form to Bruce Holdhusen at [email protected]. Research Services will evaluate your proposal and contact you for additional information. MnDOT's Transportation Research and Innovation Group (TRIG) will review completed proposals at their spring meeting where you will be asked to present a short summary of your project.

MnDOT Implementation Project Proposal

MnDOT Implementation Project Guidelines and Process

WHAT IS IMPLEMENTATION? Good research implementation projects save time, money or resources by helping put new ideas and technology into practice. They might solve a long-time problem or improve how MnDOT does business. We are looking for pilot projects of new technology or research that can set the stage for future full deployment. We’re not looking to fund standard equipment purchases, a mass deployment or basic research with these funds.

The types of projects funded often include the development of manuals or best-practices guides, training curricula, technology pilot, new method testing, proof-of-concept validation and innovative equipment evaluation.

Examples of recent projects - Culvert repair best practices guide - Demonstration of AVL technology in grass mowers - Inventory of roadside infrastructure using mobile mapping technology - Development of a statewide bride inspection contract using drone technology - Pilot of an ultrasonic measuring system for bridge corrosion

PROJECT GUIDELINES

1. Address Problem or Need - The proposal needs to clearly state the problem being solved and the opportunity or need that is being satisfied.

2. Research Connection

The implementation project must demonstrate, test or advance a new practice. Preferably, it builds on completed national, state or local research, including from the following programs:

a. Federal Research i. National Cooperative Highway Research Program (NCHRP) or other Federal

Cooperative Research Program project ii. Pooled Fund Research Project (MnDOT-lead, MnDOT participation in pooled

fund project/program, or single state project) b. State Research

i. MnDOT Research Project ii. Other State DOT Research Project

iii. Intelligent Transportation System (ITS) Inst. or MN Guidestar Program iv. MnDOT’s Maintenance New Technology Research and Equipment Committee

(NTREC) program v. MnDOT’s Pavement Research Facility - (MnROAD)

c. Local Research i. Local Road Research Board (LRRB) research projects

3. Demonstrate Application – The proposal needs to indicate how the results of the

implementation project will be used or applied within the department. State how the results could lead to full implementation in day-to-day practice and whether there is commitment to support implementation statewide, and how the benefits can be quantified.

MnDOT Implementation Project Guidelines and Process

4. Internal Champions – Implementation proposals must identify a MnDOT staff person as the project manager to move forward for funding consideration, and it is helpful to also identify a management champion at the DE, ADE or Office Director-level.

5. Other Considerations:

Evaluation and Report – Each project should produce a final product or a publishable report on the project outcomes.

Equipment purchases

a. Should be kept to a minimum and only include items necessary to support the implementation project.

b. Can be used as seed money to demonstrate the viability of the equipment. Pilot projects should be limited to a specific area or location.

c. Not intended as a funding source for full deployment of equipment through the state. d. Can’t be used to supplement equipment budgets.

Construction Project Supplemental Agreement

a. Implementation in a construction project should be discussed at the conceptual stage to determine feasibility of the financing, and how the project report will be completed.

PROCESS

1. Submit an Idea a. Provide a short description of the implementation idea on the MnDOT/LRRB IdeaScale

web site: http://mndot-lrrb.ideascale.com/ b. The implementation idea must be submitted by a MnDOT employee

2. If Your Idea is Selected, Submit an Implementation Project Proposal

a. MnDOT Research Services will send a proposal form to selected idea submitters requesting detailed information about the proposed implementation project

b. Complete the form as thoroughly as possible (more than one person can contribute) and submit the draft to Research Services.

c. Research Services will assist with completion of the final form for submission to the Transportation Research and Innovation Group (TRIG).

3. Review, Funding Decision and Completion of Work Plan

a. Proposals for implementation funding are reviewed by TRIG, the governing board for MnDOT and LRRB’s research programs.

b. Each proposer gives a short presentation of their Implementation Project Proposal to the TRIG board.

c. If funding is approved, the proposer and Research Services will determine an appropriate contracting mechanism and work with the investigator to complete a detailed Implementation Project Work Plan (either university or consultant). Research Services is available to assist with completion of the Work Plan.

d. Once the Work Plan is approved, the project moves forward to the procurement stage (contract, work order, etc.)

(Revised November 2017)