It might be an issue with the lag calendars, unfortunately P6 is limited to some global control of lag calendars instead of an independent calendar. Sometimes you need it to be equal to successor, sometimes you need it to be equal to predecessor and sometimes different to successor or predecessor but not a 24/7 calendar.
Predecessor Activity Calendar - Choose this option to calculate lag based on the predecessor activity's calendar.
Successor Activity Calendar - Choose this option to calculate lag based on the successor activity's calendar.
24 hour calendar - Choose this option to use a calendar that specifies work time 7 days/week and 24 hours/day.
Project Default Calendar - Choose this option to use the calendar that is designated as the default for new activities.
The default calendar for new activities is specified on the Administration > Calendars page or in the Project Management module.
Suggest you try changing the options and see if the computed values of float varies.
Also try changing the milestone type from finish to start milestone.
Member for
16 years 7 months
Member for16 years7 months
Submitted by Gary Whitehead on Wed, 2012-08-29 09:29
That is correct, if I had the same calendar for all my activities, the total float of each of my critical path activities would be zero. I think this may be a bug.
Member for
21 years 8 monthsIt might be an issue with the
It might be an issue with the lag calendars, unfortunately P6 is limited to some global control of lag calendars instead of an independent calendar. Sometimes you need it to be equal to successor, sometimes you need it to be equal to predecessor and sometimes different to successor or predecessor but not a 24/7 calendar.
Suggest you try changing the options and see if the computed values of float varies.
Also try changing the milestone type from finish to start milestone.
Member for
16 years 7 monthsIt seems to be calculating
It seems to be calculating the late finish of Activity A using Activity B's calendar, for some reason.
Can you try a couple of things for me?
(1) Please confirm relationship from A to B is FS with zero lag
(2) Please confirm what settings you have in schedule options for "Compute Total FLoat As" and "Calendar for scheduling relationship lag"
(3) What happens to total float if you change the settings in (2)?
(4) What happense to total float if you make activity B a start milestone?
(5) What happens if you make it a task?
(6) What happens if you dissolve activity B?
(7) What happens if you give Activity B (as a finish milestone) the continuous calendar?
Member for
24 yearsRob,In P6, the default number
Rob,
In P6, the default number of hours per day is 8 hours = 1 day, the moment you change the working hours then the calculations will change.
Regards,
Daniel
Member for
13 years 4 monthsThat is correct, if I had the
That is correct, if I had the same calendar for all my activities, the total float of each of my critical path activities would be zero. I think this may be a bug.
Member for
13 years 4 monthsThere are no constraints on
There are no constraints on any of the activities except for the first one (A) which has a "Start on or After" primary constraint.
Member for
24 years 9 monthsCheck if there are no Finish
Check if there are no Finish No Later han constrints.
Member for
19 years 1 monthI can only guess that it's
I can only guess that it's because of the difference in calendars;
and the links as FS for all;
if you got the same calendar for all,
then your total float will be zero