Submission, Content and Fulfillment of Project Utilization Plan Sample Clauses

Submission, Content and Fulfillment of Project Utilization Plan a. Fourteen (14) calendar days before the solicitation of the first proposal for the Construction of part of the Homefield Project, which is issued by Developer after the execution of the Agreement, Developer will submit a Project Utilization Plan to the UG for review and approval. The Project Utilization Plan shall be on the form attached to this Exhibit as Attachment A or on another form provided or approved by the UG. This Project Utilization Plan shall set forth, to the best of Developer's knowledge: all categories of work that will be covered within solicitations that Developer or its Contractors intend to issue for all Construction and Professional Services providers necessary for Construction of the Homefield Project; an estimate of the dollar value of all work covered by these solicitations; an estimate of the dollar value of work within each identified work category; the dollar value of the work for each identified work category that is projected to be performed by LBEs, MBEs, and WBEs; any known potential joint ventures with LBEs, MBEs, and WBEs within each identified work category; an overall schedule of all work projected to be performed related to the design, development, and construction of the Homefield Project laid out sequentially over time; and the actions Developer intends to take, with respect to each of these solicitations, to make its Best Efforts to meet the goals set forth in Section III.A.1. of this Exhibit.
Sample 1
AutoNDA by SimpleDocs

Related to Submission, Content and Fulfillment of Project Utilization Plan

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • COMPLIANCE OF LAWS, NOTIFICATIONS ETC. BY PARTIES The Parties are entering into this Agreement for the allotment of a [Apartment/Plot] with the full knowledge of all laws, rules, regulations, notifications applicable to the project.

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

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

  • Specific Order Processes and Requirements 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Information Submission by Connecting Transmission Owner The initial information submission by Connecting Transmission Owner shall occur no later than one hundred eighty (180) Calendar Days prior to Trial Operation and shall include New York State Transmission System information necessary to allow the Developer to select equipment and meet any system protection and stability requirements, unless otherwise mutually agreed to by the Developer and Connecting Transmission Owner. On a monthly basis Connecting Transmission Owner shall provide Developer and NYISO a status report on the construction and installation of Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades, including, but not limited to, the following information: (1) progress to date; (2) a description of the activities since the last report; (3) a description of the action items for the next period; and (4) the delivery status of equipment ordered.

  • Service Order Process Requirements 53.5.1 CenturyLink will accept orders for As-Is Transfer of services from CenturyLink to CLEC where CenturyLink is the End User’s current local exchange carrier.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

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