Technical Reports and Access to Project Results Sample Clauses

Technical Reports and Access to Project Results. Awardee shall disclose all Project Results to CEPI’s Project Lead, at meetings of the JMAG and shall provide written reports of progress made under the iPDP using a template provided by CEPI (“Technical Reports”), within twenty (20) Business Days of the end of each calendar quarter during the term of the Project as set out in the iPDP. In addition, the Awardee shall make Project Results available to CEPI as described in the iPDP or otherwise as may reasonably be requested from time to time by CEPI.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Technical Reports and Access to Project Results. Each Partner shall disclose to CEPI’s Project Lead at JMAG meetings the Project Data that such Partner has been responsible for generating under the Project, and details of progress made under the Work Package(s) for such Project, in a form (including level of abstraction) reasonably acceptable to CEPI and the applicable Partner and consistent with applicable laws and regulations. Each Partner shall provide written reports of progress made under the Work Package(s) for such Project using the template provided by CEPI and attached hereto as Annex K (“Technical Reports”) every [***] during the Term in which activities under such Project are occurring. In addition, each Partner shall make Project Data available to CEPI as designated in and required by the applicable Work Package or otherwise as may reasonably be requested by CEPI from time to time, in a form (including level of abstraction) reasonably acceptable to CEPI and the applicable Partner, and consistent with applicable laws and regulations. Technical Reports and such Project Data and Project Results disclosed or provided by a Partner under this Clause 2.5 shall be such Partner’s Confidential Information.
Sample 1Sample 2
Technical Reports and Access to Project Results. Awardee shall disclose Project Results informally to CEPI’s Project Lead, at meetings of the JMAG and through regular written reports of progress made under the iPDP using a template provided by CEPI (“Technical Reports”), within [***] of a Project’s [***]. Awardee also shall make Project Results available to CEPI as described in the iPDP or otherwise as may reasonably be requested.
Sample 1

Related to Technical Reports and Access to Project Results

  • 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.

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Technical Reports All technical reports are to be prepared jointly by the Recipient/Institution conducting Work and all collaborating institutions or as deemed acceptable by the Centre’s contact.

  • Progress Reports and Invoices The goals of this subtask are to: (1) periodically verify that satisfactory and continued progress is made towards achieving the project objectives of this Agreement; and (2) ensure that invoices contain all required information and are submitted in the appropriate format. • Submit a monthly Progress Report to the CAM. Each progress report must: o Summarize progress made on all Agreement activities as specified in the scope of work for the preceding month, including accomplishments, problems, milestones, products, schedule, fiscal status, and an assessment of the ability to complete the Agreement within the current budget and any anticipated cost overruns. See the Progress Report Format Attachment for the recommended specifications. • Submit a monthly or quarterly Invoice that follows the instructions in the “Payment of Funds” section of the terms and conditions, including a financial report on Match Fund and in-state expenditures. • Progress Reports • Invoices

  • 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.

  • Research Reports Distributor acknowledges that Dealer may prepare research reports relating to the Fund that are not to be used for marketing purposes (“Research Reports”). Distributor hereby authorizes Dealer to use the name of the Fund, Distributor and BREDS in Research Reports.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Progress Reports The Recipient shall submit to the OPWC, at the OPWC's request, summary reports detailing the progress of the Project pursuant to this Agreement and any additional reports containing such information as the OPWC may reasonably require.

  • 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.

  • 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.

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