LawGrids logoLAWGRIDS.ORG

Regulation 19, TAMIL NADU INFRASTRUCTURE DEVELOPMENT BOARD REGULATIONS 2013: Project Management Plan

TAMIL NADU INFRASTRUCTURE DEVELOPMENT BOARD REGULATIONS 2013 - Regulation 19

Text of regulation 19

Project Management Plan

19. Project Management Plan—(1) The Public agency or Sponsoring Agency shall cause to be prepared by the Project Management Facility or the Project Manager, following the principles contained in Appendix V, a Project Management Plan at a stage no later the signing of the Contract or the Concession Agreement, which shall: (a) define the processes that enable all parties to meet their obligations; (b) monitor performance by the Parties of their respective obligations under the contract or the Concession Agreement; (c) manage differences through proactive relationship management; (d) manage unanticipated developments and mitigating risks through efficient risk management; and (e) resolve disputes in an expeditious manner, with minimal impact on service delivery. (2) The Project Management Plan shall also serve as a repository of basic project related documentation and shall include: (a) The Contract or Concession Agreement and its schedules; (b) All financing agreements as well as financial models, where applicable; (c) The names, roles and contact details of key individuals of both parties; (d) Implementation plan during development, construction, operations and exit phases; (e) Performance management plan; (f) Risk management plan; (g) Financial and contract administration plan; (h) Relationship management and Contingency plan; and (i) Contract Termination and Handover plan. 20. Treatment of variation (1) Where a Contract or a Concession Agreement includes provisions for amendments consequent on variations, it shall be the responsibility of the Project Manager or PMF to: (a) Ensure party proposing an amendment consequent upon variation justifies it with adequate evidence and related costs; (b) Validate that the proposed amendments consequent upon variation are in accordance with procedures laid down in the Contract or Concession Agreement; 11 (c) Maintain a register of all amendments consequent upon variation throughout the project lifecycle; (d) Promote effective communication to have a shared understanding of implications of any amendments consequent upon variation between contracting parties; and (e) Ensure that timing for all amendments consequent upon variation are mutually agreed to, and take steps to ensure that variation management process outlined in the contract is followed by all contracting parties. (2) The Sponsoring Agency shall obtain approval for all amendments to terms of the Concession Agreement from the Board. 21. Exit strategy for continued service delivery after exit (1) The Public Agency or Sponsoring Agency shall ensure that the Contract or Concession Agreement provides for a hand back and exit strategy for the Project. (2) Such an exit strategy shall include: (a) Review of options to ensure service continuity; (b) Testing and valuation of assets; (c) Resource allocation for implementing the exit strategy; and (d) Obligation of the parties in relation to the exit strategy. (3) The Project Management Facility shall be responsible for implementation of exit strategy at the end of contract term. (4) After the exit of the Private Sector Participant, the Sponsoring Agency may decide to continue the delivery of the service through a fresh operations and maintenance contract. ***** 12

Previous and next

All provisions of TAMIL NADU INFRASTRUCTURE DEVELOPMENT BOARD REGULATIONS 2013

Questions people ask

Is regulation 19 of TAMIL NADU INFRASTRUCTURE DEVELOPMENT BOARD REGULATIONS 2013 still in force?

No repeal of TAMIL NADU INFRASTRUCTURE DEVELOPMENT BOARD REGULATIONS 2013 is recorded.