We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.
For more information visit our privacy policy.Framework This Agreement establishes a framework that will enable Red Hat to provide Software and Services to Client. “Software” means Red Hat Enterprise Linux, JBoss Enterprise Middleware and other software programs branded by Red Hat, its Affiliates and/or third parties including all modifications, additions or further enhancements delivered by Red Hat. The specific services (the “Services”) and/or Software that Red Hat will provide to Client will be described in an Order Form, signed by the parties or otherwise accepted by Red Hat, which may consist of (a) one or more mutually agreed order forms, statements of work, work orders or similar transaction documents, or (b) an order placed by Client through Red Hat's online store accessible from a Red Hat website. The parties agree that the terms of this Agreement will govern all purchases and use by Client of Software and Services unless otherwise agreed by the parties in writing.
Legal Framework 1. This programme agreement shall be read in conjunction with the following documents which, together with this programme agreement, constitute the legal framework of the EEA Financial Mechanism 2014-2021: (a) Protocol 38c to the EEA Agreement on the EEA Financial Mechanism 2014-2021; (b) the Regulation on the implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “Regulation”) issued by the Donor States in accordance with Article 10(5) of Protocol 38c; (c) the Memorandum of Understanding on the Implementation of the EEA Financial Mechanism 2014-2021 (hereinafter referred to as the “MoU”), entered into between the Donor States and the Beneficiary State; and (d) any guidelines adopted by the FMC in accordance with the Regulation. 2. In case of an inconsistency between this programme agreement and the Regulation, the Regulation shall prevail. 3. The legal framework is binding for the Parties. An act or omission by a Party to this programme agreement that is incompatible with the legal framework constitutes a breach of this programme agreement by that Party.
NIST Cybersecurity Framework The U.S. Department of Commerce National Institute for Standards and Technology Framework for Improving Critical Infrastructure Cybersecurity Version 1.1.
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.
Homework In addition to regular attendance at scheduled classes, each student will be required to devote additional time each week outside the classroom to study and work on assignments.
Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.
Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA. (b) If the HSP is not subject to the procurement provisions of the BPSAA, the HSP will have a procurement policy in place that requires the acquisition of supplies, equipment or services valued at over $25,000 through a competitive process that ensures the best value for funds expended. If the HSP acquires supplies, equipment or services with the Funding it will do so through a process that is consistent with this policy.
Project Implementation The Borrower shall:
Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.
Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.