BACKGROUND Framework Agreement Sample Clauses

BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of a range of Internal and External Building Works services which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of Heating and Water Hygiene which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1
BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of Lifts, which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1
BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of a range of Asbestos Removals Services, which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1
BACKGROUND Framework Agreement. 1.1 TPPL, as the agent for the Consortium has tendered and selected a framework of Suppliers to provide a range of minibuses, accessible welfare buses, passenger transport buses, coaches and conversion works which Members of TPPL and other Contracting Authorities can call upon as required.
Sample 1
BACKGROUND Framework Agreement. 1.1 The Authority is setting up a framework of consultants for the carrying out of various asset management services to include programme and project management for the provision of investment appraisal, strategic support and construction-related services which the Authority and Authorised Users can call upon on an ad hoc basis as required.
Sample 1
BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of a range of Fire Safety Services, which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1
AutoNDA by SimpleDocs
BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of a range of Pest Control, which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1
BACKGROUND Framework Agreement. 1.1 The Client is setting up a framework of service providers for the provision of a range of Waking Watch Services, which the Client and Authorised Entities can call upon on an ad hoc basis as required.
Sample 1

Related to BACKGROUND Framework Agreement

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

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

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

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

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

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

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A, Statement of Work.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!