The longest path basis for determining the critical-path is flawed, because of the common use of internal start-no-earlier-than and finish-no-later-than date constraints. From a practical standpoint, the prolific use of date constraints cannot be mandated out of existence, and is likely to only increase in the future. Actually, we encourage the discrete use of date constraints as a practical and effective way to simulate project management intentions and their likely consequences.
Although I completely agree with the above statement I would like to add that some software wrongly implement the FNL constraints by fixing late dates to impossible dates, ridiculous late dates early than early dates !!! thus creating the negative lag aberration. Not all software implement the modeling of FNL constraints so wrong with such distortion of the float values, one of the most important metrics in scheduling.
It is simple, if a FNL constraint cannot be met then the late dates become equal to the early dates, late cannot be earlier than early, a missing mathematical constraint in such software. Note that the right mathematical model Keeps the correct identification of criticality on these activities maintaining float equal to 0 and not by assigning dates that have no meaning in the physical world as we know it.
Member for
16 years 7 months
Member for16 years7 months
Submitted by Gary Whitehead on Sun, 2012-04-01 10:43
just link them to the latest activity in the project -don't create a new milestone beyond the end date, as that will then become your new critical path
As an interim solution (as the plan isn't my own) would you advise adding either a successor task or an end milestone to each of the open-ended tasks, with these set at a point in the future beyond the schedule?
Thanks
W
Member for
15 years 9 months
Member for15 years9 months
Submitted by Johannes Vandenberg on Sat, 2012-03-31 17:11
The best way to deal with this situation is to make sure that all activities have predessesors and successors. In a schedele you should not have open ends. If you use Primavera Risk Analysis then use the option "Schedule check". This detailes all the anomilies in the schedele.
Member for
21 years 7 monthsJust remember to avoid the
Just remember to avoid the misconception there is always a single critical path, real life contracts usually involve several delivery milestones.
From
http://www.icoste.org/AACE2008%20Papers/Toronto_ps07.pdf
The longest path basis for determining the critical-path is flawed, because of the common use of internal start-no-earlier-than and finish-no-later-than date constraints. From a practical standpoint, the prolific use of date constraints cannot be mandated out of existence, and is likely to only increase in the future. Actually, we encourage the discrete use of date constraints as a practical and effective way to simulate project management intentions and their likely consequences.
Although I completely agree with the above statement I would like to add that some software wrongly implement the FNL constraints by fixing late dates to impossible dates, ridiculous late dates early than early dates !!! thus creating the negative lag aberration. Not all software implement the modeling of FNL constraints so wrong with such distortion of the float values, one of the most important metrics in scheduling.
It is simple, if a FNL constraint cannot be met then the late dates become equal to the early dates, late cannot be earlier than early, a missing mathematical constraint in such software. Note that the right mathematical model Keeps the correct identification of criticality on these activities maintaining float equal to 0 and not by assigning dates that have no meaning in the physical world as we know it.
Member for
16 years 7 monthsjust link them to the latest
just link them to the latest activity in the project -don't create a new milestone beyond the end date, as that will then become your new critical path
Member for
13 years 7 monthsThanks Johannes,As an interim
Thanks Johannes,
As an interim solution (as the plan isn't my own) would you advise adding either a successor task or an end milestone to each of the open-ended tasks, with these set at a point in the future beyond the schedule?
Thanks
W
Member for
15 years 9 monthsHi WilliamThe best way to
Hi William
The best way to deal with this situation is to make sure that all activities have predessesors and successors. In a schedele you should not have open ends. If you use Primavera Risk Analysis then use the option "Schedule check". This detailes all the anomilies in the schedele.
Johannes