Developer Obligation to Manage and Operate Sample Clauses

Developer Obligation to Manage and Operate. (a) At all times following the Service Commencement Date, the Developer, at its sole cost and expense (except as otherwise provided herein), will cause the Project Assets to be managed, maintained and operated in accordance with Law, all Governmental Approvals, the terms, conditions and standards set forth in this Agreement, including the requirements set forth in the Technical Requirements, and in accordance with Good Industry Practice. Without limiting the foregoing, the Developer agrees to be responsible for the following, at its sole cost and expense at all times following the Service Commencement Date for the Project:
AutoNDA by SimpleDocs
Developer Obligation to Manage and Operate. 56 Section 9.03 Procedures Relating to Maintenance Work ..........................................58 Section 9.04 Major Maintenance Reserve Fund .........................................................60 Section 9.05 Police and Enforcement Services ............................................................60 Section 9.06 Maintenance by the Department ............................................................61 Section 9.07
Developer Obligation to Manage and Operate. (a) At all times following the Service Commencement Date, the Developer, at its sole cost and expense (except as otherwise provided herein), will cause the Project Assets to be managed, maintained and operated in accordance with Law, all Governmental ...
Developer Obligation to Manage and Operate 

Related to Developer Obligation to Manage and Operate

  • Parallel Operation Obligations Once the Small Generating Facility has been authorized to commence parallel operation, the Interconnection Customer shall abide by all rules and procedures pertaining to the parallel operation of the Small Generating Facility in the applicable control area, including, but not limited to: (1) the rules and procedures concerning the operation of generation set forth in the NYISO tariffs or ISO Procedures or the Connecting Transmission Owner’s tariff; (2) any requirements consistent with Good Utility Practice or that are necessary to ensure the safe and reliable operation of the Transmission System or Distribution System; and (3) the Operating Requirements set forth in Attachment 5 of this Agreement.

  • Obligation to Provide Information Each party’s obligation to provide information shall be as follows:

  • OBLIGATION TO NEGOTIATE 50.01 The Employer and the Union acknowledge that during negotiations which preceded this Agreement, each had the unlimited right and opportunity to make demands and proposals with respect to any subject or matter not removed by law from the area of collective bargaining/negotiations and that the understandings and agreements arrived at by the parties after the exercise of that right and opportunity are set forth in this Agreement.

  • Exceptions to the obligation to provide assistance 1. Assistance may be refused or may be subject to the satisfaction of certain conditions or requirements, in cases where a Party or the EAC Partner States as the case may be concerned is of the opinion that assistance under this Protocol would:

  • Obligation to Provide Public Access to Grant Records The Division reserves the right to unilaterally cancel this Agreement in the event that the Grantee refuses public access to all documents or other materials made or received by the Grantee that are subject to the provisions of Chapter 119, Florida Statutes, known as the Florida Public Records Act. The Grantee must immediately contact the Division's Contract Manager for assistance if it receives a public records request related to this Agreement.

  • Developer’s Obligations (a) Upon the expiry of the Agreement Period by efflux of time and in the normal course, the Developer shall on the Expiry Date, hand back vacant and peaceful possession of Project Site and the Project Facilities to the Authority free of cost and in good operable condition.

  • Exception to Obligations Neither Party's obligations under this Section shall apply to the extent the infringement is caused by: (i) modification of the facilities or equipment (including software) by the indemnitee; (ii) use by the indemnitee of the facilities or equipment (including software) in combination with equipment or facilities (including software) not provided or authorized by the indemnitor, provided the facilities or equipment (including software) would not be infringing if used alone; (iii) conformance to specifications of the indemnitee which would necessarily result in infringement; or (iv) continued use by the indemnitee of the affected facilities or equipment (including software) after being placed on notice to discontinue use as set forth herein.

  • Obligation to Maintain Confidentiality The Executive acknowledges that the continued success of the Company depends upon the use and protection of a large body of confidential and proprietary information, including confidential and proprietary information now existing or to be developed in the future. “Confidential Information” will be defined as all information of any sort (whether merely remembered or embodied in a tangible or intangible form) that is (i) related to the Company’s prior, current or potential business and (ii) not generally or publicly known. Therefore, the Executive agrees not to disclose or use for the Executive’s own account any of such Confidential Information, except as reasonably necessary for the performance of the Executive’s duties as an employee or director of the Company, without prior written consent of the Board, unless and to the extent that any Confidential Information (i) becomes generally known to and available for use by the public other than as a result of the Executive’s improper acts or omissions to act or (ii) is required to be disclosed pursuant to any applicable law, regulatory action or court order; provided, however, that the Executive must give the Company prompt written notice of any such legal requirement, disclose no more information than is so required, and cooperate fully with all efforts by the Company (at the Company’s sole expense) to obtain a protective order or similar confidentiality treatment for such information. Upon the termination of the Executive’s employment with the Company, the Executive agrees to deliver to the Company, upon request, all memoranda, notes, plans, records, reports and other documents (including copies thereof and electronic media) relating to the business of the Company (including, without limitation, all Confidential Information) that the Executive may then possess or have under the Executive’s control, other than such documents as are generally or publicly known (provided, that such documents are not known as a result of the Executive’s breach or actions in violation of this Agreement); and at any time thereafter, if any such materials are brought to the Executive’s attention or the Executive discovers them in the Executive’s possession, the Executive shall deliver such materials to the Company immediately upon such notice or discovery. The provisions of this Section 10.2(a) shall specifically survive the expiration or earlier termination of this Agreement and the termination of the Executive’s employment with the Company.

  • Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.

  • APPLICANT’S OBLIGATION TO MAINTAIN VIABLE PRESENCE In order to receive and maintain the limitation authorized by Section 2.4 in addition to the other obligations required by this Agreement, the Applicant shall Maintain Viable Presence in the District commencing at the start of the Tax Limitation Period through the Final Termination Date of this Agreement. Notwithstanding anything contained in this Agreement to the contrary, the Applicant shall not be in breach of, and shall not be subject to any liability for failure to Maintain Viable Presence to the extent such failure is caused by Force Majeure, provided the Applicant makes commercially reasonable efforts to remedy the cause of such Force Majeure.

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