A JV AGREEMENT Sample Clauses

A JV AGREEMENT. Except as set forth on PART 3.6 OF THE DISCLOSURE LETTER, all of the terms and conditions of the Joint Venture are set forth in the JV Agreement and no other agreement, document or understanding (oral or written) of any nature exists with respect to either the establishment of the Joint Venture or the relationship between the parties who comprise the Joint Venture. The JV Agreement has not been amended, modified, restated, superseded or nullified in any manner whatsoever. HOB has not received any notice of a default by HOB or any other party under the JV Agreement which has not been cured. The JV Agreement is a valid and binding agreement and enforceable in accordance with the terms and conditions set forth therein (assuming that the JV Agreement is valid, binding and enforceable against the other parties thereto). HOB is in compliance in all respects with the terms and provisions of the JV Agreement. To the knowledge of HOB, each of the Selling Parties is in compliance with the provisions of the JV Agreement. HOB hereby represents (but does not warrant) to the other parties hereto as follows:
View Source

Related to A JV AGREEMENT

  • Operating Agreement You have received and read a copy of the Company’s Operating Agreement (the “Operating Agreement”) and agree that your execution of this Subscription Agreement constitutes your consent to the Operating Agreement, and that upon acceptance of this Subscription Agreement by the Company, you will become a member of the Company as a holder of Class A Units. When this Subscription Agreement is countersigned by the Company, the Operating Agreement shall be binding upon acceptance of your subscription.

  • Cooperation Agreement At the Closing, PCC and Buyer shall, and PCC shall cause PCC Parent to, execute and deliver the Cooperation Agreement pursuant to which Buyer, PCC Parent and PCC shall provide each other certain information and other assistance in connection with the collection, administration and/or satisfaction of certain of the Retained Liabilities.

  • Governing Agreement The Assigned Transaction and the Confirmation shall form a part of, and be subject to, the ISDA Master Agreement dated as of September 29, 2006, as amended or supplemented from time to time (the "New Master Agreement"), between Assignee and Remaining Party. The Confirmation shall form a part of, and be subject to, the New Master Agreement.

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its Reliability Planning Process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Short-Term Reliability Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the STAR or Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Short-Term Reliability Process Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.