A colleague send me this screenshot in P6. I would have expected a free float value = 0 of the last activity. It seems however it depends on the last milestone, although it has no logical relation to this milestone ?
A colleague send me this screenshot in P6. I would have expected a free float value = 0 of the last activity. It seems however it depends on the last milestone, although it has no logical relation to this milestone ?
For me completely vague.
[[wysiwyg_imageupload:2470:]]
Member for
24 years 9 months
Member for24 years9 months
Submitted by Patrick Weaver on Sat, 2015-05-16 02:33
1. Good scheduling practice requires an end Milestone for the project. The last activity should have a successor (ie, the Milestone). and every activity should be able to trace a link form its successor to thsi Milestone.
2. If the Milestone has float, as Rafael says, the FF and TF are equal; the constraint acts as the successor.
3. This construct would also mean the critical path as a positive flaot value.
A constraint can be considered as a successor event for purpose of calculating free float. The activity in question can have a time constraint as well as an overall project finish date you set as a global constraint.
You can also set open ended activities as critical, this will make total and free float of the open ended activities equal to zero.
Also keep in mind float values will depend on calendars and float calculation settings depending on your software.
Member for
11 years 3 monthsThanks guys for your
Thanks guys for your answer.
A colleague send me this screenshot in P6. I would have expected a free float value = 0 of the last activity. It seems however it depends on the last milestone, although it has no logical relation to this milestone ?
For me completely vague.
[[wysiwyg_imageupload:2471:]]
Member for
11 years 3 monthsThanks guys for your
Thanks guys for your answer.
A colleague send me this screenshot in P6. I would have expected a free float value = 0 of the last activity. It seems however it depends on the last milestone, although it has no logical relation to this milestone ?
For me completely vague.
[[wysiwyg_imageupload:2470:]]
Member for
24 years 9 months1. Good scheduling practice
1. Good scheduling practice requires an end Milestone for the project. The last activity should have a successor (ie, the Milestone). and every activity should be able to trace a link form its successor to thsi Milestone.
2. If the Milestone has float, as Rafael says, the FF and TF are equal; the constraint acts as the successor.
3. This construct would also mean the critical path as a positive flaot value.
For more on flaot calculations see: http://www.mosaicprojects.com.au/PDF/Schedule_Float.pdf
Member for
21 years 8 monthsA constraint can be
A constraint can be considered as a successor event for purpose of calculating free float. The activity in question can have a time constraint as well as an overall project finish date you set as a global constraint.
You can also set open ended activities as critical, this will make total and free float of the open ended activities equal to zero.
Also keep in mind float values will depend on calendars and float calculation settings depending on your software.