Jorge,

Please explain a little better why the weekend in your example is important to count in a "global float" number. Wouldn’t it be dangerous to inflate the value based on the successor’s calendar?

The goal should be to ignore ALL calendar effects on the activity and "key successor". Also how do you recommend getting (exporting/calculating) the Float start date OR the Float end date?

Jorge,
Sorry I have different view on yours. The difference calendar is the requirment.

May I stress on the formula: Float = LF - EF. This formula cannot provide the expected result since the difference is in same calendar also.

That’s why I suggest is the difference is Float start date - Float end date.

Example to support, consider a activity is OD=5; start on Fri; end on Thr; 5 wkday/wk calendar; 1D float after schedule. Standard formula will result 1, but the result may be 3 since weekend may be count in and this depends the calendar of its key successor(s).

Alex,
you proposed hand made leveling that may be used only for small projects where the number of resources and activities is small. Besides the artificial links may restrict scheduling options in future when the situation in your project may change.
I agree that the scheduling software shall use not only activity and resource calendars but also calendars of relationships (lags).
If you can simulate the real life conditions then the schedule will be more reliable and less complicated.

Vladimir

Agree that we need to consider the resource when calculating float. However, if we added the resource constraint within the forward / backward pass then it will complicate the calculation. In a way that you may or may not notify where and when the resource driving the activity to longer than it original antipicated.

My usual pratice is firstly assign the pure logic / duration without any resource constraints.
Look at the resource histogram
find the period that have a peak for each individual resources (or critical resource only)and overall resource
Link the resource logic between activity.
ie two independent activities using resource 10 unit of resource / day
if resource A is only limited to 10 units / day I need to link between them and start one activity 1 first then activity 2.

And that may create a critical path within the logic network
I schedule the project again and looking at what are the possible way to increase the total float.

this excises may take sereval pass. Once finish I will then have a baseline project.

Back to the original question, it will be difficult to calculate exact float within a multi-cal project environment. Remember if you have a link between two activity pre activity have a 5 day cal and the suc have a 7 day cal what is the relationship should be ?? cal 5 days or 7 days. if the relationship is FS and the first activity finished @ Friday should the activity start on Sat since the activity can start on SAT. But the predecessor cal can only start on monday - friday. It is complicated. The software have to make a assumption which is the global cal use at all time. I guess if the software allows each relation have their own cal assign to it then a calculation base on multi-cal float can be achieve.

The question is what benefit the schedule or the project can gain by introducing all these additional variables. Remember one or variable you need one more regulation or additional causes in the spec from the clients. (Because they don’t want to give a open cheque to the contractor)

Yup.. if we use different calendar it will be make different finish date and total float......

Regards,
Berli

Suresh, hope this help
Create a dummy activity in 7-d calendar to ’eat’ float. One dummy per each float. FS relationship to its associated activity.
Before claculation, OD for dummy is zero. Schedule the network. Then by gloabl change fill in start/finish dates of float to dummy activity Start on and expect finish dates constraint. The OD of dummy will be in 7-day calendar calculated float.

Creat a custom data item called "float", and make a global change "float = early finish - early start".

Joe

P3 calculate various field base on a common field. Like plan % Complete, summary of acutal % complete, total float.

However, it is not possible to calculate float on a multi calenda activity.

If you want you can also constrain finish dates to the early finish dates in the copy.

Just copy your project to a new project and do a global change to your calendars.