Hi folks,
I can’t seem to find any definitive answer on how free float should be calculated in instances where there is a mandatory constraint forcing a successor task to start before one of it’s predecessors is finished.
I normally find the definition of free float to state something similar to, "the amount of delay which can be assigned to any one activity without delaying subsequent activities". Obviously, this definition does not account for the possibility of such a constraint.
What would you all expect scheduling software to do in this instance? FF = 0? FF = -(x)?
Does it matter?
Bernard Ertl
InterPlan Systems [1]
I can’t seem to find any definitive answer on how free float should be calculated in instances where there is a mandatory constraint forcing a successor task to start before one of it’s predecessors is finished.
I normally find the definition of free float to state something similar to, "the amount of delay which can be assigned to any one activity without delaying subsequent activities". Obviously, this definition does not account for the possibility of such a constraint.
What would you all expect scheduling software to do in this instance? FF = 0? FF = -(x)?
Does it matter?
Bernard Ertl
InterPlan Systems [1]