Cost Allocation Recommendations for Expanded Scope Project Sample Clauses

Cost Allocation Recommendations for Expanded Scope Project. An Expanded Scope Project may be a combination of one or more EOPs, Requested Service Projects, Capacity Increase Projects, and Single System Projects. The provisions governing ColumbiaGrid cost allocation recommendations for such types of Projects will be applied to the various portions of any Expanded Scope Project as applicable.
AutoNDA by SimpleDocs

Related to Cost Allocation Recommendations for Expanded Scope Project

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • Business Plan The Lenders shall have received a satisfactory detailed business plan of the Borrowers for fiscal years 1996 - 2002 and a satisfactory written analysis of the business and prospects of the Borrowers for the period from the Closing Date through the final maturity of the Term Loans.

  • Work Plan Coordinate a work plan including a list of the proposed meetings and coordination activities, and related tasks to be performed, a schedule and an estimate. The work plan must satisfy the requirements of the project and must be approved by the State prior to commencing work.

  • Annual Work Plan and Budget 1. The Recipient shall, not later than November 30th of each year, prepare and furnish to the Association an annual work plan and budget (“Annual Work Plan and Budget”) for the Project for the subsequent year, said Annual Work Plan and Budget of such scope and detail as the Association shall have reasonably requested.

  • Annual Work Plans (a) The Recipient shall prepare in accordance with guidelines acceptable to the Association and furnish to the Association not later than March 31 in each calendar year, a proposed annual work plan and budget for the Project for the following fiscal year of the Recipient, of such scope and in such detail as the Association shall reasonably request.

  • Annual Work Plans and Budgets The Recipient shall furnish to the Association as soon as available, but in any case not later than September 1 of each year, the annual work plan and budget for the Project for each subsequent year of Project implementation, of such scope and detail as the Association shall have reasonably requested, except for the annual work plan and budget for the Project for the first year of Project implementation, which shall be furnished no later than one (1) month after the Effective Date.

  • For Lump Sum Change Order The payment and extension of time (if any) provided by this Change Order constitutes compensation in full to the Contractor and its Subcontractors and Suppliers for all costs and markups directly and indirectly attributable to the Change Order herein, for all delays related thereto and for performance of changes within the time stated.

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

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

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