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.
Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline: • •
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:
Project Timeline The Project Timeline establishes a start and end date for each Phase of the Project. Developed during the Initiate & Plan Stage and revised as mutually agreed to, if needed, the timeline accounts for resource availability, business goals, size and complexity of the Project, and task duration requirements.
Timelines a) Timelines may be extended by mutual consent of the parties.
Metrics The DISTRICT and PARTNER will partake in monthly coordination meetings at mutually agreed upon times and dates to discuss the progress of the program Scope of Work. DISTRICT and PARTNER will also mutually establish criteria and process for ongoing program assessment/evaluation such as, but not limited to the DISTRICT’s assessment metrics and other state metrics [(Measures of Academic Progress – English, SBAC – 11th grade, Redesignation Rates, mutually developed rubric score/s, student attendance, and Social Emotional Learning (SEL) data)]. The DISTRICT and PARTNER will also engage in annual review of program content to ensure standards alignment that comply with DISTRICT approved coursework. The PARTNER will provide their impact data based upon these metrics.
STRATEGIC PLAN (1) Within ninety (90) days, the Board shall adopt, implement, and thereafter ensure Bank adherence to a written strategic plan for the Bank covering at least a three-year period. The strategic plan shall establish objectives for the Bank's overall risk profile, earnings performance, growth, balance sheet mix, off-balance sheet activities, liability structure, capital adequacy, reduction in the volume of nonperforming assets, product line development and market segments that the Bank intends to promote or develop, together with strategies to achieve those objectives and, at a minimum, include:
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.
Milestones Subject to the provisions of the SGIP, the Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement. A Party’s obligations under this provision may be extended by agreement. If a Party anticipates that it will be unable to meet a milestone for any reason other than a Force Majeure event, it shall immediately notify the other Parties of the reason(s) for not meeting the milestone and (1) propose the earliest reasonable alternate date by which it can attain this and future milestones, and (2) requesting appropriate amendments to Attachment 4. The Party affected by the failure to meet a milestone shall not unreasonably withhold agreement to such an amendment unless it will suffer significant uncompensated economic or operational harm from the delay, (1) attainment of the same milestone has previously been delayed, or (2) it has reason to believe that the delay in meeting the milestone is intentional or unwarranted notwithstanding the circumstances explained by the Party proposing the amendment.
Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least thirty (30) days written notice to the SLDC and GUVNL, of the date on which it intends to synchronize the Power Project to the Grid System.