AUGUST 2011

THIS PAGE INTENTIONALLY BLANK

i

Table of Contents 1.0 INTRODUCTION …………………………………………………………... 1

1.1 Purpose of Research Manual …………………………………………. 1 1.2 Research Division Mission and Responsibilities ……………………... 1 1.3 Role of SHA’s Research Advisory Board (RAB) ……………………. 2 1.4 Research Advisory Board Membership ……………………………… 2 1.5 RAB Meeting Frequency and Location ……………………………… 2

2.0 RESEARCH WORK PROGRAM DEVELOPMENT …………………… 3

2.1 Overview ……………………………………………………………... 3 2.2 Determining Research Needs ………………………………………… 3 2.3 External Requests …………………………………………………….. 4 2.4 Limitations on the Use of Research Funds …………………………... 4 2.5 Problem Statement Review …………………………………………... 4 2.6 Prioritization and Selection of Projects ………………………………. 5 2.7 Research Work Program Development and Approval ……………….. 5

3.0 RESEARCH PROJECT MANAGEMENT ………………………………. 6

3.1 Formation of Technical Team ………………………………………... 6 3.2 Research Project Work Plan ………………………………………….. 6 3.3 Legal Agreements for Projects ……………………………………….. 7 3.4 Notice to Proceed …………………………………………………….. 7 3.5 Project Meetings ……………………………………………………… 7

3.5.1 Kick-Off Meetings ………………………………………… 7 3.5.2 Progress Meetings ………………………………………… 8

3.6 Progress Reports/Invoicing …………………………………………... 8 3.6.1 Progress Reports …………………………………………... 8 3.6.2 Invoices …………………………………………………… 8 3.6.3 Progress Report/Invoice Reviews ………………………… 8

3.7 Interim and Final Reports ……………………………………………. 9 3.7.1 Interim and Final Report Reviews ……………………….... 10

3.8 Distribution of Final Reports ………………………………………..... 10 3.9 TRB/Transportation Conference Presentations ………………............. 10

4.0 PROGRAM REPORTING /EVALUATION ……………………………...11

4.1 Financial Reports ……………………………………………………... 11 4.1.1 Financial Report Reviews …………………………………. 11

4.2 Annual Reports ……………………………………………………….. 11 4.3 TRIS Database – Reporting Research in Progress and Completed Research ……………………………………………… 11 4.4 Customer Satisfaction Survey.……………….……………………… 11

5.0 PROJECT CLOSEOUT ………………………………..…………………...12

5.1 SHA FMIS Closeout ………………………………………………….. 12 5.2 Audits/Consultant Services Notification ……………………………… 12

ii

5.3 FHWA Closeout ……………………………………………………… 12 6.0 OTHER ………………………………………………………………………. 12

6.1 Pooled-Fund Studies ………………………………………………….. 12 6.2 Experimental Features ………………………………………………... 13 6.3 New Products …………………………………………………………. 13 6.4 Local Technical Assistance Program (LTAP) ………………………... 13 6.5 Peer Exchanges ……………………………………………………….. 14 6.6 NCHRP ……………………………………………………………….. 14

6.6.1 NCHRP Projects …………………………………………... 14 6.6.2 NCHRP Synthesis Projects ………………………………... 15

6.7 Literature Searches …………………………………………………… 15 APPENDICES APPENDIX A Flowchart of Process APPENDIX B Problem Statement Outline APPENDIX C Guidelines for Technical Liaisons APPENDIX D Quarterly Progress Report Template APPENDIX E Technical Report Documentation Page APPENDIX F Experimental Features Guidelines APPENDIX G 23 CFR 420, Planning and Research Program Administration APPENDIX H Glossary

1

Maryland State Highway Administration Research Administration Manual

1.0 INTRODUCTION 1.1 Purpose of Research Manual The primary purpose of this manual is to provide a comprehensive description of how the Maryland State Highway Administration (SHA) manages its research program. This information should help those who are interested better understand the process of soliciting research needs and selecting which projects will be funded. The Research Manual provides a relatively condensed reference outlining general responsibilities, requirements and policies associated with the development and management of SHA’s research work program. The hope is that this manual will lead to improved understanding and increased involvement in SHA’s research program. This manual is also intended to satisfy the federal requirement contained in 23 CFR 420.209(b) (see Appendix F) which requires that each state document its management process and procedures for selecting and implementing Research Development & Technology (RD&T) activities. 1.2 Research Division Mission and Responsibilities

The mission of the Research Division is to develop and maintain a research program that supports SHA’s Business Plan, to share research information and to support appropriate technology transfer activities.

Primary responsibilities of the Research Division in fulfilling this mission include:

• Developing and managing SHA’s research work program. • Coordinating activities for the National Cooperative Highway Research Program

(NCHRP). The NCHRP is an applied, contract research program with the objective of developing near-term, practical solutions to problems facing transportation agencies. Funding support for NCHRP comes from the states (5.5% of total SPR funds) and provides funding for $35 million annually for a national highway research program which is administered by the Transportation Research Board (TRB). The Research Division’s role includes soliciting problem statements for research issues of national significance and coordinating Maryland’s ballot to assess national transportation research priorities.

• Supporting the Technology Transfer (T2) Center at the University of Maryland and serving on its Advisory Board, which provides numerous training opportunities for SHA employees, local jurisdictions and the transportation community at large.

• Keeping SHA abreast of the latest developments in surface transportation research by distributing information from TRB, other state DOT’s and transportation research organizations to the appropriate areas in SHA.

2

• Representing Maryland DOT as the State’s representative to the Transportation Research Board (TRB) and serving as Maryland’s representative on the national AASHTO Research Advisory Committee (RAC) and as SHRP II (Strategic Highway Research Program) coordinator.

• Partnering with the University Transportation Centers located at the University of Maryland and the Morgan State University on internship and research activities.

• Coordinating SHA’s response to NCHRP and state DOT surveys and distribute surveys developed by SHA through the AASHTO RAC email group.

1.3 Role of SHA’s Research Advisory Board (RAB) The Research Advisory Board (RAB) guides SHA’s research program. Its responsibilities include providing input to the overall research direction of the Administration, prioritizing research needs, and supporting the implementation of research efforts. 1.4 Research Advisory Board Membership The RAB membership is broad and includes Maryland Department of Transportation (MDOT) and modal staff as well as local government, Federal Highway Administration (FHWA), university and industry representatives. The standing board members are:

• SHA Administrator (Chair) • SHA Deputy Administrator for Finance, Information Technology and Administration

(Vice-Chair) • SHA Deputy Administrator/Chief Engineer for Planning and Engineering • SHA Deputy Administrator/Chief Engineer for Operations • SHA Director Office of Policy and Research • SHA Research Division Chief • FHWA Representative • MDOT Headquarters Representative • MDOT Modal Representative • County Government Representative • University Representative (University of Maryland) • University Representative (Morgan State University) • Industry Representative • Consultant Representative

1.5 RAB Meeting Frequency and Location The RAB meets semi-annually, generally in late January and August. Meetings are typically held at SHA’s Headquarters Building. Agendas for the RAB meetings are prepared by the Research Division with input from others.

3

2.0 RESEARCH WORK PROGRAM DEVELOPMENT 2.1 Overview The annual research solicitation cycle for SHA’s research program is as follows: The Research Division solicits research problem statements from SHA Senior Managers in January/February. In the spring, all complete and relevant research problem statements are compiled by the Research Division and sent to SHA's Research Advisory Board for prioritization. In late spring, the identified research priorities are reviewed with SHA’s Administrator and Deputy Administrators to formulate the draft annual research work program. During the summer, the Research Division develops the formal research work program and obtains approval for the work program from the Federal Highway Administration. In the fall, the Research Division requests formal work plans/research proposals for the approved research projects. In late fall/winter, project agreements are prepared, funding is authorized, and Notice to Proceed is issued. In January/February the cycle for the upcoming federal fiscal year begins again. The solicitation process is depicted graphically in Appendix A. 2.2 Determining Research Needs Determining SHA’s research needs is accomplished through the annual solicitation of research problem statements early each calendar year. The Research Division prepares a solicitation memo that is sent to SHA Senior Managers and chair persons of SHA Key Performance Area councils typically in late January or early February. (Note: Please see “External Requests” below.) Each senior manager’s office is required to submit the research needs in the format of a Research Problem Statement. Please see Appendix B for the outline of SHA’s Research Problem Statements. Problem statements must address the following items:

• Project Title. • Problem Statement (brief description of the problem proposed for research and what has

been done by others). • Research Objectives (brief description of the objectives of the research and major tasks to

be undertaken). • Implementation Summary (brief description of how the products or findings of the

research will be used). • Expected Benefits (estimate of how the findings or product of the research will benefit

SHA, including cost savings, time savings, and/or process improvement). • Amount of Funding Requested (total amount of funding being requested for the proposed

research project, including SHA administrative overhead if the project will be done by SHA forces).

• Anticipated Duration of Project (time, in months or years, to complete the proposed research project). Note: To minimize chances of project slippage, multi-year projects are generally discouraged. Larger projects may be broken into distinct project phases.

4

• Identification of Technical Liaison (this is the individual employed by SHA who will be the principal liaison and serve as SHA’s technical expert for the proposed project). Note: If the proposed research is to be completed by SHA staff, the Technical Liaison may also be the Principal Investigator.

2.3 External Requests Research needs for SHA’s research program are solicited internally through SHA Senior Managers and also through the Maryland University Transportation Centers (UTCs). UTC researchers desiring to submit problem statements should work with the Director and/or staff of the pertinent office(s) at SHA with primary functional responsibility in the area relating to the proposed research. This will help ensure that such research proposals are known and considered in the context of the overall research needs of each SHA office. To increase the chances for funding in the research work program UTC problem statements should be submitted through the appropriate office/senior manager at SHA to ensure the proposed research is needed. The senior manager and/or office staff can then champion the need for the research. 2.4 Limitations on the Use of Research Funds Funding for the SHA’s research program is used to address the research needs to accomplish the mission, goals and objectives of SHA. It is intended that funding be utilized for transportation research and development projects and for non-routine technology transfer activities. Unless a research project is to be conducted by in-house staff or needs substantial in-house support, SHA staff salaries should not be a part of the research project. Research funds are not intended to supplant normal SHA staff salaries, to fund travel beyond that required to complete the project, to purchase office equipment, or to be a substitute for projects that would be done otherwise. The intent of the SHA’s research program is not to fund the acquisition of computers and other equipment unless such equipment is an integral component and is absolutely necessary for completion of the research project. In these instances, the need to purchase equipment must be stated in the research project work plan and clearly shown as a separate line item in the itemized budget. Title to all equipment purchased under a research project rests with the SHA. It must be tagged as SHA property and be turned over to the SHA upon the completion of the research project. Note: All project activities must comply with applicable state and federal laws/regulations. 2.5 Problem Statement Review The Research Division will review all research problem statements received for completeness and appropriateness for SHA’s research program. If clarification is needed, the Research Division will contact the problem statement submitter.

5

The Research Division may also provide supplemental information to the RAB related to the problem statement, including summaries of related on-going or recently completed research, funding history if a project is funded over several years or in phases, and other information it deems helpful in prioritizing and selecting projects for funding. 2.6 Prioritization and Selection of Projects After initial review of the problem statements by the Research Division, the statements are compiled into a package for review and prioritization by the RAB. The RAB is asked to review and prioritize the research problem statements based on their relevance and merit defined below.

• Relevance – Does the proposal clearly address a need identified in the goals and objectives of SHA’s Business Plan? Will a solution be timely? Is it likely that the research can be implemented by SHA?

• Merit – Can the problem be solved by research? Does the proposed research have a high probability of successful completion and application in the field of transportation? Does the proposal present a sound understanding of the problem and an appropriate solution to it? Are satisfactory answers or similar studies underway elsewhere? Is there support for implementation of the research findings? Will implementation be cost effective?

Points are assigned based upon each RAB member’s assessment of the problem statement’s relevance and merit. Rankings for all responding RAB members are then summed by the Research Division to determine overall research work program priorities. Note: Pooled fund studies are prioritized in a similar manner separately from non-pooled fund studies. For a description of pooled fund studies see section 6.1. The cumulative research problem statement rankings, in priority order, are used to prepare recommendations for the draft research work program. In developing the draft work program, the Research Division compares the ranked research needs against the available funding for new projects for the upcoming fiscal year. This information is reviewed with SHA’s Deputy Administrators and Administrator for their endorsement in preparing the final research work program. 2.7 Research Work Program Development and Approval After endorsement of the proposed research work program by SHA’s Administrator, the Research Division sends notification to all research problem statements submitters and the RAB members of the projects to be included in the research work program for the upcoming fiscal year. The Research Division then assembles the final research work program and requests approval of the work program from the FHWA DelMar Division Office by September 1 each year. The Research Work Plan that is sent to the FHWA must include the following information:

• A description of RD&T activities to be accomplished in the program period.

6

• The estimated cost for each eligible activity, with a breakdown of funding by Federal, State and other sources (if applicable).

• A description of any cooperative RD&T activities in which the State DOT is participating, e.g. pooled fund studies.

• The following statement certifying compliance with 23 USC 505 “State Planning and Research,” is included in the cover letter to FHWA I, _______________________, Administrator, State Highway Administration, of the State of Maryland, do hereby certify that the State is in compliance with all requirements of 23 U.S.C. 505 and its implementing regulations with respect to the research, development, and technology transfer program, and contemplate no changes in statutes, regulations, or administrative procedures which would affect such compliance.

3.0 RESEARCH PROJECT MANAGEMENT 3.1 Formation of Technical Team With few exceptions, e.g. NCHRP and TRB support, working technical teams are formed to direct and monitor the progress of research projects. At a minimum, these technical teams will include an Administrative Lead from the Research Division and a Technical Liaison representing the functional area in which the research is being conducted. Additional members may include representatives from the FHWA, representatives of SHA Key Performance Area councils and additional subject experts. All research projects have an assigned Administrative Lead in the Research Division. This individual is the central point of contact for issues regarding a specific research project and is responsible for overall management of the project. The Administrative Lead sets up project meetings, requests proposals, makes sure reports are submitted, facilitates communications between the Principal Investigator and the Technical Liaison for the project, captures and tracks progress on action items from meetings, and processes invoices. They are involved in all aspects of the project, but are not usually SHA’s technical expert. All research projects have a Technical Liaison from the office whose functional responsibility coincides with the topic of research. The importance of timely and substantive input from the technical liaison is critical to the success of a research project. See Appendix C, Guidelines for Technical Liaisons. 3.2 Research Project Work Plan An initial task of the technical team is to develop/review and refine a scope of work (work plan) for the proposed research project. The work plan expands upon the research proposal (problem statement) and defines:

• What and how the research will be done? • What resources (people, equipment and facilities) will be required?

7

• What it will cost? • When it will be completed?

The format of the work plan should follow the outline below:

• Introduction • Research Objectives • Research Benefits • Study Approach (including methodology and evaluation criteria) • Key Staff • Project Time Line • Itemized Budget

3.3 Legal Agreements for Projects Legal agreements or purchase orders are required for all research projects conducted by non-SHA staff. The Research Division prepares and processes research agreements for projects with state universities. To streamline the procurement process, the Research Division may request the development of multi-year master agreements outlining the general terms and conditions of projects to be done with a particular entity. Once the master agreement has been executed, individual projects, or tasks, can then be authorized with a written Notice to Proceed after review and acceptance of a project proposal. Research projects completed by a consulting firm are usually covered under an existing open-end agreement at SHA. If a new agreement is needed or if the project requires a sole source procurement, it is handed by SHA’s Office of Procurement & Contracts. 3.4 Notice to Proceed A written Notice to Proceed from the Chief of the Research Division (or other appropriate SHA official as determined by the Chief of Research) is required prior to beginning work on a project. The Notice to Proceed shall include the: project title, contract number, total amount payable (upset limit) and the completion date. Note: Expenses for any work done prior to the date of the Notice to Proceed cannot be reimbursed. 3.5 Project Meetings Project meetings are held throughout the life of a project. These meetings may be requested by any party involved in the research project and should be held at least twice a year. The Administrative Lead has responsibility for scheduling these meetings. 3.5.1 Kick–Off Meetings A kick-off meeting should be held for each new project. The meeting should include the Principal Investigator (P.I.), the Technical Liaison, the Administrative Lead from the Research Division, and any other key people involved with the study. Expectations for progress reports, future meetings, and project completion should be discussed at the meeting. The Administrative Lead should request that the P.I. include a technical report documentation page and a one-to-two page summary with the final report (The Administrative Lead can provide samples).

8

3.5.2 Progress Meetings Progress review meetings are held throughout the duration of a research project. A schedule for progress meetings may be developed at the “Kick-Off Meeting,” or progress meetings can be held on more of an ad hoc basis as project conditions warrant. Progress review meetings should include all members of the project technical team. 3.6 Progress Reports/Invoicing

3.6.1 Progress Reports Progress reports are usually required to be submitted to the Research Division on a quarterly basis (March 31, June 30, September 30 and December 31) unless specified differently in the research project agreement. The Administrative Lead sends quarterly requests with the progress report template to the P.I. At a minimum, the quarterly report is expected to include the following:

• A written summary of progress made on the research project for that quarter. This may be shown by including a brief description of work during that period under each major task in the research work plan together with the estimated percent complete for that task.

• A written summary of any problems encountered and how they were addressed. • A written summary outlining anticipated work for the next quarter. • A summary of costs for the quarter and cumulative expenditures.

Please see Appendix D for SHA’s Quarterly Progress Report template. 3.6.2 Invoices The timely submission of invoices and progress reports is important. Invoices should clearly indicate who is getting paid and what they are getting paid for. Invoices must reference the project title and contract number. Invoices must clearly show the cost being invoiced, the cumulative total invoiced and the funding amount remaining. If an invoice covers more than one research project, supporting invoice back-up must clearly breakdown the costs for each project. 3.6.3 Progress Report/Invoice Reviews A progress report must be received from the Principal Investigator before the invoice can be paid. If a progress report has not been received, a letter or an e-mail should be sent by the Administrative Lead in the Research Division to the Principal Investigator requesting the progress report. The Administrative Lead should check with the SHA technical liaison for the project to see if he/she is satisfied with the work completed and if sufficient progress has been made to justify the amount of the invoice. The Administrative Lead should also check the project balance from the latest FMIS expenditures spreadsheet to verify that the invoice is reasonable and accurate.

9

Note: As stipulated in research project agreements, payment of invoices is limited to a maximum of 90% until the final report has been completed and accepted by the SHA. Once the Administrative Lead completes the foregoing steps, the invoice can be processed for payment. If the invoice is from a state institution, the original should be sent to the Financial Accounting and Reporting Section to be processed through FMIS. The Research Division’s Index Number (01012), the agency object (either 8199 – technical services such as training, or 9037 – research and development costs), and project contract number must be included on the invoice. The invoice must also be approved by the Chief of Research before it is sent to the Financial Accounting and Reporting Section. If the invoice is from an entity that is not a state institution, the original should be approved by the Chief of Research and given to the Administrative Assistant for input into FMIS. An electronic copy of the invoice should be e-mailed to the SHA technical liaison for their records and a copy placed in the project file. Note: The Administrative Lead in the Research Division is responsible for adding the information to the Research Projects Database. The Administrative Lead should check in FMIS to see if the invoice has been paid (will take several days before it appears in FMIS) or wait until the monthly expenditures report comes out and check to see if it is listed as a new charge. 3.7 Interim and Final Reports Research reports document the methodology and findings of the research, and are an essential requirement of every research project. Reports should be written for an audience broader than just the technical experts with an intimate understanding of the subject. Primary units of measure should be U.S. Units, but metric equivalents can also be included. A brief description of what each figure and graph conveys should be discussed in the text of the report. (This will also help to address ADA accessibility issues.) The Research Division does not currently have a set template for reports, but they should generally follow this outline:

• Preliminaries (Title Page, Technical Documentation Page /Abstract (See Appendix E), Table of Contents, List of Tables, List of Figures)

• Executive Summary • Introduction (Background, Statement of Hypothesis) • Literature Review (Review of Previous Research, Summary of State-of-the-Art) • Methodology (Experiment Design, Equipment, Procedures) • Findings (Summary of Data, Method of Analysis, Presentation of Results)

10

• Discussion (Validity of Hypothesis, Factors Affecting Results, Implications) • Conclusions (Conclusions, Suggestions for Further Work) • Implementation Plan • References • Appendices (as required)

All draft reports are expected to be edited/reviewed by the university before being submitted to SHA. Any report that is found to require significant edits will be returned to the university before the Technical Lead is asked to provide comments on the content. The final 10% of the project budget will also be withheld until the report is deemed to be acceptable for publishing. 3.7.1 Interim and Final Report Reviews The Administrative Lead in the Research Division will circulate copies of the interim reports and draft final reports to all members of the Technical Team for their review and comment. A copy of the final draft must also be sent to SHA’s Office of Communications for their review. The Administrative Lead will compile all comments and ensure that they are addressed by the Principal Investigator. The Administrative Lead shall also create the final report cover using the established Research Division template. 3.8 Distribution of Final Reports All final research reports should include the technical documentation page, a one to two-page report summary, and an electronic copy of the report should be made available to the Research Division. At the minimum, the Research Division will send copies of the final reports to:

1. The FHWA Maryland Division Office 2. The Maryland Technology Transfer Center 3. The SHA Technical Liaison 4. The Transportation Research Board Library (TRID) (TRIS-TRB@nas.edu). 5. National Transportation Library (NTL) (NTLDigitalSubmissions@dot.gov). 6. Federal Highway Administration Research Librarian (fhwalibrary@dot.gov). 7. Office of Corporate Research, Technology, and Innovation Management, HRTM-10,

Turner Fairbank Highway Research Center (john.moulden@dot.gov). 8. Volpe National Transportation Systems Center, TRISNET Repository DTS-930

(susan.dresley@dot.com). 9. Northwestern University Transportation Library (r-sarmiento@northwestern.edu).

The Administrative Lead should also notify the Chief of Research that the record should be deleted in TRB’s Research in Program (RiP) database. 3.9 TRB/Transportation Conference Presentations Principal Investigators are expected to notify the Research Division about all presentations to be made on projects funded by the SHA at the TRB Annual Meeting or other transportation related

11

conferences. Copies of the draft presentation should be sent to SHA at least one month prior to the conference for review. 4.0 PROGRAM REPORTING/EVALUATION 4.1 Financial Reports The Research Division develops a monthly report of expenditures for all active research projects. A summary of new charges and a spreadsheet for each open Research Work Program is distributed internally among Research Division staff. If the report indicates that an erroneous charge was placed against a research project number, it is the responsibility of the Administrative Lead to work with the appropriate office and/or Cost Accounting Division to have the charge reversed or transferred to the correct number. The Research Division also sends a monthly financial report to the Program Development Division which summarizes all new research expenditures and keeps a running total of expenditures for the current fiscal year. The Program Development Division uses the information to determine SHA’s total State Planning and Research expenditures. 4.1.1 Financial Report Reviews Financial expenditure reports should be reviewed by the Administrative Lead and the Research Division Chief to ensure there are no erroneous charges and the total expenditures are commensurate with the percentage of work complete on each project. 4.2 Annual Reports In accordance with federal regulations (23 CFR 420.117), the Research Division must prepare and submit to the FHWA periodic reports summarizing program accomplishments, expenditures, project status, etc. FHWA’s work program approval typically requires that the annual report be submitted within 90 days of the end of the federal fiscal year. 4.3 TRIS Database – Reporting Research in Progress and Completed Research As described in Section 6.7, there are several primary transportation research databases that are routinely used for literature searches. The Research Division updates its records in the Research in Progress database twice each year and submits a copy of research project final reports to TRB for input to the TRIS database. 4.4 Customer Satisfaction Survey The mission of the Research Division is to develop and maintain a research program that supports SHA’s Business plan, to share research information, and to support appropriate technology transfer activities. In order to gauge general customer satisfaction with and opinions about the Research Division services, a biennial survey is conducted by the Division.

12

5.0 PROJECT AGREEMENT CLOSEOUT 5.1 SHA FMIS Closeout To initiate closing of the project in FMIS, the Administrative Lead should send a memo to the Office of Finance Program Coordination section with the project numbers that should be closed. They will notify the Federal Aid Program Section that the projects are being closed in FMIS. Note: For projects with federal funding, it takes at least 120 days for the project to be closed after notification. This allows time for all final paperwork to be submitted by the federal side. 5.2 Office of Audits/Office of Procurement & Contracts Notification Once all of the projects under an agreement are completed, the Administrative Lead should send a letter to the university and or/consultant notifying them that the contract is being closed. The Office of Audits and the Office of Procurement & Contracts should receive a copy of the letter. The letter should state that the projects are completed and the contracts can be closed out. 5.3 FHWA Closeout The entire authorization (all projects in the work program) must be closed out at the same time. An authorization cannot be closed on a project by project basis. The Research Division will send a memo to the Federal Aid Program Section to close an authorization. The memo will request the year to be closed, an attachment with a summary of the work on each project, and a copy of the most recent financial report for that work program. Once the request is made, it will take six to eight weeks for the year to actually be closed out. The leftover money is then deobligated and re-obligated for future Research Programs. Note: Funds lapse after four years once they have been deobligated. 6.0 OTHER 6.1 Pooled Fund Studies

When significant or widespread interest is shown in solving transportation-related problems, research, planning, and technology transfer activities may be jointly funded by several federal, state, regional, and local transportation agencies, academic institutions, foundations, or private firms as a pooled fund study.

To qualify as a pooled fund study, more than one state transportation agency, federal agency, other agency, such as a municipality or metropolitan planning organization, college/university or a private company, must find the subject important enough to commit funds or other resources to conduct the research, planning, and technology transfer activity. If a subject has been studied previously, the new study should provide new information that will complement or advance previous investigations of the subject matter.

13

A federal, state, regional, or local transportation agency may initiate pooled fund studies. Private companies, foundations, and colleges/universities may partner with any or all of the sponsoring agencies to conduct pooled fund projects.

For the latest on pooled fund program procedures please refer to this web link, http://www.pooledfund.org/.

6.2 Experimental Features When a new or innovative highway technology or alternative standard technology is incorporated into a federally funded project, the Federal Highway Administration requires that the “experimental feature” be evaluated to determine if it performs satisfactorily. Federal guidelines require that the features be evaluated according to an approved work plan. State Planning and Research (SPR) funds can only be used for the evaluation of experimental features and not for materials or construction of the feature itself. The Experimental Features Program is managed by SHA’s Office of Materials Technology. See Appendix F for FHWA’s Experimental Features Guidelines. 6.3 New Products The New Products Evaluation Program (NPEP) is a mechanism that allows vendors to pursue eligibility to use their products on SHA projects. The NPEP is managed by SHA’s Office of Materials Technology and New Products Officers investigate, evaluate and make recommendations regarding the usefulness of new products. The New Products Officers are from various technical offices throughout the SHA and make up the New Products Committee. Committee meetings are held twice a year and subgroups meet more frequently to address specific evaluations. Note: Approval of a new product means that the product is eligible for use on SHA’s projects where appropriate. However, product acceptance is on a project-by-project basis and all products must meet SHA’s Quality Assurance Guidelines. 6.4 Local Technical Assistance Program (LTAP) The Local Technical Assistance Program (LTAP) provides transportation technology transfer services to county and local agencies with transportation responsibilities. The Centers will receive funding through the LTAP program and have the following responsibilities:

1. Maintain mailing lists 2. Publish a quarterly newsletter 3. Serve as a clearinghouse for transportation information 4. Provide information and training on new and existing technologies 5. Perform a self-evaluation of the program

14

The Maryland Transportation Technology Transfer Center (T2 Center) was established in 1984 at the University of Maryland, College Park, to serve these needs in Maryland. The Research Division is represented on the T2 Center’s Advisory Board 6.5 Peer Exchanges The Federal Highway Administration requires that each state host a peer exchange periodically to review its research program. The goal of the peer exchange is for participants from various state research programs, the Federal Highway Administration, the host state, and others as deemed appropriate, to share information and to identify the strengths and opportunities for improvement of the host state’s research program. At the end of the one-to-two day exchange, the Peer Exchange Team develops a report, which the host state refers to for program improvements. The cost of hosting a peer exchange is included in the Research Work Program for the fiscal year in which it will be held. In accordance with 23 CFR 420.209(a) (7), expenses for hosting peer exchanges are eligible for 100% federal funding. 6.6 NCHRP NCHRP is an acronym for the National Cooperative Highway Research Program, which is a national pooled fund (cooperative) transportation program that is managed by the Transportation Research Board (TRB). It is an applied research program in which states and sponsors can submit research problem statements on transportation issues of national importance for possible funding. All states contribute 5.5% of their State Planning and Research (SPR) funds which allows for a national transportation research program of around $35 million/year. There are two major NCHRP research programs in which the Research Division maintains a lead coordination role on behalf of the SHA. They are the overall NCHRP (projects) program and the NCHRP Synthesis Program. 6.6.1 NCHRP Projects Each year TRB solicits research needs from the States, the FHWA and the AASHTO committees/subcommittees. Detailed research problem statements are submitted for consideration and reviewed by NCHRP staff and FHWA subject experts. These statements are then rated by the AASHTO Standing Committee on Research (SCOR) and the AASHTO Research Advisory Committee (RAC). These ratings and review comments are then priority ranked by NCHRP staff and provided to SCOR prior to its annual March meeting to determine final NCHRP priorities. The recommendations from the SCOR are then approved by ballot by the Chief Executive Officers of the State DOTs each summer. Once approved NCHRP staff formulate project panels to develop the Request for Proposals (RFPs), to review contractor proposal submissions, to recommend selection of a contractor, and to serve as oversight review panel throughout the duration of the project study. The Research Division coordinates and submits nominees to serve as project panel members.

15

6.6.2 NCHRP Synthesis Projects Historically, a continuing project funded through the NCHRP process is NCHRP Project No. 20-05, “Synthesis of Information related to Highway Problems.” NCHRP syntheses topics are solicited annually where there is a nationally recognized need to gather information regarding the current state of practice in transportation development and operational issues and to document state-of-the-art/best practices. The Research Division solicits and coordinates the submittal of synthesis needs from the SHA. A committee reviews all submittals and selects synthesis projects for funding. Once a synthesis topic has been selected for funding NCHRP staff follow a similar process to other NCHRP projects (see above) in forming project panels and selecting contractors. Again, the Research Division coordinates and submits nominees to serve as synthesis project panel members. 6.7 Literature Searches A review of the relevant literature is an essential component of a research project. Conducting a literature search will allow the investigator of the research problem to gain an improved understanding and build upon what is already known about the topic being researched. For transportation research projects there are several major bibliographical databases that should be searched. These include the Transportation Research Information Service (TRIS), the Research in Progress (RiP) database, University Transportation Center (UTC) Reports database, and the TRB Publications Index.

• The TRIS database is available online at http://ntlsearch.bts.gov/tris/index.do. • The RiP database is available online at http://rip.trb.org. • The UTC Reports database is available online at http://utc.dot.gov/utc_results.html. • The TRB Publications Index is available online at http://pubsindex.trb.org/. • Online Access to the full text papers published in the Transportation Research Record

(Journal of TRB) since 1996 is available at http://trb.metapress.com/home/main.mpx. • TRISWorld is a resource that became available to TRB sponsors in 2009. TRISworld

combines the records from TRIS with English language records from the International Transport Document Database, providing access to over 700,000 records of published transportation research worldwide. TRISworld is available online at http://trisworld.trb.org/.

• Another potential useful general search for information is the Bureau of Transportation Statistics National Transportation Library, which is available at http://ntl.bts.gov/.

• Searches via other search engines, e.g. Google, Yahoo, Northern Light, etc. may also be useful.

Presently, these online search references are publicly available. However, the Research Division can conduct literature searches for SHA staff upon request.

16

THIS PAGE INTENTIONALLY BLANK

Flowchart of Research Work Program Development Appendix A

17

Receive & ReviewResearch Problem

Statements(Spring)

Send ProblemStatements to RAB for

Prioritization(late Spring)

Annual Solicitation ofResearch Needs(January-February)

Review PrioritizationRatings and DevelopDraft Work Program

(Summer)

Finalize and SubmitAnnual Research Work

Program for FHWAApproval

(late Summer-early Fall)

Formulation of Annual Research Work ProgramOffice of Policy and Research - Research Division

The Research Division Chief sends solicitation memo toSHA Senior Managers requesting submittal of problemstatements for the annual research work program that willstart for the federal fiscal year beginning October 1.

The Research Division receives and reviews problemstatements, reviews carryover ideas from prior year, e.g.pooled fund studies that SHA offices have expressed aninterest in.

The Research Division sends problem statements to theResearch Advisory Board (RAB) for prioritization.

The Research Division reviews prioritization ratings fromRAB with Administrator and Deputy Administrators,determines money available for programming projects,assigns contract numbers and formulates the draft annualwork program.

The Research Division finalizes the research work programand submits it for FHWA review and approval. The FHWADivision offices reviews and approves the work program.

Refine Scope of Work,Obligate Funding &

Issue NTP for FundedProjects

(Fall-Winter)

The Research Division works with the submitting office andPrincipal Investigator to refine the scope of work, preparesand submits Form 42-25C's to obligate funding, submitsForm 30s to Finance. Requests preparation of projectagreements and issues Notice to Proceed (NTP).

Appendix B Research Problem Statement Outline

18

Maryland State Highway Administration Research Problem Statement for FFY

Project Title: (A short descriptive title of the proposed project, not to exceed 10 words) Related SHA Business Plan Objective: (Indicate which objective in SHA’s Business Plan the proposed research initiative most directly supports: e.g. This problem statement supports the development of performance measures for Objective x.x. in SHA’s Business Plan.) Research Problem Statement: (In less than one page describe the problem the proposed research initiative would address and its significance.) Research Objectives: (Briefly indicate the objectives of the proposed research project and identify the major tasks necessary to achieve the research objectives.) Implementation: (Briefly indicate how the findings or product of the research will be implemented and the expected benefits.) Expected Benefits: (Briefly quantify how the findings or product of the research will benefit SHA, including cost savings, time savings, and/or process improvement.) This problem statement is most appropriate for: (Please select only one category below, see attached descriptions of research programs) Pooled Fund Study (participation in funding by more than one state) Maryland led University Contract Research New Product Evaluation Program National Cooperative Highway Research Program (NCHRP) National Cooperative Highway Research Program Synthesis National Cooperative Highway Research Program IDEA Other (please explain) Amount of funding being requested: (If funding will be supplemented by other sources, please indicate the source and amount.) Anticipated duration of research project: (Multi-year projects are discouraged. However, projects may be broken into distinct phases that have a usable end product.) Technical Liaison Info: (Please indicate who will actively participate in the project as a technical liaison.)

Research Problem Statement Outline Appendix B

19

Name: Office/Division: Phone number: E-mail: Senior Manager Concurrence: Name Date

Appendix B Research Problem Statement Outline

20

Types of Research Programs Pooled Fund Study – A FHWA sponsored or state led research study of significant or widespread interest with funding participation by more than one state or agency. All contributing partners have a role on the steering committee for the study. (Note: There is an option to have TRB or FHWA administer State led studies, but their services must be paid for as part of the study.) For a state like Maryland, pooled fund study contributions typically range from $5,000-$20,000 per year. Maryland led University Contract Research – SHA sponsored transportation research and technology transfer conducted by universities, e.g. University of Maryland College Park. (Note: Procurement regulations give preference to public institutions, though partnerships with private universities are not prohibited.) New Product Evaluation Program – There are various alternatives for the testing and evaluation of new products. SHA has a New Products Committee to fulfill this need in Maryland. There are also national entities like the Highway Innovative Technology Evaluation Center (HITEC) that serve this purpose. National Cooperative Highway Research Program (NCHRP) – Is a significant national highway research program sponsored by AASHTO member departments that produces solutions to problems common to state highway agencies. TRB staff administers the program in cooperation with FHWA with oversight from the AASHTO Standing Committee on Research (SCOR). Costs for NCHRP projects are typically in the range of $150,000-$250,000. National Cooperative Highway Research Program-Synthesis – Suggestions for NCHRP syntheses are solicited annually where there is a nationally recognized need to gather information regarding the current state of practice in transportation development and operational issues and to document state-of-the-art/best practices. Cost for NCHRP Synthesis projects are $25,000 plus administrative expenses. National Cooperative Highway Research Program IDEA – This is a NCHRP program that funds Innovations Deserving Exploratory Analysis (IDEA), which are initial investigations of innovative, but untested concepts with potential for breakthroughs in transportation practice. Proposals are of two types: those aimed at demonstrating and idea will work, and those aimed at developing a prototype. Costs for NCHRP IDEA project awards typically range from $75,000-$100,000 per proposal. (Note: current cap for a proposal is $150,000.) Other – This could be in-house research done by SHA staff or by entities other than described above. Note: All SHA staff cost estimates must include SHA’s administrative overhead.

Research Guidelines for Technical Liaison

Appendix C

21

Research Guidelines for Technical Liaisons The State Highway Administration’s (SHA) SPR Part II Research Program is administered by the Research Division in the Office of Policy and Research with oversight by SHA’s Research Advisory Board. The majority of SHA’s research is conducted by local universities. While the Research Division is responsible for overall administration and supervision of SHA’s research work program (including providing ultimate direction to research contractors), this role is more in helping to identify research needs and to facilitate the undertaking of the research in a fair and responsive manner. All research projects have an Administrative Lead in the Research Division and a Technical Liaison with expert knowledge in the area relevant to the research study/project. Summarized below are the major responsibilities of the Technical Liaison for research projects. • Review problem statement submittals to ensure that they accurately describe the

nature of the problem and proposed research need. • For projects selected for funding, assume lead responsibility in developing a scope

of work for the research project. The Research Division will assist in the development of a scope of work, but does not always have the expertise needed to describe the work tasks that need to be done or to identify the products of the research project. It is very important that the technical liaison make sure that the work tasks and products described in the scope of work meet the technical objectives of the study/project.

• Attend project coordination meetings to obtain feedback, provide input and to

monitor progress of the research study/project. Being involved will help ensure that the project meets your needs and provides the highest quality results.

• Serve as the central contact for technical questions on the research study/project.

Research Division staff have varied experiences and backgrounds, but they are not experts in all functional areas.

• To the extent applicable, coordinate internal SHA data collection that is needed to

support the research study/project. • Review all progress reports and invoices. The Research Division will provide

copies of all invoices and progress reports for review by the technical liaison. The technical liaison should review these documents to ensure that the requested payment is consistent with the project tasks and is commensurate with the amount of work completed. Based on the recommendation of the technical liaison the Research Division will process invoices for payment.

Appendix C

Research Guidelines for  Technical Liaison 

22

• Assist in the evaluation of those conducting the research by providing feedback on their performance and/or completing consultant performance evaluations (if applicable).

• Review research project reports to ensure that the technical aspects and findings of

the research study/project are clearly and accurately documented.

• Help disseminate research findings to co-workers and others interested in the research topic.

Research Division staff will be involved in all of the foregoing activities, but please remember a more favorable outcome from the research study/project is likely with a strong involvement from the technical liaison.

Appendix D

23

For Quarter Ending Date of This Report

Project Number:          

Project Title:                              

Project Start Date:           Project Completion Date:           % Work Done:          

Name Agency Phone Fax Email Principal Investigator                    Principal Investigator                    Researcher                    Researcher                    

1. Summary of Progress for Quarter

Attach a progress schedule consisting of graphical information depicting (1) a schedule of research activities tied to each task defined in the proposal; (2) a percentage completion of each task; (3) a concise discussion (2 to 3 sentences) of the current status, including accomplishments and problems encountered, if any. List all tasks, even if no work was done during this period on the task; (4) and a brief description of the activities accomplished by each member of the research team as listed in the project budget. (1)          

(2)          

(3)          

(4)          

2. Planned Work for New Quarter

         

3. Possible Project Modification (if any)

Maryland State Highway Administration

SPR Research Projects Quarterly Progress Report

Appendix D Quarterly Progress Report Template

24

Describe any challenges encountered or anticipated that might affect the completion of the project within the time, scope, and fiscal constraints set forth in the agreement, along with recommended solutions to those problems. NOTING CHALLENGES IN THIS SECTION DOES NOT CONSTITUTE A REQUEST TO MODIFY THE PROJECT. Requests for additional time, money, or scope revisions must be submitted in a separate letter to the Chief of Research. Project Personnel: Indicate any proposed changes of research personnel assigned to the project. Provide telephone numbers, fax numbers and email addresses for proposed new personnel and provide a justification for the change(s).

          Work Plan: Briefly describe changes or additions needed to the Work Plan in the current Project Agreement, and why the changes are needed.

          Deliverables: Describe changes needed to the currently approved deliverables, and why the changes are needed.

          Project Completion: Indicate whether you believe the completion date of this project should be changed, why the change is needed, and a proposed new termination date.

          Project Budget: Indicate whether you believe the project budget should be changed, why the change is needed, and describe the changes you are proposing.

         

4. Equipment (to be completed if funding has been allocated in the approved project proposal)

List equipment or systems purchased during this reporting period. Equipment is defined as items with a unit cost of $500 or more. A system is defined as two or more separate components purchased to form a functional unit. Attach evidence that the equipment has been added to the university inventory system.

         

5. Contacts & Meetings Describe any meetings or conversations with SHA technical liaisons and other pertinent individuals relative to this project.

         

6. Miscellaneous

Provide any other relevant information not covered above.          

Appendix E

25

Technical Report Documentation Page1. Report No.

MD-Fiscal Year–Project Number 2. Government Accession No. 3. Recipient's Catalog No.

4. Title and Subtitle

5. Report Date

6. Performing Organization Code

7. Author/s

8. Performing Organization Report No.

9. Performing Organization Name and Address

10. Work Unit No. (TRAIS) 11. Contract or Grant No.

12. Sponsoring Organization Name and Address Maryland State Highway Administration Office of Policy & Research 707 North Calvert Street Baltimore MD 21202

13. Type of Report and Period CoveredFinal Report

14. Sponsoring Agency Code

15. Supplementary Notes 16. Abstract 17. Key Words

18. Distribution Statement: No restrictions This document is available from the Research Division upon request.

19. Security Classification (of this report) None

20. Security Classification (of this page) None

21. No. Of Pages

22. Price

Form DOT F 1700.7 (8-72) Reproduction of form and completed page is authorized.

Appendix F Experimental Features Guidelines

26

CONSTRUCTION PROJECTS INCORPORATING EXPERIMENTAL FEATURES

1. What is the purpose or objective of the experimental features program?

a. The purpose of the experimental features program is to encourage highway agencies to evaluate new or innovative highway technology, or alternative standard technology,under actual construction and operating conditions by means of a program or experimental construction projects.

b. To provide a mechanism for the widespread dissemination and application of the results of these evaluations.

2. What are some key definitions of the program?

a. Control Section - a section or feature of a highway designed and constructed in a standard manner and as nearly as practicable under identical conditions so that comparisons can be made.

b. Experimental Feature - a material, process, method, equipment item, traffic operational device, or other feature that: (1) has not been sufficiently tested under actual service conditions to merit acceptance without reservation in normal highway construction, or (2) has been accepted but needs to be compared with alternative acceptable features for determining their relative merits and cost effectiveness.

c. Experimental Project - a Federal-aid highway construction project incorporating one or more experimental features.

d. Work Plan - a written program of action including a description of the experimental feature, experimental feature objectives, measurements to be made, characteristics to be evaluated, time schedules, reporting requirements, cost estimates, construction and post-construction inspection schedules, control sections, and evaluations to be conducted.

3. What are the general principles of the program?

a. Experimental Project Designation. Any Federal-aid project incorporating experimental features should be designated an experimental project and treated accordingly.

b. Work plan. A work plan is required for each experimental feature. c. Approvals

I. For projects on the Interstate system that incorporate experimental features or on any NHS route that incorporates proprietary products, the work plans must be approved by the Division Administrator prior to or with approval of Plans, Specifications, and Estimates (PS&E). Work plans for experimental projects utilizing State Planning and Research (SPR) funds need approval by the Division Administrator in accordance with normal approval procedures for SPR funded studies. (For NHS projects with State approval authority and oversight, work plan approval is delegated to the State.)

II. Experimental features included in ongoing projects by change order also need approval by the Division Administrator.

d. Control Sections. Control sections or other alternatives should be provided for performance comparisons in all experimental projects unless the nature of the experiment is such that a control section or alternative would serve no purpose.

e. Cost Data. Cost data should be compiled for all experimental and control features.

Experimental Features Guidelines Appendix F

27

f. Multiple Project Justification. Two or three construction projects should be adequate to conclusively evaluate a single feature. The justification for more than five construction projects should be carefully analyzed prior to initiation.

4. How should the results of the experimental features program be reported?

a. Reporting of results should be completed for all experimental features. All reporting(including form, content, and delivery) should follow the requirements set forth in the approved work plan. Final reports prepared utilizing SPR and non-SPR funds are to be submitted for review and approval to the FHWA Division Office in accordance with the established procedures for SPR funded RD&T studies. Two copies of the final report should be provided to the FHWA Division Administrator. The Division Office should forward one copy to the following address:

FHWA Office of Research and Technology Services Turner-Fairbank Highway Research Center, HRTS-1 6300 Georgetown Pike, Room F-204 McLean, VA 22101-2296

b. The FHWA supports the continued use of the AASHTO Product Evaluation List (APEL). Contracting agencies should provide the appropriate experimental feature evaluation report information to the APEL web site so that other agencies may benefit from their evaluations.

5. How are projects with experimental features terminated?

The Division Administrator may determine the project has been completed when the workplan goals either have been achieved or cannot be achieved.

6. How are projects with experimental features financed?

a. Total construction costs attributable to experimental features may be financed with the appropriate class of Federal-aid funds. SPR funds cannot be used for constructing experimental features.

b. Evaluation costs may be financed with the same class of funds used for construction of the experimental feature, SPR funds, or non-Federal funds. If SPR funds are used,the administrative requirements in 23 CFR Part 420 are applicable.

7. Is this non-regulatory supplemental guidance for construction projects incorporating experimental features equivalent to the "request to experiment" process outlined in the Manual on Uniform Traffic Control Devices (MUTCD)?

No, this non-regulatory supplemental guidance is separate and distinct from the "Request to Experiment" process outlined in the MUTCD.

Updated 10/31/08

Appendix G

23 CFR 420, Planning and Research Program Administration 

28

Title 23--Highways CHAPTER I--FEDERAL HIGHWAY ADMINISTRATION, DEPARTMENT OF TRANSPORTATION PART 420--PLANNING AND RESEARCH PROGRAM ADMINISTRATION

23 CFR 420, Planning and Research  Program Administration

Appendix G

29

Appendix G

23 CFR 420, Planning and Research Program Administration 

30

23 CFR 420, Planning and Research  Program Administration

Appendix G

31

Appendix G

23 CFR 420, Planning and Research Program Administration 

32

23 CFR 420, Planning and Research  Program Administration

Appendix G

33

Appendix G

23 CFR 420, Planning and Research Program Administration 

34

23 CFR 420, Planning and Research  Program Administration

Appendix G

35

Appendix G

23 CFR 420, Planning and Research Program Administration 

36

23 CFR 420, Planning and Research  Program Administration

Appendix G

37

Appendix G

23 CFR 420, Planning and Research Program Administration 

38

23 CFR 420, Planning and Research  Program Administration

Appendix G

39

Appendix G

23 CFR 420, Planning and Research Program Administration 

40

Glossary Appendix H

41

Selected Research Terms Accuracy – The degree to which an estimate represents the true state of nature, e.g. freedom from error. (See “precision” for contrast) ANOVA – Refers to ANalysis Of VAriance, and involves the analysis of the total variability of a set of data into components that can be attributed to different sources of variation, e.g. random fluctuations and systematic differences. Applied Research – Research that is undertaken to extend knowledge in pursuit of specific objectives with a specific practical application in view. Applied research is the dominant activity in state transportation research programs. Basic Research – Research that is undertaken to extend knowledge and understanding without concern for the utility of the findings. Before-After Study – A study where data is collected prior to and following an event or action. Data taken at each point is compared and analyzed to identify the effect of the event or action. It is often presumed that the event or action caused a change in the observed measurement, but such presumption is not always valid (see causative relationship). Causative Relationship – By definition a relationship where a change in one variable of a pair causes a change in the other variable. Three conditions must be satisfied to establish a causative relationship, they are: consistency, responsiveness and mechanism. Consistency refers to when a change in one variable of the pair is made a change in the other variable follows it and that a similar result occurs for each test. Responsiveness means that a change in the independent variable results in a change in the dependent variable and that suppressing the first event always suppresses the effect. A mechanism means that there must be some viable explanation or connection between the two factors. If these three factors are not present the relationship should be presumed to be casual, not causative. Cross-Sectional Study – A study collecting data on some variable at a particular period of time from different geographical areas, households, organizations, etc. Development – The process of arriving at a satisfactory design of a viable application of new knowledge by designing, testing and evaluating. Empirical – Based on observation and experiment rather than theory. Endogenous – Caused by internal factors, e.g. inside the model. Exogenous - Caused by outside influences, e.g. outside the model. Experiment – A set of measurements carried out under specific and controlled conditions to discover, verify or illustrate a theory, hypothesis or relationship.

Appendix H Glossary 

42

Experimental Methods – Experimental methods begin with a hypothesis. An experiment is then designed to test the hypothesis by observing the response of a variable to change in a limited number of other variables under controlled conditions. Recorded observations are evaluated to explain relationships and to refute or support the hypothesis. Hypothesis – A hypothesis is a trial idea or conjectural statement about relationship between two or more variables. A statistical hypothesis is a formal statement about the underlying mechanisms that generated the observed data. Observational Method – The scientific method of recording observations according to a plan, then analyzing and interpreting the data collected from a valid statistical sample to develop a theory or hypothesis that explains the observations. Precision – Refers to the exactness of a set of measurements, e.g. a precise set of measurements have little variance from the sample mean. (See “accuracy” for contrast) Research – The application of a systematic and rigorous process, i.e. Scientific Method, to extend knowledge on a larger organizational need or subject. Research can be applied or basic. Research Project Work Plan – The scope of work for a specific research project that addresses what will be done, how it will be done, who will do it, when it will be done and what it will cost. Research Work Program – A work program is a compilation of individual research projects and technology transfer activities that will be undertaken over a specific time period, e.g. a fiscal year. Scientific Method – The theoretical and empirical processes of discovery and demonstration by a rigorous and systematic approach. Three types of methods are recognized: Observational Method, Experimental Methods and the Survey Method. Survey Method – Surveys are used to obtain information not generally available under other circumstances via a sample of a population. Collected responses are then analyzed to improve understanding regarding the issues surveyed and to assess relationships among responses. Technology Transfer – Activities associated with the dissemination of knowledge that leads to the adoption of new techniques or eventual innovation. Times Series – A set of observations on a characteristic or phenomenon taken at different points of time. Validity – The degree to which a procedure or model is founded on logic or corresponds to nature, e.g. the real world.