If activities have different calendars their floats would be different even if they belong to the same path.
Besides, as I showed in the example in my previous post, P6 calculates wrong resource constrained floats and shows wrong resource constrained critical path.
Was it fixed in version 21?
Member for
19 years
Member for19 years
Submitted by Rodel Marasigan on Fri, 2022-11-04 07:29
Currently, I am using it to show the Activity critical path (Float Path) of the selected activity. In the toolbar, you can activate Activity Critical Path Toolbar. By default, it calculate the float path using backward pass of selected activity. If you select the start milestone of the program and click forward pass, it will display the activity forward pass float path. You can increase the number of activity criticality (float path). If the level resource is used, it used the resource level float path of selected activity, forward or backward pass (which ever is selected) or both.
Member for
24 years 8 months
Member for24 years9 months
Submitted by Vladimir Liberzon on Thu, 2022-11-03 13:42
I am curious if P6 leveling was improved in version 21.
Look at the schedule below, created with P6 v.20
Notice that the last project activity Check Support has 20 days total and free float,
activities Develop technical requirements and Develop functional requirements have 13 days total floats though both are critical.
Critical activities do not create a path though in this simple schedule all activities and resources use the same calendar and no constraints are applied except resource availability constraints.
If nothing changed resource constrained total floats and resource critical path in P6 v.21 can be misleading.
I shall probably help my first client migrate to v21 this month. As always, Ed Harris has a good explanation of what this does. I am just not clear how, without a fully-functioning Resource Levelling facility, this helps? Without proper control of splitting under resource levelling, I currently have no clients using it. A cynic (mea culpa) would suggest this new facility extends cute Layout filtering, without actually improving the core arithmetic.
Member for
19 yearsHi Vladimir,As far as I'm
Hi Vladimir,
As far as I'm aware, P6 only calculates Activity float path and not Resource float path.
Member for
24 years 8 monthsRodel,what do you mean by the
Rodel,
what do you mean by the float path?
If activities have different calendars their floats would be different even if they belong to the same path.
Besides, as I showed in the example in my previous post, P6 calculates wrong resource constrained floats and shows wrong resource constrained critical path.
Was it fixed in version 21?
Member for
19 yearsCurrently, I am using it to
Currently, I am using it to show the Activity critical path (Float Path) of the selected activity. In the toolbar, you can activate Activity Critical Path Toolbar. By default, it calculate the float path using backward pass of selected activity. If you select the start milestone of the program and click forward pass, it will display the activity forward pass float path. You can increase the number of activity criticality (float path). If the level resource is used, it used the resource level float path of selected activity, forward or backward pass (which ever is selected) or both.
Member for
24 years 8 monthsI am curious if P6 leveling
I am curious if P6 leveling was improved in version 21.
Look at the schedule below, created with P6 v.20
Notice that the last project activity Check Support has 20 days total and free float,
activities Develop technical requirements and Develop functional requirements have 13 days total floats though both are critical.
Critical activities do not create a path though in this simple schedule all activities and resources use the same calendar and no constraints are applied except resource availability constraints.
If nothing changed resource constrained total floats and resource critical path in P6 v.21 can be misleading.
Member for
9 years 8 monthsI shall probably help my
I shall probably help my first client migrate to v21 this month. As always, Ed Harris has a good explanation of what this does. I am just not clear how, without a fully-functioning Resource Levelling facility, this helps? Without proper control of splitting under resource levelling, I currently have no clients using it. A cynic (mea culpa) would suggest this new facility extends cute Layout filtering, without actually improving the core arithmetic.