You will get an argument about the redundat logic especially from the government.
I totally disagree 100% with using progress override I can show you examples where this is absoulty non sense and the float values are incorrect. If you stay on top of out of sequence progress from the begining of the project you wil not run into your proposed problem.
Using progress override has the electrical in-wall AND the Drywall finishing prior to the Studs which is PHYSICALLY IMPOSSIBLE.
I meant have a FS in ADDITION to compound or combination relationship. Yes, it is a bit redundant and they commonly are by accident of hitting the chain button too many times. But it is a common complaint with my schedules but my philosophy is that it doesn't hurt on change anything. The arguement saying that it does hurt states that is changes the float, but I dis-agree because the FS is still driving. In fact, and I think Ron Winter has stated similarly, it does not hurt because if it does not start FS as scheduled, the chain is not broken and there is FF as a safety net.
Related topic:
I have the philosophy that progress overide is much better than Retained logic because on big busy construction projects schedulers do not go back and correct past logic errors which can effect logic and float even though it is dead logic and most of the time should not. I generally run a schedule with both to see if there are any such issues. (Unless something changed in the calculating between p3 and p6)
Member for
16 years 3 months
Member for16 years4 months
Submitted by Zoltan Palffy on Mon, 2017-12-04 14:24
this is called a compound or combination relationship and is used all of the time as standard practice that ties down the start of the activity as well as the finish of it. Technically an activity with only a SS successor as a relationship will be counted as an open end relationship.
Member for
16 years 3 monthsYou will get an argument
You will get an argument about the redundat logic especially from the government.
I totally disagree 100% with using progress override I can show you examples where this is absoulty non sense and the float values are incorrect. If you stay on top of out of sequence progress from the begining of the project you wil not run into your proposed problem.
Using progress override has the electrical in-wall AND the Drywall finishing prior to the Studs which is PHYSICALLY IMPOSSIBLE.
So like Rocky says nah I don't use it
[[wysiwyg_imageupload:5372:]]
Member for
12 years 6 monthsI meant have a FS in ADDITION
I meant have a FS in ADDITION to compound or combination relationship. Yes, it is a bit redundant and they commonly are by accident of hitting the chain button too many times. But it is a common complaint with my schedules but my philosophy is that it doesn't hurt on change anything. The arguement saying that it does hurt states that is changes the float, but I dis-agree because the FS is still driving. In fact, and I think Ron Winter has stated similarly, it does not hurt because if it does not start FS as scheduled, the chain is not broken and there is FF as a safety net.
Related topic:
I have the philosophy that progress overide is much better than Retained logic because on big busy construction projects schedulers do not go back and correct past logic errors which can effect logic and float even though it is dead logic and most of the time should not. I generally run a schedule with both to see if there are any such issues. (Unless something changed in the calculating between p3 and p6)
Member for
16 years 3 monthsthis is called a compound or
this is called a compound or combination relationship and is used all of the time as standard practice that ties down the start of the activity as well as the finish of it. Technically an activity with only a SS successor as a relationship will be counted as an open end relationship.
Member for
12 years 6 monthsclarification: (SS 0 and FF 0
clarification: (SS 0 and FF 0 of course)