Partnering GSA intends to encourage the foundation of a cohesive partnership between the OASIS Contractors, GSA OASIS personnel, and Federal agency customers to identify and achieve reciprocal goals, with effective and efficient customer-focused service, in accordance with the terms of the OASIS contract. Failure to attend meetings, maintain a Contractor OASIS webpage, or otherwise not comply with this section may result in activation of Dormant Status and/or result in a Contractor being Off-Ramped (See Sections H.16. and H.17.).
H.11.1. Meetings From time to time, the Government may require Contractor attendance, including the attendance of Contractor Key Personnel, at meetings at various locations. Meetings may be via web-casting, in-person at a government facility, a commercial conference center, or a mutually agreed- upon Contractor facility on a rotational basis, as determined by the Government. Follow-up meetings may be held periodically throughout the duration of XXXXX in order to assess performance against the goals and to reinforce partnering principles. GSA may require up to four OASIS Program Management Review (PMR) meetings per year. The goal of the PMR meetings are to provide a platform for OASIS Contractors, OASIS staff, and other agency representatives to communicate current issues, resolve potential problems, discuss business and marketing opportunities, review future and ongoing GSA and Government-wide initiatives, and address OASIS fundamentals. Any Contractor costs associated to PMR Meetings shall be at no direct cost to the Government.
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.
Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.
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.
4.1.2.2 The Framework Agreement establishes the terms and conditions that will govern the contract awarded during the term of the Framework Agreement. The Framework Agreement establishes for the procurement works by package as and when required, over the specified period of time. The Framework Agreement does not commit a Procuring Entity to procure, nor a Firm to supply. The Framework Agreement allows the Procuring Entity to call the Contractor to commence the works on a particular package in a specified location within the duration of the agreement.
4.1.2.3 This Framework Agreement does not guarantee the contractor of being called for a contract to start and no commitment is made with regard to possible number of packages to carry out.
4.1.2.4 This Framework Agreement does exclude the Procuring Entity from the right to procure the same Works from other firms.
4.1.2.5 This Framework Agreement does not stop the Procuring Entity from removing the contractor from the same Agreement.
4.1.2.6 FAs shall be established for a maximum period of three (3) years. The Procuring Entity may with the Consent of the Contractor extend this Agreement if the agreement period is less than three (3) years, if the initial engagement has been satisfactory.
4.1.2.7 Call-off Contracts; for work on a package to start, the Procuring Entity shall issue a notice of acceptance of a particular package requesting the contractor to furnish a Performance Security and to start the works thereafter, and providing the contractor with details of location where the works, are to be carried out. The call-off statement shall specify the objectives, tasks, deliverables, timeframes and price or price mechanism. The price for individual call-off contracts shall be based on the prices detailed in the Framework Agreement.
License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.
Valid Agreement This Agreement has been duly executed and delivered by the Purchaser and constitutes the legal, valid and binding obligation of the Purchaser, enforceable against the Purchaser in accordance with its terms, except (i) as limited by applicable bankruptcy, insolvency, reorganization, moratorium, and other laws of general application affecting enforcement of creditors’ rights generally, and (ii) as limited by laws relating to the availability of specific performance, injunctive relief, or other equitable remedies.
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
Supply Agreement Seller and Buyer, or their Affiliates, shall have executed the Supply 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.
Consortium Agreement agreement entered into by and between the Manager and the Contractors, pursuant to Annex X.
