Summary of Actions and Implementation Timelines
Summary of Actions and Implementation Timelines Sample Clauses
Related to Summary of Actions and Implementation Timelines
Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.
Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).
PURPOSE AND IMPLEMENTATION This Umbrella Agreement (hereinafter referred to as the "Agreement" or "Umbrella Agreement") shall be for the purpose of collaborative research, development, and testing opportunities on various topics of mutual interest to enable advanced understanding of aeronautics, science, and space systems research and development and to provide workforce development in Science, Technology, Engineering, and Mathematics (STEM) while furthering NASA’s research and development goals. The Parties shall execute one (1) Annex Agreement (hereinafter referred to as the "Annex") concurrently with this Umbrella Agreement. The Parties may execute subsequent Annexes under this Umbrella Agreement consistent with the purpose and terms of this Umbrella Agreement. This Umbrella Agreement shall govern all Annexes executed hereunder; no Annex shall amend this Umbrella Agreement. Each Annex will detail the specific purpose of the proposed activity, responsibilities, schedule and milestones, and any personnel, property, or facilities to be utilized under the task. This Umbrella Agreement takes precedence over any Annexes. In the event of a conflict between the Umbrella Agreement and any Annex concerning the meaning of its provisions, and the rights, obligations and remedies of the Parties, the Umbrella Agreement is controlling.
Schedule for Completing Agreement Closeout Activities Provide All Draft and Final Written Products on a CD-ROM or USB memory stick, organized by the tasks in the Agreement. Products: • Final Meeting Agreement Summary (if applicable) • Schedule for Completing Agreement Closeout Activities • All Draft and Final Written Products
Project Implementation 2. The Borrower shall:
Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.
Implementation Specifications 1. The accounting shall contain the date, nature, and purpose of such disclosures, and the name and address of the person or agency to whom the disclosure is made.
Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
