Framework agreement scope Sample Clauses

Framework agreement scope. This agreement provides you with access to Suppliers who can wholly manage your print requirements by providing a fully managed end to end print management service. You can further define your requirements as part of the call-off process, the agreement is fully flexible and you can choose to use one or more of the services offered. The agreement is designed to meet the needs of all complex print service requirements or where you require the support of a print management service, print needs are fully managed on your behalf.
AutoNDA by SimpleDocs
Framework agreement scope. 1. By the present Framework Agreement, the Contractor undertakes to provide services to the Cyprus Energy Regulatory Authority (CERA) for the harmonization of the legislative framework and provision of regulatory (financial, legal, technical) support for the development of cross-border electrical interconnection in the Republic of Cyprus as described in Annex II of the tender procedure documents, and in accordance with the terms and conditions laid down in the Framework Agreement and outlined in section 3.1 of Part A of the Tender Procedure Documents.

Related to Framework agreement scope

  • 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.

  • 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.

  • FRAMEWORK AGREEMENT MANAGEMENT The Parties shall manage this Framework Agreement in accordance with Schedule 14 (Framework Management).

  • TERM OF FRAMEWORK AGREEMENT The Framework Agreement shall take effect on the Commencement Date and (unless it is otherwise terminated in accordance with the terms of this Framework Agreement or it is otherwise lawfully terminated) shall terminate at the end of the Term.

  • SCOPE OF FRAMEWORK AGREEMENT 3.1 This Framework Agreement governs the relationship between the Authority and the Supplier in respect of the provision of the Services by the Supplier to the Authority and to Other Contracting Bodies.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • Vendor Agreement 230105 Vendor Agreement pdf The Vendor Agreement must be downloaded from the “Attachments” section of the IonWave eBid System, reviewed, Vendor Name placed in the line provided at the top, and uploaded to this location. If Vendor has proposed deviations to the Vendor Agreement, Vendor may assert so in the Attribute Questions and those shall be addressed during evaluation.

  • 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.

  • 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.

  • Client Agreement 2.1. The Company may unilaterally change any terms of this Client Agreement for any of the following reasons:

Time is Money Join Law Insider Premium to draft better contracts faster.