Single Project Implementation Units (SPIU) Sample Clauses

Single Project Implementation Units (SPIU). The SPIU will be responsible for overall Project implementation in consultation with other relevant national agencies and ministries to ensure consistency with national policies. The SPIU established at national level will be composed of Project staff either seconded or recruited, and will be headed by the SPIU Coordinator. The SPIU will be accountable to the RAB Director General who will be the executive level head responsible for the strategic direction of the Project. The SPIU will be responsible for Project coordination and management of fiduciary issues in conformity with the standards and requirements agreed upon between Borrower and IFAD. The SPIU coordinator in place will also oversee and coordinate KIIWP activities that will be implemented at both the central and district level. In addition to the existing SPIU staff performing cross-cutting functions of finance/accounting, monitoring and evaluation (M&E), procurement and administration, KIIWP staff will be recruited to support its implementation. The proposed KIIWP staff positions include: a Project Manager, an accountant, an M&E officer in charge also of gender and youth, an irrigation specialist, an electromechanical engineer, a civil engineer, an environmental and climate specialist, a safeguards compliance specialist, and a procurement officer.
Sample 1
AutoNDA by SimpleDocs

Related to Single Project Implementation Units (SPIU)

  • Project Implementation 2. The Borrower shall:

  • Project Completion Date It is agreed between the Parties that the Project Completion Date is <END DATE, YEAR>. If the Project is not completed by such date then, subject to an amendment agreed to between the Parties, Alberta Innovates may elect to terminate this Investment Agreement. In such event, Alberta Innovates will notify the Applicant of its decision to terminate as soon as reasonably practical and shall advise the Applicant of the effective date of termination. Alberta Innovates will have no liability or obligation to reimburse the Applicant for any Project Costs incurred after the effective date of termination and may require the Applicant to return any portions of the Investment which were spent on Ineligible Expenses. Additionally, any portion of the Investment not used and accounted for in accordance with this Agreement as of the Project Completion Date or earlier termination is repayable by the Applicant to AI at AI’s request.

  • Project Completion Part 1 – Material Completion

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

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • PROJECT CONDITIONS A. The Grantee agrees to the following Project Conditions:

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

  • Project Construction Budget The project construction cost allowance specifically stated in writing as the ‘revised’ or ‘current’ ‘Project Construction Budget’ by the Trustees at each applicable phase of plan development.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Project Changes 1.8.1. All changes shall be administered per the UGC.

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