Disclosure of Contractor Parties Litigation The Contractor shall require that all Contractor Parties, as appropriate, disclose to the Contractor, to the best of their knowledge, any Claims involving the Contractor Parties that might reasonably be expected to materially adversely affect their businesses, operations, assets, properties, financial stability, business prospects or ability to Perform fully under the Contract, no later than ten (10) Days after becoming aware or after they should have become aware of any such Claims. Disclosure shall be in writing.
Role of the Central Parties and Crown a) The central parties shall each have the following rights:
Parties and Purpose This agreement (the “Agreement”) is entered by and between certain portfolios and classes thereof, specified below and in Schedule C, of Franklin Xxxxxxxxx Variable Insurance Products Trust, an open-end management investment company organized as a statutory trust under Delaware law (the “Trust”), Franklin/Xxxxxxxxx Distributors, Inc., a California corporation which is the principal underwriter for the Trust (the “Underwriter,” and together with the Trust, “we” or “us”), the insurance company identified on Schedule A (together “you”) and your distributor, on your own behalf and on behalf of each segregated asset account maintained by you that is listed on Schedule B, as that schedule may be amended from time to time (“Account” or “Accounts”). The purpose of this Agreement is to entitle you, on behalf of the Accounts, to purchase the shares, and classes of shares, of portfolios of the Trust (“Portfolios”) that are identified on Schedule C, consistent with the terms of the prospectuses of the Portfolios, solely for the purpose of funding benefits of your variable life insurance policies or variable annuity contracts (“Contracts”) that are identified on Schedule D. This Agreement does not authorize any other purchases or redemptions of shares of the Trust.
Parties Bound This Agreement shall be binding upon:
PARTIES TO AGREEMENT This agreement is between the University of Central Florida (UCF) on behalf of its Board of Trustees, for the benefit of the University of Central Florida Department of Housing and Residence Life (UCF DHRL), and any person seeking residence accommodations in any of the various UCF DHRL residences (the Student). If the Student is a minor, or suffers any incapacity affecting the Student’s legal ability to enter into a contract, the term the Student shall also include the Student’s parent or legal guardian. The Student may not designate another person to act as agent or representative of the Student with regard to this agreement (i.e., having a friend pick up or turn in keys). The Student remains personally responsible for all rights and obligations arising from or related to this agreement.
APPLICATION AND PARTIES BOUND 5.1 The parties bound by this General Agreement are listed in Schedule 5.
Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation 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 Generator Deactivation 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 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 Generator Deactivation 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.
PARTIES AND DATE This Agreement is made and entered into this 19th day of June, 2019 (“Effective Date”) by and between the City of Corona, a municipal corporation organized under the laws of the State of California with its principal place of business at 000 Xxxxx Xxxxxxxx Xxxxxx, Xxxxxx, Xxxxxxxxxx 00000 (“City”) and Xxxxx, a California Corporation with its principal place of business at 000 Xxxxx Xxxxxx, Xxxxxxxxx, XX 00000 (“Consultant”). City and Consultant are sometimes individually referred to as “Party” and collectively as “Parties” in this Agreement.
Compliance Between Individual Contract and Master Agreement An individual contract between the Board and an individual employee, heretofore or hereafter executed, shall be subject to and consistent with the terms and conditions of this Agreement. If an individual contract contains any language inconsistent with this Agreement, this Agreement during its duration shall be controlling.
RECOGNITION AND SCOPE 1.01 The Company agrees to recognize the Union as the sole collective bargaining agent for employees covered by this Agreement.
