Programme Agreement. The parties agree to amend clause 6.2.1 of Programme Agreement, which amendments are, for ease of reference reflected hereunder by underlined text for insertions and strikethrough text for deletions, as follows –
Programme Agreement Sample Clauses
Related to Programme Agreement
Client Agreement 2.1. The Company may unilaterally change any terms of this Client Agreement for any of the following reasons:
Framework Agreement 4.1.2.1 The Parties shall enter into a Framework Agreement within 28 days after the Contractor receives the Letter of Acceptance, unless the Particular Conditions establish otherwise. The Framework Agreement shall be based upon FORM No. 3 – FRAMEWORK AGREEMENT annexed to the Particular Conditions. The costs of stamp duties and similar charges (if any) imposed by law in connection with entry into the Framework Agreement shall be borne by the Procuring Entity.
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.
One Agreement This Agreement and any related security or other agreements required by this Agreement, collectively:
Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.
Arrangement Agreement This Plan of Arrangement is made pursuant to, and is subject to the provisions of, the Arrangement Agreement, except in respect of the sequence of the steps comprising the Arrangement, which shall occur in the order set forth herein.
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.
Support Agreement CFSC will not terminate, or make any amendment or modification to, the Support Agreement which, in the determination of the Agent, adversely affects the Banks’ interests pursuant to this Agreement, without giving the Agent and the Banks at least thirty (30) days prior written notice and obtaining the written consent of the Majority Banks.
Client Agreements Supplier will have a direct contract with, or provide its standard Product or Service terms directly to, Client, which will be enforceable solely between Client and Supplier, for all terms related to Client’s receipt and use of Products and Services (each a “Client Agreement”), other than the payment, risk of loss, and delivery terms that are contracted directly with Accenture.
Pharmacovigilance Agreement Within [***] after the Effective Date, BMS and the Company (under the guidance of their respective Pharmacovigilance Departments, or equivalent thereof) shall define and finalize the responsibilities the Parties shall employ to protect patients and promote their well-being in connection with the use of the Licensed Compound(s) until such time that all pharmacovigilance responsibilities have transferred from BMS to Company. These responsibilities shall include mutually acceptable guidelines and procedures for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of adverse event reports, pregnancy reports, and any other information concerning the safety of any Licensed Compound(s). Such guidelines and procedures shall be in accordance with, and enable the Parties and their Affiliates to fulfill, local and international regulatory reporting obligations to government authorities. Furthermore, such agreed procedures shall be consistent with relevant International Council for Harmonization (ICH) guidelines, except where said guidelines may conflict with existing local regulatory safety reporting requirements, in which case local reporting requirements shall prevail. Until such guidelines and procedures are set forth in a written agreement between the Parties (hereafter referred to as the “Pharmacovigilance Agreement”), the Party responsible for pharmacovigilance prior to execution of this Agreement shall have sole Pharmacovigilance responsibility for the Licensed Compound(s) subject to all applicable regulations and guidelines. In the event that this Agreement is terminated, the Parties agree to implement the necessary procedures and practices to ensure that any outstanding pharmacovigilance reporting obligations are fulfilled. Certain information marked as [***] has been excluded from this exhibit because it is both (i) not material and (ii) would be competitively harmful if publicly disclosed.
