Project Implementation Units Sample Clauses

Project Implementation Units. (a) The Recipient shall cause SAMSA as per the Tripartite Agreement, to maintain until the completion of the Project, the regional project management unit which will be hosted by SAMSA, with terms of reference, qualifications and expertise satisfactory to the Bank.
Sample 1Sample 2
AutoNDA by SimpleDocs
Project Implementation Units. 4. The Recipient shall for the purposes of the Project:
Sample 1Sample 2
Project Implementation Units. 6. Within one month of the Effective Date, each PCB shall establish a PIU in its SME Department. Each PIU shall be responsible for coordinating with the relevant PCB units to ensure that (a) all information and reporting requirements related to PCBs and subloans are met; and (b) all necessary accounts and related financial statements as well as all disbursement records are submitted to the PSC.
Sample 1Sample 2
Project Implementation Units. 6. The PIUs, established in each Project District, shall be responsible for
Sample 1
Project Implementation Units. 5. The Borrower shall ensure that in each Pourashava, a PIU shall be established within three months of the Effective Date. The PIU shall be headed by the Pourashava Mayor, who shall be assisted by the Chief Executive Officer. Each PIU shall comprise three sections: (i) the infrastructure improvement section, headed by the Executive Engineer or the Assistant Engineer, as the case may be; (ii) the urban governance improvement section, headed by the Secretary of the Pourashava; and (iii) the environmental, sanitation, and slum improvement section, headed by the Health Officer. The PIU shall be located within the Pourashava office and be responsible for (i) preparing the detailed annual work plan for the respective Pourashava; (ii) implementing the governance improvement activities specified in the UGIAP, including the preparation and implementation of the PDP, GAP, and PRAP; (iii) implementing physical works, including the preparation of bid documents as well as procurement and supervision of contractors; and (iv) preparing progress reports for submission to the PMO.
Sample 1
Project Implementation Units. (a) The Recipient shall, at all times during Project implementation, maintain two Project Implementation Units ("PIUs") each with distinct responsibility for implementing the Project: (i) the UPNNC; and (ii) the UCP.
Sample 1
Project Implementation Units. 7. The Borrower shall cause each Project Executing Agency to ensure that the PIUs implement the Subprojects and carry out necessary coordination with the concerned departments in the State to ensure the smooth implementation of the Subprojects.
Sample 1
AutoNDA by SimpleDocs
Project Implementation Units. A D-PIU, headed by the Deputy Director General of DHE as Project Manager, shall be established to implement and supervise Project activities at the central level. D-PIU shall, among other things, be responsible for (i) consolidating Project reporting; and (ii) reviewing withdrawal applications for endorsement by MOE's Department of Finance. Various departments and institutions of MOE, as part of the D-PIU shall be responsible for activities that fall within their area of responsibility. PIUs shall also be established in NUOL, CU and SU, headed by the respective university's Vice-President as Project Manager, to coordinate with D-PIU and concerned provincial authorities in implementing and supervising the Project, including procurement activities, monitoring, and reporting.
Sample 1

Related to Project Implementation Units

  • Project Implementation 2. The Borrower shall:

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

  • Project Completion The Project and the Work are complete.

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

  • Information Systems Acquisition Development and Maintenance Security of System Files. To protect City Information Processing Systems and system files containing information, Service Provider will ensure that access to source code is restricted to authorized users whose specific job function necessitates such access.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

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

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • Project Overview Project Title [Drafting note: ARENA to complete. Insert full long name in accordance with ARENA’s naming convention] i.e. [GMS Number] [Powerworks, voltage control on the Pacific Islands Study] [GMS Number] [study/ project/ fellowship/ scholarship/ R&D Project] Contract Number [Drafting note: ARENA to complete – to be obtained from ARENA’s GMS] Recipient [Drafting note: Recipient to insert full legal name and ABN] Guidelines and policies Advancing Renewables Program – Program Guidelines, 2020 (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/XXXXX_XXX_Xxxxxxxxxx_XX_Xxxxxx_Xxxxx_XXXXX.xxx) ARENA Variation Policy (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxxx-xxxxxxxxx-xxxxxxxxx-xxxxxx.xxx) ARENA Report Writing Guidelines (xxxxx://xxxxx.xxx.xx/xxxxxx/0000/00/xxxxx-xxxxxx-xxxxxxx-xxxxxxxxxx.xxx)

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