Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.
AGREEMENT OF THE PARTIES The language used in this Agreement will be deemed to be the language chosen by the parties hereto to express their mutual intent, and no rule of strict construction will be applied against any party hereto. Neither Executive nor the Company shall be entitled to any presumption in connection with any determination made hereunder in connection with any arbitration, judicial or administrative proceeding relating to or arising under this Agreement.
Agreement Scope The scope of this Agreement is as prescribed in section 46 of the Act, setting out: • the health services to be provided to the State by the HSP, • the TTR in support of the health services to be provided, • the funding to be provided to the HSP for the provision of the health services, including the way in which the funding is to be provided, • the performance measures and operational targets for the provision of the health services by the HSP, • how the evaluation and review of results in relation to the performance measures and operational targets is to be carried out, • the performance data and other data to be provided by the HSP to the Department CEO, including how, and how often, the data is to be provided, and • any other matter the Department CEO considers relevant to the provision of the health services by the HSP. Where appropriate, reference will be made in this Agreement to Policy Frameworks issued by the Department CEO pursuant to Part 3, Division 2 of the Act.
Pharmacovigilance Agreement Subject to the terms of this Agreement, and at a date to be determined by the JDC, Facet and Trubion shall define and finalize the actions the Parties shall employ to protect patients and promote their well-being in a written agreement (hereinafter referred to as the “Pharmacovigilance Agreement”). 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 Collaboration Product. Such guidelines and procedures shall be in accordance with, and enable the Parties to fulfill, local and national regulatory reporting obligations to Governmental Authorities. Furthermore, such agreed procedures shall be consistent with relevant ICH guidelines, except where said guidelines may conflict with existing local regulatory safety reporting requirements, in which case local reporting requirements shall prevail. The Pharmacovigilance Agreement will provide for a worldwide safety database to be maintained by the Party appointed by the JDC. Each Party hereby agrees to comply with its respective obligations under such Pharmacovigilance Agreement (as the Parties may agree to modify it from time to time) and to cause its Affiliates and permitted sublicensees to comply with such obligations.
Elements Unsatisfactory Needs Improvement Proficient Exemplary IV-A-1. Reflective Practice Demonstrates limited reflection on practice and/or use of insights gained to improve practice. May reflect on the effectiveness of lessons/ units and interactions with students but not with colleagues and/or rarely uses insights to improve practice. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues, and uses insights gained to improve practice and student learning. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues; and uses and shares with colleagues, insights gained to improve practice and student learning. Is able to model this element.
Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement.
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.
Cooperative Agreement The provisions and pricing of this Contract will be extended to other California local or state governmental entities. Governmental entities wishing to use this Contract will be responsible for issuing their own purchase documents/price agreements, providing for their own acceptance, and making any subsequent payments. Contractor shall be required to include in any Contract entered into with another agency or entity that is entered into as an extension of this Contract a Contract clause that will hold harmless the County of Orange from all claims, demands, actions or causes of actions of every kind resulting directly or indirectly, arising out of, or in any way connected with the use of this contract. Failure to do so will be considered a material breach of this Contract and grounds for immediate Contract termination. The cooperative entities are responsible for obtaining all certificates of insurance and bonds required. The Contractor is responsible for providing each cooperative entity a copy of the Contract upon request by the cooperative entity. The County of Orange makes no guarantee of usage by other users of this Contract. The Contractor shall be required to maintain a list of the cooperative entities using this Contract. The list shall report dollar volumes spent annually and shall be provided on an annual basis to the County, at the County’s request.
Cooperation; Confidentiality Each party to this Agreement agrees to cooperate with the other party and with all appropriate governmental authorities having the requisite jurisdiction (including, but not limited to, the SEC) in connection with any investigation or inquiry relating to this Agreement or the Fund. Subject to the foregoing, the Sub-Adviser shall treat as confidential all information pertaining to the Fund and actions of the Fund, the Manager and the Sub-Adviser, and the Manager shall treat as confidential and use only in connection with the Series all information furnished to the Fund or the Manager by the Sub-Adviser, in connection with its duties under the Agreement except that the aforesaid information need not be treated as confidential if required to be disclosed under applicable law, if generally available to the public through means other than by disclosure by the Sub-Adviser or the Manager, or if available from a source other than the Manager, Sub-Adviser or the Fund.
Collaboration 31.1 If the Buyer has specified in the Order Form that it requires the Supplier to enter into a Collaboration Agreement, the Supplier must give the Buyer an executed Collaboration Agreement before the Start date. 31.2 In addition to any obligations under the Collaboration Agreement, the Supplier must: 31.2.1 work proactively and in good faith with each of the Buyer’s contractors 31.2.2 co-operate and share information with the Buyer’s contractors to enable the efficient operation of the Buyer’s ICT services and G-Cloud Services