7.14. Change Management

minute read

Process Owner | PMO

Change Management is all about management of a Change. Change here means a change in design, leading to a change of drawings and impacting time (in execution) and budget. Other changes like change of Contractor has been dealt with in Contracts management. Change of products midcourse of project execution will continue to be considered as a change of Design.

So, in a larger context, Design here means Design as in drawings, specifications of work, method statements, change of products & brands, the introduction of substitutions, change of forms and substances used in execution etc. When a piece of work is designed, drawing issued, Contract is awarded with detailing of works, technical specifications and method statement, it is construed that the work scope is defined and concluded. Any change in the above will be considered as Change from Change Management point of view.

Why does change arise? One of the most notable reason is a change introduced by the Developer to meet a client requirement emerging in the midway of project execution. The other notable reasons are;

So, is change bad? Any change will lead to some impact on the Schedule and cost. While some changes generate additional revenue by way of client attraction, some will save cost. It would undoubtedly impact the overall carrying cost and, in some instances, additional cost and delays in Schedule due to the introduction of changes. Strengthening of slabs to accommodate client requirements in Aquila Tower A or introducing slipform to accelerate the works in Centaurus are classic examples of Changes. So, change per se is not bad. What is terrible is deciding on change without properly analysing its impact on cost and budget.

Rule 7.19

(Rule 7.19)The following process shall be followed for evaluation and approval of Change management

  1. For Top-Down Change Management initiation, during the course of project execution, the management (Director-Operations) can initiate a request to the PMO for possible change detailing the requirement.
  2. Director PMO shall initiate an exercise of assessing the change concerning cost and time by using the QS team, TISS Team, CDD team and other functional teams as may be required.
  3. Similarly, for Bottom-Up Change Management initiation, the GM office for reasons mentioned in the earlier section can initiate a change request, to the Director (PMO) with complete background and reasoning. Kindly follow Project Manager Instruction Flowchart enclosed herewith as Appendix 22.
  4. The PMO shall oversee the above process and present their findings to Group CEO and Director Operations for approval.
  5. The assessment note shall fall apart from other shall include the following;
    1. Details of the change
    2. Reasons for the change
    3. Likely impact of the change on various aspects of project execution
    4. The overall impact on time/Schedule
    5. The overall impact on the budget
    6. How to implement the change – steps /actions/responsibilities
    7. Timeline of implementation of change
    8. The person responsible for implementations
    9. Confirmation that the stakeholders are aligned for the change and the timeline
    10. Final recommendations
  6. Once the same is approved with or without modifications, the same shall be formally communicated to all stakeholders by the Director PMO.
  7. Should the change require any amendment to contract, contract sum, scope, EOT, and EOC etc. suitable VO shall be issued by the GM.
  8. The Schedule shall be amended by introducing a delay report in ERP.
  9. The BOQs shall be amended suitably in the ERP.
  10. Should the change require the issue of new Contract or amendment to existing Contract, the same shall be done following the process of issue of new Contract or amendment to contract as the case may be
Back to Top


Scope of ERP

At this stage, not all part of the above process is in ERP except uploading all the reports and relevant documents in the repository of the ERP.

The approval of Variation order, amendment to contracts, amendment of Schedule and BOQ are part of the ERP process and kindly refer the respective sections [l] for the detailing of ERP process.

Appendix Links:

Appendix 22 PMO Flowchart

Rules:
Rule 7.19 Evaluation and approval of Change management