Has your question already been answered?

Get a quicker response; before you post, why not search to see if it has already been answered

the case for and against putting a Float Activity at the end to keep critical path zero for simplicity etc.

1 reply [Last post]
John Reeves
User offline. Last seen 1 week 5 days ago. Offline
Joined: 10 May 2013
Posts: 40
Groups: None
In an normal environment with an Owner, a CM, and a Contractor what is the the case for and against putting a Float Activity at the end to keep critical path zero for simplicity etc and to key on time left at the end.  The definition of Ctitical Path is zero float - but what if you have more time than you need - such as 3 months on a 2 year job, it would not be helpful to inflate durations just to hit the spec, but also a "float" activity at the end might have issues.  If the contractor wants to show float, isn't it in the owners favor to let them. 

Replies

Zoltan Palffy
User offline. Last seen 1 hour 58 min ago. Offline
Joined: 13 Jul 2009
Posts: 1902

why not just set the threshold and define the critical path to what ever float that you have  

go to tools

schedule 

options

Define critical activities as 

Total float less than or equal to 

then put in your value.

the other option is to never set a project must finish by date or have a fnish on or before milestone this way the float wil ALWAYS be zero