Activities with neg (-) Total Float

Riaz,

Hit F9 & got to Options. Check the settings for "Define Critical Activities as". Most likely this is set to "Longest Path", instead of "Total float less than or equal to 0", which you were expecting.

99% of the time, negative float is caused by either out of sequence working, or constraints which are not being adhered to. IMO either of these situations is an example of poor planning. If most of the schedule has negative float, I would start your review by understanding why.

Cheers,

G

 Thanks for your comments.

But even though, if it is set to "Longest Path", software should show activities in longest path, as "critical activities" by changing bar color or not?

Secondly,

I am using P6 R8.2 and trying to import the aforesaid schedule but getting this message CVRCU-1939-9.

How to rectify this problem? I would really appreciate, if you can help me out.

Regards

Riaz 

Yes, if it is set to longest path, then activities on the longrst path should be critical.

But this will not be all activities with neg float, only those activities on the longest path.

If you are not seeing any activities at all shaded red, try the following:

1) Apply the default filter "critical" -do any activities show up in this filter?

2) Insert the column "critical", from the "General" section -are any activities ticked?

3) Check your bar settings by right-clicking in the barchart and choosing "bars" -Is there a bar called "Critical Remaining" present? Is it selected? Is the timescale set to "remain bar", filter set to "normal and critical", and colour set to red?

I can't help you with you second query -suggest you contact Oracle support and/or check the knowledge base.

Cheers,

G

Hi Riaz - welcome to Planning Planet

Another possibility is that the software has a general Must End By that acts as a global constraint.

Also check your calendars as the might be a whole series of Non Work days that have not been covered by work patterns.

Good luck.

Mike Testro

I would expect that if Longest Path is not selected then Total Float less than or equal to some value might create the situation if the value is set to some negative number.  Say you select -10 then anything larger than -10, say -9, even if negative would be displayed as non critical because -9 is greater than -10. 

It is possible the scheduler was trying to understand the logic of the critical path and at some point selected a negative number to define zero criticality along some negative float path. 

Still the procedure is cumbersome and confusing when you have several contractual milestones. The best way to understand criticality is without negative float functionality, something difficult to erase on software that mixes true float with negative float.