Purpose Timescale Summary of Involvement Reporting Mechanism Sample Clauses

Purpose Timescale Summary of Involvement Reporting Mechanism. Inspectors Report The Inspector will publish a report outlining the examination’s findings, together with any changes to the Deposit Plan and reasons for those recommendations. The Inspector’s decisions will be binding upon the Council. September2023 (indicative) Adoption The Council is required to adopt the final LDP incorporating the Inspector’s recommendations within 8 weeks of receiving it, unless the Welsh Government intervenes. October 2023 (indicative) • On or before the day on which the LDP is adopted, the Council will publish the Inspector’s Report and make it available for inspection and to view on Council’s web site. The Local Development Plan will become operative on the date it is adopted, and final publication of the Plan should follow as soon as possible (after the expiry of the six-week legal challenge period).
AutoNDA by SimpleDocs
Purpose Timescale Summary of Involvement Reporting Mechanism. Inspectors Report The Inspector will publish a report outlining the examination’s findings, together with any changes to the Deposit Plan and reasons for those recommendations. The Inspector’s decisions will be binding upon the Council. September2024 (indicative) Adoption The Council is required to adopt the final Replacement LDP incorporating the Inspector’s recommendations within 8 weeks of receiving it, unless the Welsh Government intervenes. October 2024 (indicative) • On or before the day on which the Replacement LDP is adopted, the Council will publish the Inspector’s Report and make it available for inspection and to view on Council’s web site. The Replacement LDP will become operative on the date it is adopted, and final publication of the Replacement Plan should follow as soon as possible (after the expiry of the six-week legal challenge period).

Related to Purpose Timescale Summary of Involvement Reporting Mechanism

  • PROJECT MILESTONES, REPORTING AND PAYMENTS 15. The milestones for the projects, their relationship to the outputs, expected completion dates, relevant reporting dates and expected payments to be made are set out in bilateral schedules to this Agreement. The Commonwealth will make payments subject to the performance reports demonstrating the relevant milestone has been met.

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

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

  • Progress Reporting 5. The IP will submit to UNICEF narrative progress reports against the planned activities contained in the Programme Document, using the PDPR. Unless otherwise agreed between the Parties in writing, these reports will be submitted at the end of every Quarter. The final report will be submitted no later than thirty (30) calendar days after the end the Programme and will be provided together with the FACE form.

  • 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

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

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

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

  • Child Abuse Reporting Requirement Grantee will:

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

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