Extension of the Implementation Schedule Sample Clauses

Extension of the Implementation Schedule. Deadlines: If, given written justification from the Discharger and the Regional Water Board staff determines that a delay in the SEP implementation schedule is beyond the reasonable control of the Discharger, the Executive Officer may revise the implementation schedule as appropriate. Written justification must be received by the Designated Regional Water Board Representative before the specific due date occurs, must describe circumstances causing the delay, and must state when each task of the SEP will be completed. If any extension of the implementation schedule is granted, the Regional Water Board staff shall provide the Discharger a new implementation schedule in writing, which shall include the date the SEP will be completed (Revised SEP Completion Date).
Sample 1Sample 2
AutoNDA by SimpleDocs
Extension of the Implementation Schedule. Deadlines: If, given written justification from the Discharger, the Executive Officer determines that a delay in the CP implementation schedule is beyond the reasonable control of the Discharger, the Executive Officer may revise the implementation schedule as appropriate. Written justification must be received by the Regional Water Board representative identified Digitally signed by Xxxxxx Xxxxxx Date: 2018.05.04 13:44:25 -07'00' Digitally signed by Xxxxxxxx Xx.Xxxx Date: 2018.05.04 16:31:49 -07'00' Exhibit A‌‌ Compilation of Violations Ferndale City POTW WDID No. 1B83136OHUM NPDES No. CA0022721
Sample 1

Related to Extension of the Implementation Schedule

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Construction Schedule The progress schedule of construction of the Project as provided by Developer and approved by District.

  • Supplemental Conditions 1. All individuals involved, and all others who might possibly contribute to the acceptable adjustment of a grievance, are authorized and urged to testify with full assurance that no reprisal will follow by reason of such participation.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.

  • Modifications/Add-ons 6.3.1 Licensee shall comply with SAP’s registration procedure prior to making Modifications or Add-ons. All Modifications and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. All Add-ons developed by SAP (either independently or jointly with Licensee) and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. Licensee agrees to execute those documents reasonably necessary to secure SAP’s rights in the foregoing Modifications and Add-ons. All Add-ons developed by or on behalf of Licensee without SAP’s participation (“Licensee Add-on”), and all rights associated therewith, shall be the exclusive property of Licensee subject to SAP’s rights in and to the Software and SAP Materials; provided, Licensee shall not commercialize, market, distribute, license, sublicense, transfer, assign or otherwise alienate any such Licensee Add-ons. SAP retains the right to independently develop its own Modifications or Add-ons to the Software, and Licensee agrees not to take any action that would limit SAP’s sale, assignment, licensing or use of its own Software or Modifications or Add-ons thereto.

  • Additional Conditions For each mediation or arbitration:

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • ADDITIONAL CONTRACTOR TERMS AND CONDITIONS WITHIN AN AUTHORIZED USER AGREEMENT Additional Contractor Terms and Conditions may become part of an Authorized User Agreement in accordance with Section 28 of Appendix B. EMPLOYEE INFORMATION REQUIRED TO BE REPORTED BY CERTAIN CONSULTANT CONTRACTORS AND SERVICE CONTRACTORS Civil Service Law § 97 and State Finance Law § 163 establish reporting requirements for maintaining certain information concerning Contract Employees working under State Agency service and consulting Contracts. State Agency consultant Contracts are defined as “Contracts entered into by a state Agency for analysis, evaluation, research, training, data processing, computer programming, engineering, environmental health and mental health services, accounting, auditing, paralegal, legal, or similar services” (“covered consultant Contract” or “covered consultant services”). The information must be provided to the state Agency awarding such Contracts, OSC, DOB and CS. To meet these requirements, the Contractor agrees to complete:

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