WONDERFUL QUESTION, I THINK THE CONTRACTOR CANT ADJUST THIS OPTION WHEN UPDATING, BECAUSE IT WILL BE MISLEADING ACTION AND CANT MONITOR THE SITE WORKS.
Member for
20 years 4 months
Member for20 years4 months
Submitted by Charleston-Jos… on Sat, 2007-10-20 03:27
Very interesting. I think depends on which side are you
The bright side, if your are in the contractor side
use retained logic to scare the project team in acting to mitigate delays, the top executive of the contractor are ignoramos always under the influence of commercial or contract department believing that claims for extension of time and associated cost will give them more profit than running the project as per baseline program or revised baseline program
use progress overide if the project teams are enligthen, the contract department influence in site activities are minimal to the point of zero, progress overide will also make way to upgrade the program into live and realistic schedule activities.
IF you are on the dark side, meaning, consultant, project manager, client. Always use retained logic to scare the contractor in doing there very best to achieve project goals.
Cheers,
Sensei
Member for
20 years 10 months
Member for20 years11 months
Submitted by Andrew Flowerdew on Wed, 2007-10-17 20:12
Member for
18 years 2 monthsRE: Time Impact Analysis (Prog Override vs. Retained Logic)
WONDERFUL QUESTION, I THINK THE CONTRACTOR CANT ADJUST THIS OPTION WHEN UPDATING, BECAUSE IT WILL BE MISLEADING ACTION AND CANT MONITOR THE SITE WORKS.
Member for
20 years 4 monthsRE: Time Impact Analysis (Prog Override vs. Retained Logic)
Actually,
My post will not help anyone in the project team. But it is real experience.
So go back to Post No. 3 by Andrew.
But the best advice is just blend with the project team, like a TIMANO of the Bourne Identity series.
I think this is one reason Primavera give this options. It will make us flexible and not dogmatic in our planning activities.
Remember, planning is only a tools. There are lots of controversy and issues on the way planning are implemented in particular project.
Cheers,
Sensei
Member for
20 years 4 monthsRE: Time Impact Analysis (Prog Override vs. Retained Logic)
HI,
Very interesting. I think depends on which side are you
The bright side, if your are in the contractor side
use retained logic to scare the project team in acting to mitigate delays, the top executive of the contractor are ignoramos always under the influence of commercial or contract department believing that claims for extension of time and associated cost will give them more profit than running the project as per baseline program or revised baseline program
use progress overide if the project teams are enligthen, the contract department influence in site activities are minimal to the point of zero, progress overide will also make way to upgrade the program into live and realistic schedule activities.
IF you are on the dark side, meaning, consultant, project manager, client. Always use retained logic to scare the contractor in doing there very best to achieve project goals.
Cheers,
Sensei
Member for
20 years 10 monthsRE: Time Impact Analysis (Prog Override vs. Retained Logic)
Neither give the final answer, use whichever but be prepared to adjust the results if needed to reflect the reality of what happened when updating.
Member for
19 years 2 monthsRE: Time Impact Analysis (Prog Override vs. Retained Logic)
Hi,Hesham
progress override logic should be used for the horizontal projects like roads and infrastructures.
retained logic should be used for the vertical projects like Buildings.
THANKS