Baseline is not resourced but the disruption or more accuately described as lost/unproductive hours is quantifiable as it is mainly the delay in issuing permits resulting in idle time.
Since your programme is currently unapproved I would start from the original programme before any progress updates and then tighten up the logic and removing all constraints - try to establish a clear critical path.
Make sure you do this BEFORE making a detailed study of the delay events.
Hint - this is done much quicker if you open up the .xer file in PowerProject - make the adjustments and save it back as an .xer for P6.
Then make a spreadsheet log of all your change orders and make a chronological list of dtate of event impact of the events - that is the earliest possible date that the affected task could have started.
Now create dummy tasks of each event in turn and impact it to the affected task - reschedule and note the effect.
Go on to the next delay event and repeat the process.
Make sure that all contractor's delay events are included in the matrix.
This will establish your entitlement to any EoT.
Disruption is a totally different matter and you will need a fully resourced baseline programme before you even think about it.
Check other threads on the topic anmd come back if you need more help.
Member for
14 years 6 monthsThanks Mike for the
Thanks Mike for the tips.
Baseline is not resourced but the disruption or more accuately described as lost/unproductive hours is quantifiable as it is mainly the delay in issuing permits resulting in idle time.
Will look up other threads on this.
Regards
Aidan
Member for
19 years 10 monthsHi Aidan In other words
Hi Aidan
In other words -situation normal.
Since your programme is currently unapproved I would start from the original programme before any progress updates and then tighten up the logic and removing all constraints - try to establish a clear critical path.
Make sure you do this BEFORE making a detailed study of the delay events.
Hint - this is done much quicker if you open up the .xer file in PowerProject - make the adjustments and save it back as an .xer for P6.
Then make a spreadsheet log of all your change orders and make a chronological list of dtate of event impact of the events - that is the earliest possible date that the affected task could have started.
Now create dummy tasks of each event in turn and impact it to the affected task - reschedule and note the effect.
Go on to the next delay event and repeat the process.
Make sure that all contractor's delay events are included in the matrix.
This will establish your entitlement to any EoT.
Disruption is a totally different matter and you will need a fully resourced baseline programme before you even think about it.
Check other threads on the topic anmd come back if you need more help.
Best regards
Mike Testro