Harmonogram of Project Interim Report submission Sample Clauses

Harmonogram of Project Interim Report submission. 4.3.1 Project Promoter is obligated to submit Project Interim Report within 15 working days after the end of each reporting period specified in Table 10. 4.3.2 If the Project contract comes into effectiveness in the second half of the respective Reporting period, Program Operator will join this Reporting period with the following Reporting period. 4.3.3 The principle from aforementioned article can be used also in case the full Project Interim Report will not be submitted within the designated time limit, in case the Project Interim Report was rejected or the approval of report was suspended and in others similar cases.
AutoNDA by SimpleDocs

Related to Harmonogram of Project Interim Report submission

  • REPORT SUBMISSION 1. Copies of reporting packages for audits conducted in accordance with 2 CFR Part 200, Subpart F-Audit Requirements, and required by PART I of this form shall be submitted, when required by 2 CFR 200.512, by or on behalf of the recipient directly to the Federal Audit Clearinghouse (FAC) as provided in 2 CFR 200.36 and 200.512 A. The Federal Audit Clearinghouse designated in 2 CFR §200.501(a) (the number of copies required by 2 CFR §200.501(a) should be submitted to the Federal Audit Clearinghouse), at the following address: Federal Audit Clearinghouse Bureau of the Census 0000 Xxxx 00xx Xxxxxx Xxxxxxxxxxxxxx, XX 00000 Submissions of the Single Audit reporting package for fiscal periods ending on or after January 1, 2008, must be submitted using the Federal Clearinghouse’s Internet Data Entry System which can be found at xxxx://xxxxxxxxx.xxxxxx.xxx/facweb/ 2. Copies of financial reporting packages required by PART II of this Attachment shall be submitted by or on behalf of the recipient directly to each of the following: A. The Department of Environmental Protection at one of the following addresses: By Mail: Florida Department of Environmental Protection Office of Inspector General, MS 40 0000 Xxxxxxxxxxxx Xxxxxxxxx Tallahassee, Florida 32399-3000 Electronically: XXXXXxxxxxXxxxx@xxx.xxxxx.xx.xx B. The Auditor General’s Office at the following address: Auditor General Local Government Audits/342 Xxxxxx Xxxxxx Building, Room 000 000 Xxxx Xxxxxxx Xxxxxx Xxxxxxxxxxx, Xxxxxxx 00000-1450 The Auditor General’s website (xxxx://xxxxxxxxx.xxx/) provides instructions for filing an electronic copy of a financial reporting package. 3. Copies of reports or management letters required by PART III of this Attachment shall be submitted by or on behalf of the recipient directly to the Department of Environmental Protection at one of the following addresses: By Mail: Florida Department of Environmental Protection Office of Inspector General, MS 40 0000 Xxxxxxxxxxxx Xxxxxxxxx Tallahassee, Florida 32399-3000 Electronically: XXXXXxxxxxXxxxx@xxx.xxxxx.xx.xx 4. Any reports, management letters, or other information required to be submitted to the Department of Environmental Protection pursuant to this Agreement shall be submitted timely in accordance with 2 CFR 200.512, section 215.97, F.S., and Chapters 10.550 (local governmental entities) or 10.650 (nonprofit and for-profit organizations), Rules of the Auditor General, as applicable. 5. Recipients, when submitting financial reporting packages to the Department of Environmental Protection for audits done in accordance with 2 CFR 200, Subpart F-Audit Requirements, or Chapters 10.550 (local governmental entities) and 10.650 (non and for-profit organizations), Rules of the Auditor General, should indicate the date and the reporting package was delivered to the recipient correspondence accompanying the reporting package.

  • Development Reports Beginning six months after Effective Date and ending on the date of first commercial sale of a Licensed Product in the United States, LICENSEE shall report to Cornell progress covering LICENSEE's (and Affiliate's and Sublicensee's) activities and efforts in the development of rights granted to LICENSEE under this Agreement for the preceding six months. The report shall include, but not be limited to, activities and efforts to develop and test all Licensed Products and obtain governmental approvals necessary for marketing the same. Such semi-annual reports shall be due within sixty days (60) of the reporting period and shall use the form as provided herein as Appendix C.

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Project Initiation i - Upon final execution of the Agreement with the DISTRICT, the ARCHITECT shall: ♦ Review the Program Management Plan (PMP) with the DISTRICT and its representatives to familiarize them with the proposed tasks and schedule and develop necessary modifications. The PMP defines the Program Master Schedule and Budgets and each Project scope and budget. ii - Within the first week following execution of the Agreement, meet with the DISTRICT and its representatives to prepare a detailed task analysis and work plan for documentation in a computer-generated project schedule. iii - This task analysis and work plan will identify specific tasks including, but not limited to: ♦ interviews, ♦ data collection ♦ analysis, ♦ report preparation, ♦ planning, ♦ Architectural programming, concepts and schematic design preparation and estimating that are part of the work of the Project. Also identified will be milestone activities or dates, specific task responsibilities, required completion times necessary for the review and approval by the DISTRICT and by all regulatory agencies and additional definition of deliverables. iv - Participate in a general Project kick-off meeting to include the ARCHITECT, appropriate sub-consultants, and DISTRICT staff. v - The project kick-off meeting will introduce key team members from the DISTRICT and the ARCHITECT to each other, defining roles and responsibilities relative to the Project. vi - Identify and review pertinent information and/or documentation necessary from the DISTRICT for the completion of the Project. vii - Review and explain the overall project goals, general approach, tasks, work plan and procedures and deliverable products of the Project. viii - Review and explain the task analysis and Project work plan for all parties present; determine any adjustments or fine tuning that needs to be made to the work plan. ix - Review documentation of the Project kick-off meeting prepared by the DISTRICT’S representative and comment prior to distribution. x - Base Drawings and Site Survey Information

  • Research Plan The Parties recognize that the Research Plan describes the collaborative research and development activities they will undertake and that interim research goals set forth in the Research Plan are good faith guidelines. Should events occur that require modification of these goals, then by mutual agreement the Parties can modify them through an amendment, according to Paragraph 13.6.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Project Work Plan The Statement of Work is the formal document incorporated into the Grant. The Project Work Plan documents how the Grantee will achieve the performance measures outlined in the Grant. Changes to the Statement of Work require an amendment. Project Work Plans may be changed with written approval from PEI and the Grantee.

  • Invoice Submission All invoices submitted by Contractor shall include the City Contract Number, an assigned Invoice Number, and an Invoice Date. Contractor shall be provided with a cover sheet for invoicing. This cover sheet must be filled out correctly and submitted with each invoice. Contractor shall submit the original invoice through the responsible City Project Manager at: City of Ocala Engineer’s Office, Attn: Xxxxx Xxxxxxxxxx, 0000 XX 00xx Xxxxxx, Xxxxxxxx 000, Xxxxx, Xxxxxxx 00000, E-Mail: xxxxxxxxxxx@xxxxxxx.xxx.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!