Project Abstract. Each proposal should contain a project abstract that summarizes the project objectives and tasks. The abstract should be no more than 200 words and is prepared free form (no RTI form needed). This section of the selected proposal will become part of the Project Agreement; the Abstract should be direct. Use contractual phrases which are definitive, such as – “this project shall”, rather than “we propose to” or “the proposed project will”. The primary value of the abstract is to clearly and succinctly describe the project. The ability to succinctly summarize the work proposed to do help demonstrate the understanding of the project. For successful proposals, the abstract is used to enter a project description into relevant databases, including. • TxDOT's research database(s) • Transportation Research Board’s (TRB) Research in Progress system Implementation (for research projects only) At the university’s option, include a free form section by this title that presents the researcher's assessment of potential areas for application of the research findings, such as changes in specifications, standards, or department policies. If included, this section should also include an assessment of which TxDOT operations will be affected. When deciding whether or not to include an implementation section, consider the project being proposed, and what the project results will look like. If including thoughts about the implementation will better explain the project or knowledge of the area, include the section. For projects expected to produce results which could be implemented either during the progress of the project or shortly after completion, material in this section might include an assessment of several issues. The form in which the findings would be most effectively reported • mathematical model or formula • laboratory test procedure • design techniques The organization logically responsible for application of the results • American Association of State Highway and Transportation Officials (AASHTO) • Federal Highway Administration (FHWA) • Texas Department of Transportation (TxDOT) Division or District The specific medium of practice that would be changed or developed by the findings • AASHTO Standard Specifications • TxDOT Standard Specifications • special specifications The best method to convey the research findings to operating personnel for use • circulation of a written report • personal contact with operating personnel • demonstrations • movie, slide, or videotape presentation • field manuals • training classes Work Plan The Work Plan is a free form section that should fully describe the approach researchers intend to use and specify how the project will be structured and performed. For joint projects or projects with subcontractors, the Work Plan should specify which entity(s) will be performing the work on each task. Ideally, each task in the Work Plan is separate and distinct. A well written Work Plan will also describe dependencies and relationships between the tasks, including the project’s critical path. The Work Plan for a research and implementation project should contain at least the following information. • How the project and each deliverable/ tasks will be managed. • Principles or theories to be used. • Possible solutions to the problem. • The device, process, material, or system to be developed or enhanced, when applicable. • Critical experiments to test the applicability of the theory or the item developed. • Data analysis and statistical procedures. Proprietary techniques owned by the university can, and should be discussed in a way that demonstrates the researchers’ knowledge and skill without revealing any proprietary information owned by the university. The Work Plan should not include additional information about the background and significance of the project, or researchers’ qualifications. That information belongs in other sections of the proposal. The ability to describe a clear, complete and concise Work Plan helps demonstrate the management skills and knowledge of the project. Each task in the Work Plan should highlight the expected deliverable or outcome from the work performed in the task and cross reference to the deliverables table. The deliverables can be in the form of white papers, work products (excel spreadsheets, instructor manuals, models, enhanced or developed systems, devices), seminars, close out meets, and technical reports to name a few. Technical Memos are numbered sequentially by task number.
Appears in 1 contract
Sources: Deliverable Base Project Agreements
Project Abstract. Each proposal should contain a project abstract that summarizes the project objectives and tasks. The abstract should be no more than 200 words and is prepared free form (no RTI form needed). This section of the selected proposal will become part of the Project Agreement; the Abstract should be direct. Use contractual phrases which are definitive, such as – “this project shall”, rather than “we propose to” or “the proposed project will”. The primary value of the abstract is to clearly and succinctly describe the project. The ability to succinctly summarize the work proposed to do help demonstrate the understanding of the project. For successful proposals, the abstract is used to enter a project description into relevant databases, including. • TxDOT's research database(s) • Transportation Research Board’s (TRB) Research in Progress system Implementation (for research projects only) At the university’s option, university should include a free form section by this title that presents the researcher's assessment of potential areas for application of the research findings, such as changes in specifications, standards, or department policies. If included, this section should also include an assessment of which TxDOT operations will be affected. When deciding whether or not to include an implementation section, consider the project being proposed, and what the project results will look like. If including thoughts about the implementation will better explain the project or knowledge of the area, include the section. For projects expected to produce results which could be implemented either during the progress of the project or shortly after completion, material in this section might include an assessment of several issues. The form in which the findings would be most effectively reported • mathematical model or formula • laboratory test procedure • design techniques The organization logically responsible for application of the results • American Association of State Highway and Transportation Officials (AASHTO) • Federal Highway Administration (FHWA) • Texas Department of Transportation (TxDOT) Division or District The specific medium of practice that would be changed or developed by the findings • AASHTO Standard Specifications • TxDOT Standard Specifications • special specifications The best method to convey the research findings to operating personnel for use • circulation of a written report • personal contact with operating personnel • demonstrations • movie, slide, or videotape presentation • field manuals • training classes Work Plan The Work Plan is a free form section that should fully describe the approach researchers intend to use and specify how the project will be structured and performed. For joint projects or projects with subcontractors, the Work Plan should specify which entity(s) will be performing the work on each task. Ideally, each task in the Work Plan is separate and distinct. A well written Work Plan will also describe dependencies and relationships between the tasks, including the project’s critical path. The Work Plan for a research and implementation project should contain at least the following information. • How the project and each deliverable/ tasks will be managed. • Principles or theories to be usedused (Not included in implementation projects). • Possible solutions to the problem. • The device, process, material, or system to be developed or enhanced, when applicable. • Critical experiments to test the applicability of the theory or the item developed. • Data analysis and statistical procedures. Proprietary techniques owned by the university can, and should be discussed in a way that demonstrates the researchers’ knowledge and skill without revealing any proprietary information owned by the university. The Work Plan should not include additional information about the background and significance of the project, or researchers’ qualifications. That information belongs in other sections of the proposal. The ability to describe a clear, complete and concise Work Plan helps demonstrate the management skills and knowledge of the project. Each task in the Work Plan should highlight the expected deliverable or outcome from the work performed in the task and cross reference to the deliverables table. The deliverables can be in the form of white papers, work products (excel spreadsheets, instructor manuals, models, enhanced or developed systems, devices), seminars, close out meets, and technical reports to name a few. Technical Memos are numbered sequentially by task number.
Appears in 1 contract
Sources: Deliverable Base Project Agreements