Free Float Constraint

Haresh,
if i m not mistaken, FreeFloat is the float time between a predecessor and a succesor.

so if your chain of sub-contracting activities (from Nomination to Delivery, assuming the date of nomination constraint the start of the chain) finish exactly when your construction activity should start, then with or without the Free Float, makes no difference.

correct me if i m wrong guys. dont use much of constraints in my schedule, other than contractuals keydates for STARTs and HANDOVERs.

Hi Eugene,

Good day! Free Float constraint is equivalent to "As Late As Possible" constraint. In my experience, i assigned this constraint to "Required On Site" or ROS milestone or activities for Equipment or material delivery. This is useful to determine the start of procurements (or other activities) by calculating backward from the start of its successor’s start date.

To satisfy the Consultant request, once you determined the ES of those activities with FF constraint, you could then assign a certain "lag" from its driving predecessor to simulate the same ES.

I guessed that the Consultant is not that strict with lag since they could not easily filter the activities compared with activities with constraint.

Hope this make sense.

Cheers!

Jaime

Haresh

What you can do is using custom Data items.

Plan Start and Plan Finish. and display these in your schedule. therefore you do not need to use a constraint to the milestone or activity but still able to track some of these key days.

A lot of contract is stated you cannot use constraint because that way you can display a true Critical Path

Good Luck

Alex

Thanks Jaime,

But if I use lag , it creates problem while we are updating a program ,since we cannot keep the lag fixed as we update the program. The lag will increase / decrease depending upon the progress of the site. So keeping lag instead of free float constraint is not a wise thing to do as per my thinking.

I also know that mandatory start constraint and mandatory finish constrain are not applicable since using both the constraint we cannot calculate the correct total float while updating the program.

The question I want to ask is that
Can we prove contractually, by using free float constraint our float will not be affected.
Any suggestions to this are most welcome , since I want to write contractually to the consultant that using free float constraint in my program is correct. Pls suggests…….

Dear Haresh
Is it right that use of constraint in the schedule is not welcome but in some case we are compelled these. The suggestion of other guys is valuable and you can apply these in your schedule. But I think now at this stage you don’t want to revert from your points.

Yes you can write that you are right, use of free float will not affect the schedule because free float will not be greater then total float in any case. So the driven float for the activities are the total float not free float, free float is only give a cushion that you can play with the resource leveling without affecting any other activity of schedule.

This is one solution in my opinion may be correct or not.
Regards
Tahir