PM6 Calculating Multi-projects total float problem

I will try to answer Haixiang’s question.



If you set your Schedule B’s Project Must Finish By Date to December 2999, the negative float should be gone.



I try to guess why it happens:

If you leave Project Must Finish By Date blank, P6 will use Datadate+Total Project Duration as the Project Finish date to back path calculate the Late Finish Date for each activity. Therefore, the Late Finish for activity2 is not driven by activity 1 since they belong to different project.



Please try and let me know.

Feng

For those still using P 6.0.



- Are you facing any problem?

- What are the problem or issue and how to rectify?



I have float calculation error when using P 6.0. When i originally developed the program it showed no negative float (it showed 0 day float)



I have export and import the same program into same database, it showed my project delayed for 2 months.



- I have checked the originally file, scheduling (F9) so many times, it still showed 0 day total float. But when export and import back into same database or different database it will showed negative 2 months total float (delay for 2 months)

Zhang Haixiang



You’re welcome.



I just remember that I had this issue some time ago. Data date seemed the same but due to some reason the time was different. Change of the data date either by "Fill Down" in the project’s view or by "Apply Actuals". It must be exactly the same date and time and you need one common start and one common finish for all projects.



Good luck!

Dieter

Nestor



That’s what I’ve heard from Primavera. There won’t be a bug-fix for 6.1.



Our transfers from 6.0 to 6.1 then to 6.2 where without any problems. An update of the database is required.



Regards



Dieter

Hi Dieter,



You said Oracle won’t support 6.1 any longer but what I know in Hong Kong we’re using 6.0. Indeed we’re doing tender for projects were it is specifically required to use 6.0.



Cheers,

Nestor

Sorry I assumed that you work with the current version.



This setting is in 6.2



But as Oracle announced a while ago, they won’t support 6.1 any longer, it’s better to upgrade.



Regards

Dieter

Zhang Haixiang



It’s among the Scheduling Options:

"F9" --> choose "Options" --> The third option/parameter if you’ll count from the bottom.



Regards

Dieter

They may be using different calendars, if the calendar is different, float will be different.

Another option is that the overall completion date of project 1 is different than the overall completion date of project 2, howvere, I still think the calendars are different.

Check these possibilities and let us know, so we can keep looking for options,



cheers

Did you check your Scheduling options for "Calculate float based on end date of:"? Try with "opened projects" selected.



The following is out of Primavera Help:

"Calculate float based on end date of: Choose the method by which to calculate the float period:



Choose Each project: schedules external relationships on the backward pass using each project’s finish date for open-ended activities, including activities that have an external relationship.



Choose Opened projects: schedules external relationships on the backward pass using the latest finish date of all opened projects and external relationship dates to calculate late dates of activities. Float for open-ended activities is calculated using the latest finish date of all opened projects, allowing for more float than the Each project option. Each Project’s Scheduled Finish date field is calculated as the latest finish date of all opened projects."



Hope this helps

Dieter

2 projects same completion dates? Any constraint dates?



Cheers,

I have a similar problem. I have activities in 2 projects linked. Succeeding activity (simple FS relationship) shows correct total float between early & late but preceeding activity does not show this float. Preceeding activity does not have any constraints and I cannot work out why it does not have same float as successor. Any advice from anyone?