Programme reporting metrics Sample Clauses

Programme reporting metrics a. As a minimum the Recipient will provide quarterly activity based performance metrics. These metrics must be included in any agreement with an external provider.
AutoNDA by SimpleDocs

Related to Programme reporting metrics

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

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Performance Reporting The State of California is required to submit the following financial reports to FEMA:

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Project Monitoring Reporting Evaluation A. The Project Implementing Entity shall monitor and evaluate the progress of its activities under the Project and prepare Project Reports in accordance with the provisions of Section 5.08(b) of the General Conditions and on the basis of indicators agreed with the Bank. Each such report shall cover the period of one

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

  • Reporting TIPS Sales Vendor must report all TIPS Sales to TIPS. If a TIPS sale is initiated by Vendor receiving a TIPS Member’s purchase order from TIPS directly, Vendor may consider that specific TIPS Sale reported. Otherwise, with the exception of TIPS Automated Vendors, who have signed an exclusive agreement with TIPS regarding reporting, all TIPS Sales must be reported to TIPS by either: (1) Emailing the purchase order or similar purchase document (with Vendor’s Name, as known to TIPS, and the TIPS Contract Name and Number included) to TIPS at xxxxxx@xxxx-xxx.xxx with “Confirmation Only” in the subject line of the email within three business days of Vendor’s acceptance of the order, or; (2) Within 3 business days of the order being accepted by Vendor, Vendor must login to the TIPS Vendor Portal and successfully self-report all necessary sale information within the Vendor Portal and confirm that it shows up accurately on your current Vendor Portal statement. No other method of reporting is acceptable unless agreed to by the Parties in writing. Failure to report all sales pursuant to this provision may result in immediate cancellation of Vendor’s TIPS Contract(s) for cause at TIPS’ sole discretion. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx.

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only) The wind generation facility shall, at a minimum, be required to provide the Transmission Provider with site-specific meteorological data including: • Temperature (degrees Fahrenheit) • Wind speed (meters/second) • Wind direction (degrees from True North) • Atmosphere pressure (hectopascals) • Forced outage data (wind turbine and MW unavailability)

Time is Money Join Law Insider Premium to draft better contracts faster.