Programme Management Unit Sample Clauses

Programme Management Unit. In order to support, monitor, and report on all aspects of Project implementation, including the procurement of goods, works and services for the Project, the Borrower shall, unless otherwise agreed with the Bank, establish and at all times during execution of the Project operate a PMU at the Ministry of Agriculture, Regional Development and Environment with adequate resources and suitably qualified personnel as referred to in Article 1.04, under terms of reference acceptable to the Bank. The Borrower shall procure that the Ministry of Agriculture, Regional Development and Environment entrusts the PMU with the overall co-ordination of the Project and the responsibility for the implementation of the Project. The PMU shall act as the Bank’s counterpart in all technical, financial, investment selection, disbursement facilitation, accounting/auditing, reporting, procurement and administration matters. The Borrower, acting through the Ministry of Agriculture, Regional Development and Environment undertakes to ensure that the Bank can, at the sole discretion of the Bank, directly access any international consultant working on the Project at any time.
AutoNDA by SimpleDocs
Programme Management Unit. The day-to-day implementation and coordination of the programme will be undertaken by a dedicated Programme Management Unit (PMU) headed by a National Programme Coordinator (NPC) reporting to the Secretary for Local Government and Rural Development. The PMU will be granted authority to undertake all financial and procurement management activities, lead and supervise programme implementation and provide specialist technical inputs. The recruitment and contract renewal of key PMU staff will require prior consent from IFAD. Key PMU staff includes the NPC, Finance Manager, and Procurement Manager.
Programme Management Unit. The implementation of the Programme is delegated by the lead agency to a Federal Programme Coordination Unit (FPCU). The FPCU will be co-financed by IFAD, AFDB and IsDB and include the following key personnel: a National Programme Coordinator, a Financial Controller, an Accountant in charge of IFAD funding, a Procurement Officer in charge of IFAD funded procurement, a Monitoring and Evaluation Officer, an Infrastructure Engineer, an Environmental and Climate Change Safeguards Officer, a Knowledge Management and Communication Officer, an Agricultural Productivity Officer, Social Safeguards/Gender Officer, and a Rural Institutions Development Officer. The FPCU will establish Participating States Implementation Units (PSIUs) in each target state. The PSIU will be co-financed by IFAD, AFDB and IsDB and will include the following Key Personnel: a State Programme Coordinator, a State Financial Controller, a State Accountant in charge of IFAD funding, a State Procurement Officer in charge of IFAD funded procurement, a State Monitoring and Evaluation Officer, a State Infrastructure Engineer, a State Environmental and Climate Change safeguards officer, a State Development Communication Officer, an Agricultural Productivity Officer, a Social Safeguards/Gender Officer, and a Rural Institutions Development Officer. Staff of the FMCU and PSIU will be appointed/seconded from the Federal and State Government following established Government procedures acceptable by IFAD and IFAD’s No- Objection. The PPP officer will be recruited competitively in the open market.
Programme Management Unit. The National Programme Coordination Unit (NPCU), reporting to the MoAI, will be responsible for: (a) managing the procurement of goods, works and services for the implementation of all programme activities; (b) developing the AWPB; (c) undertaking the M&E and KMC of programme activities; and (d) reporting on implementation progress and results to IFAD and MoAI. The NPCU shall comprise of competitively recruited staff. A lean State Programme Coordination Unit (SPCU) will be responsible for the day-to-day implementation of the programme at the FMS level. Reporting administratively to the Minister of the MoAI and technically to the NPCU.
Programme Management Unit. Programme coordination, supervision and monitoring will be undertaken by a small Programme Management Unit (PMU) located within the Lead Programme Agency in Baku. The PMU will be resourced from the existing IPMU (Programme Director, Financial Manager, Procurement Officer, M&E Officer, an accountant, Community Development Specialist, Administrative Manager/Coordinator with International Organisations, Office Manager). Additional staff members shall be recruited on competitive basis as needed. The appointment and removal of these key staff members shall be subject to the non-objection of the Fund.
Programme Management Unit. (PMU). The PMU, located at Kosti or any other place within the Programme Area, will report to the PSC and the federal government. It will act as the technical secretariat of the Programme. The PMU will comprise: (i) Programme Director; (ii) Senior Livestock Business Development Manager (SLBDM), responsible for Component 1 and overall field implementation; (iii) Natural Resources & Adaptation Manager (NRAM), responsible for Component 2; (iv) Group & Enterprise Development Manager (GEDM), responsible for Component 3; (v) Financial Controller (FC); (vi) a Senior Accountant; (vii) two Knowledge Management/M&E Officers (East and West, KM/M&Es); (viii) Logistics/Procurement Officer; (ix) Administration Officer; and

Related to Programme Management Unit

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity 1.1.02 Identify at least one individual to act as the program contact in the following areas: 1. Immunization Program Manager;

  • PERFORMANCE MANAGEMENT SYSTEM 6.1 The Performance Plan (Annexure A) to this Agreement sets out – 6.1.1 The standards and procedures for evaluating the Employee’s performance; and 6.1.2 The intervals for the evaluation of the Employee’s performance. 6.2 Despite the establishment of agreed intervals for evaluation, the Employer may in addition review the Employee’s performance at any stage while the contract of employment remains in force; 6.3 Personal growth and development needs identified during any performance review discussion must be documented in a Personal Development Plan as well as the actions agreed to and implementation must take place within set time frames; 6.4 The Employee’s performance will be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan (IDP) as described in 6.6 – 6.12 below; 6.5 The Employee will submit quarterly performance reports (SDBIP) and a comprehensive annual performance report at least one week prior to the performance assessment meetings to the Evaluation Panel Chairperson for distribution to the panel members for preparation purposes; 6.6 Assessment of the achievement of results as outlined in the performance plan: 6.6.1 Each KPI or group of KPIs shall be assessed according to the extent to which the specified standards or performance targets have been met and with due regard to ad-hoc tasks that had to be performed under the KPI, and the score of the employer will be given to and explained to the Employee during the assessment interview. 6.6.2 A rating on the five-point scale shall be provided for each KPI or group of KPIs which will then be multiplied by the weighting to calculate the final score; 6.6.3 The Employee will submit his self-evaluation to the Employer prior to the formal assessment; 6.6.4 In the instance where the employee could not perform due to reasons outside the control of the employer and employee, the KPI will not be considered during the evaluation. The employee should provide sufficient evidence in such instances; and 6.6.5 An overall score will be calculated based on the total of the individual scores calculated above.

  • SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

  • Performance Management 17.1 The Contractor will appoint a suitable Account Manager to liaise with the Authority’s Strategic Contract Manager. Any/all changes to the terms and conditions of the Agreement will be agreed in writing between the Authority’s Strategic Contract Manager and the Contractor’s appointed representative. 17.2 The Contractor will ensure that there will be dedicated resources to enable the smooth running of the Framework Agreement and a clear plan of contacts at various levels within the Contractor's organisation. Framework Public Bodies may look to migrate to this Framework Agreement as and when their current contractual arrangements expire. The Contractor will where necessary assign additional personnel to this Framework Agreement to ensure agreed service levels are maintained and to ensure a consistent level of service is delivered to all Framework Public Bodies. 17.3 In addition to annual meetings with the Authority's Strategic Contract Manager, the Contractor is expected to develop relationships with nominated individuals within each of the Framework Public Bodies to ensure that the level of service provided on a local basis is satisfactory. Where specific problems are identified locally, the Contractor will attempt to resolve such problems with the nominated individual within that organisation. The Authority's Strategic Contract Manager will liaise (or meet as appropriate) regularly with the Framework Public Bodies' Contract Manager, and where common problems are identified, it will be the responsibility of the Contractor to liaise with the Authority's Strategic Contract Manager to agree a satisfactory course of action. Where the Contractor becomes aware of a trend that would have a negative effect on one or more of the Framework Public Bodies, they should immediately notify the Authority's Strategic Contract Manager to discuss corrective action. 17.4 Regular meetings, frequency to be advised by Framework Public Body, will be held between the Framework Public Bodies' Contract Manager and the Contractor's representative to review the performance of their Call-Off Contract(s) under this Framework Agreement against the agreed service levels as measured through Key Performance Indicators (KPIs). Reports will be provided by the Contractor to the Framework Public Bodies' Contract Manager at least 14 days prior to the these meetings. 17.5 Performance review meetings will also be held annually, between the Authority's Strategic Contract Manager and the Contractor's representative to review the performance of the Framework Agreement against the agreed service levels as measured through Key Performance Indicators. A summary of the quarterly reports will be provided by the Contractor at least 14 days prior to these meetings. 17.6 The Authority will gather the outputs from contract management to review under the areas detailed in the table below. Provision of management reports 90% to be submitted within 10 working days of the month end Report any incident affecting the delivery of the Service(s) to the Framework Public Body 100% to be reported in writing to FPB within 24 hours of the incident being reported by telephone/email Prompt payment of sub-contractors and/or consortia members (if applicable). Maximum of 30 from receipt of payment from Framework Public Bodies, 10 days target 100% within 30 days

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Change Management BellSouth provides a collaborative process for change management of the electronic interfaces through the Change Control Process (CCP). Guidelines for this process are set forth in the CCP document as amended from time to time during this Agreement. The CCP document may be accessed via the Internet at xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx.

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Workload Management 11.1 The parties to this Agreement acknowledge that employees and management have a responsibility to maintain a balanced workload and recognise the adverse affects that excessive workloads may have on employee/s and the quality of resident/client care. 11.2 To ensure that employee concerns involving excessive workloads are effectively dealt with by Management the following procedures should be applied: (a) Step 1: In the first instance, employee/s should discuss the issue with their immediate supervisor and, where appropriate, explore solutions. (b) Step 2: If a solution cannot be identified and implemented, the matter should be referred to an appropriate senior manager for further discussion. (c) Step 3: If a solution still cannot be identified and implemented, the matter should be referred to the Facility Manager for further discussion. (d) Step 4: The outcome of the discussions at each level and any proposed solutions should be recorded in writing and fed back to the effected employees. 11.3 Workload management must be an agenda item at staff meetings on at least a quarterly basis. Items in relation to workloads must be recorded in the minutes of the staff meeting, as well as actions to be taken to resolve the workloads issue/s. Resolution of workload issues should be based on the following criteria including but not limited to: (a) Clinical assessment of residents’ needs; (b) The demand of the environment such as facility layout; (c) Statutory obligation, (including, but not limited to, work health and safety legislation); (d) The requirements of nurse regulatory legislation; (e) Reasonable workloads (such as roster arrangements); (f) Accreditation standards; and (g) Budgetary considerations. 11.4 If the issue is still unresolved, the employee/s may advance the matter through Clause 9 Dispute Resolution Procedure. Arbitration of workload management issues may only occur by agreement of the employer and the employee representative, which may include the union/s.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!