Hi All,
I thought I understood pretty well how P6.2 calculated/ranked Multiple Float Paths using Total Float after reading this old POINT article http://primavera.zxlm.cn/kb/prim36502 [1] (despite the article referring to P5) however I have run into an odd scenario where this ranking system seems to fall apart.
I've managed to re-create the oddity by creating a simple 4 milestone schedule
The steps to re-create the situation are as follows:
- Create a new schedule with 4 start milestones each using a 7 day calendar (for simplicity)
- Create FS relationships between activities (1-2),(2-3),(3-4),(1-4),(2-4) (I realise some of these are redundant)
- Now create a new, temporary calendar using the 7 day calendar as a base, but set the date upon which all the milestones sit to a 'non-work' day.
- Assign this calendar to milestone 3
- Run the scheduler using Multiple paths based on "Total Float"
Strangely I end up with two float paths FP1 milestones (1,4) and FP 2 milestones (2,3), whereas I would have expected all four milestones to have been float path 1 since the 'driving' and 'most critical' relationship working back from milestone 4 should be milestone 3.
I have read in many places that P6 has some 'issues' when it comes to dealing with float calcs and multiple calendars, but this seemed pretty clear cut to me.
I'd like to know if other people have this issue, whether it's restricted to P6.2 specifically, and if anyone can explain what's actually going on. Is there something obvious I'm missing here?