Hi planners!
Id appreciate getting your advice on this.
I am facing a situation where I need to show the net negative delay impact resulting from the owners extended durations in reviewing/approving submittals. My idea was to develop a but-for schedule showing the new finish date based on normal planned durations. The problem is : successors activities actually never start the following day after AF according to their FS relation. They sometime begin long after the rev/app activity is completed and sometimes it even starts long before it began! So, if I change the extended durations from actual to planned, what will I be doing to the successor activities to show the impact. Note that these are actual dates, so another obstacle Id face is how the transfer any impact on the entire successor path.
One idea I thought of is to utilize another method where I would start with the latest activity and go through the driving predecessors only until I reach an extended rev/app activity change it and with the same amount globally change the successors. Then continue with the predecessors until the project start using the same method. Using this method, I wont need to go through maybe a 1500 activity, instead only driving activities need attention.
Any other ideas or any comments!?
Id appreciate getting your advice on this.
I am facing a situation where I need to show the net negative delay impact resulting from the owners extended durations in reviewing/approving submittals. My idea was to develop a but-for schedule showing the new finish date based on normal planned durations. The problem is : successors activities actually never start the following day after AF according to their FS relation. They sometime begin long after the rev/app activity is completed and sometimes it even starts long before it began! So, if I change the extended durations from actual to planned, what will I be doing to the successor activities to show the impact. Note that these are actual dates, so another obstacle Id face is how the transfer any impact on the entire successor path.
One idea I thought of is to utilize another method where I would start with the latest activity and go through the driving predecessors only until I reach an extended rev/app activity change it and with the same amount globally change the successors. Then continue with the predecessors until the project start using the same method. Using this method, I wont need to go through maybe a 1500 activity, instead only driving activities need attention.
Any other ideas or any comments!?