Correct procedure for revision program

I agree with you.

Not only the actual dates have to be matched, you should look at the S-curve & match the overall & individual curves so that it matches the actuals. I.e Planned progress as of date for the baseline is equal to the actual progress of the updated ones.

Cheers

Dattatreya

Argument: “it need to revise on previous revision with new ES & EF dates matching the actual update dates”

Scenario : Project of 2 year duration. Schedule of 7000 activities. Schedule to be revised (1st revision) after elapse of 1 year of project duration. 4000 activities having % complete more than 0.

How you are going to do it,

1: Activity A1 assign relations give duration and schedule it (With start date as data date since revision with 0% progress). ES & EF of this activity matches with the actuals. Good.

2: Activity A2 assign relations give duration and schedule it. ES & EF of this activity matches with the actuals. Very Good.

3: Activity A3 assign relations give duration and schedule it. ES & EF of this activity also matches with the actuals. Great.

4: Activity A4 assign relations give duration and schedule it. ES & EF of this activity also matches with the actuals. OOPs but ES & EF of A2 do not match with its actual.

Change the relations and duration of A2 and run the schedule. Eureka….ES & EF of A2 matches with the actuals. Let us proceed …but wait…. now ES & EF of A1 is not matching with its actuals.

So modify the relation of A1 ….no modify the relation and duration of A2……lets check…..

Result: After 2 years project completed and handed over….site demobilized…..but the great planner still revising the program to match ES and EF of all activities with its actual.

Sreekanth

I agree with your friend,when revising a programme you should put the actuals & reschedule it and then use that same data date in revising and/or resequencing your programme. From my point of view, you cannot provide a comprehensive forecast without considering what had happened...

There are very few instances of Projects being rescheduled in their entire life cycle.
When the gap between actual & planned is too high, you go for rescheduling with the same end date or showing a delay agreed by the Client. In this scenario you have to undertake an exercise of rescheduling. Need not be the base plan. you can freeze the current plan & categorise it as a new baseline. & then reschedule realistically.
Average O&G Projects do not undergo so many revisions in its entire lifecycle, i mean; individual phases, FEED/EPC etc. If a Project phase has too many revisions in plan, then its fits into the scenario of mismanaged projects.

Cheers
Dattatreya