Final Technical Report a) The Recipient shall submit two copies of the final technical report to the USGS Project Officer and one copy of the transmittal letter to the USGS Contracting Officer. The final performance report will be due 90 calendar days after the period of performance end date.
Final Technical Report. The Recipient shall submit or otherwise provide a Final Technical Report making disclosure of all major accomplishments by the project upon completion of the Agreement or within sixty (60) calendar days of termination of this Agreement. With the approval of the NSRP ASE Program Administrator, reprints of published articles may be attached to the Final Technical Report. As an attachment to the Final technical Report, the Project Results Template as shown in this attachment shall be used to develop a short, executive-level overview of the project. The project results overview should only contain information that can be released to the public, as this document may be separated from the Final Technical Report and used as a technology transfer tool to help other U.S. shipyards learn of the project objective and results and obtain point of contact information for possible future implementation. The complete Final Technical Report shall be submitted in an electronic format to the Program Technical Manager and the Program Technical Representative. The Final Technical Report and all other reports delivered under this Agreement shall be marked with a distribution statement to denote the extent of its availability for distribution, release, and disclosure without additional approvals or authorizations.
Final Technical Report. (i) Final Technical Report (FTR). A Final Technical Report shall be submitted to the CMF within thirty (30) calendar days of the completion of the Project Agreement. This report will provide a comprehensive, cumulative, and substantive summary of the progress and significant accomplishments achieved during the total period of the effort. Each of the topics described above shall be addressed as appropriate for the effort performed. Upon receipt, the AOR will review and provide any comments within 30 days. If necessary, the PAH will update the FTR within 30 days of receipt of AOR’s comments. Once the CMF has informed PAH that the FTR has been approved by the AOR, the PAH shall forward a copy of the FTR to the Defense Technical Information Center, Attn. DTIC-O, 8725 Xxxx X. Xxxxxxx Xxxx, Xxxxx 0000, Xxxx Xxxxxxx, XX 00000-0000.
Final Technical Report. In the month that an award is due to expire, a request notification for the Final Technical Report will be sent electronically to the award contact designated in REEport. The Final Technical Report is required within 90 calendar days after the expiration or termination of the award. The Final Technical Report covers the entire period of performance of the award and must describe progress made during the entire timeframe of the project instead of covering accomplishments made only during the final reporting segment of the project. In addition to supplying the information required under item b. of this article, the final report must include the following when applicable: Identify equipment purchased with any Federal funds under the award and indicate subsequent use of such equipment. Failure to submit an acceptable Final Technical Report within 90 calendar days after the award’s anniversary date may result in funds being withheld for other active NIFA grants for which the Project Director(s) under this award are also named as well as prevent the award of future NIFA grants until the required report has been received in the REEport system and approved by NIFA.
Final Technical Report. University shall submit a Final Technical Report to Sponsor no later than ______. The Final Technical Report shall comprehensively address the research results as they apply to the objectives identified in Exhibit A.
Final Technical Report. In the final technical report the Beneficiary/Coordinator must provide detailed information on the implementation of the activities and the results achieved by the project. This document will be used in two ways. Firstly, to evaluate the project results against the content of Annex I to the Grant Agreement in order to verify that the results correspond in terms of both quality and content to what was described when applying for the grant. Secondly, to ensure coherence between the financial statement and the activities undertaken during the project implementation. The reporting template is published on the call for proposals webpage. It contains detailed instructions. No other format is accepted. It consists of a series of questions meant to help the Beneficiary/Coordinator provide a clear focussed report that can be easily understood. The report (or any part thereof) may also be ultimately published by the Commission as part of its communication activities. Therefore, the report should provide information enabling any reader to: • Understand the project – why it was implemented, how it was implemented (methodology), etc.; • Understand the results of the project, its added value and the lessons learned from it; • Understand what problems or difficulties were encountered and how they were overcome; • Be guided to further sources of information in the area covered by the project.
Final Technical Report. Refers to the final report on the implementation of each BASE STATION as part of the requirement for the signature of the Certificate of Acceptance.
Final Technical Report. 1. Project Title: University of Nebraska-Lincoln, Conservation & Survey Division cooperative agreement to support persistent data services and well maintenance.
Final Technical Report. (FTR) (CDRL A012). For each TO, the Contractor shall provide two detailed technical reports to include task background, objectives, assumptions, specific data collected, analyses conducted, conclusions and recommendations. Each report shall be delivered to the Requiring Activity (RA) ACOR and COR. Under authority of the RA, (when an unclassified document or a classified document) with approval by the COR, each TR shall have a Distribution Statement in accordance with DoD Directive 5230.24, ‘Distribution Statements on Technical Documents. Every effort will be made to avoid utilizing Distribution F (Further Distribution Only As Directed By The Requiring Activity Identified In The PWS For Each Individual Task Order). However, if sensitive internal information is contained in the TR, a sanitized version of the TR shall be created for distribution within DoD (Distribution D) and inclusion in the DTIC Database (STI repository). If the TR is CLASSIFIED, the COR and RA will review the document for appropriate security markings IAW DoD Security Guidelines and will also have an appropriate distribution statement assigned. The Contractor shall submit an UNCLASSIFIED abstract (Report Documentation Forms, Standard Form 298) of every TR (i.e., all TO report deliverables) for all TRs containing classified information. The COR will be responsible for coordinating and submitting documents to the IAC BCO centers for inclusion in the DTIC Database. The first report will be due after 30 months for an order with a period of performance of sixty months with or without options. Only one final report is required for any period of performance that is less than 30 months. The final report is due no later than 45 days prior to the last date of the order’s period of performance.
Final Technical Report. Upon receipt of comments from the County, Xxxxxxx will make the necessary revisions to the draft report and prepare the final report, which will incorporate input received.
