I found the differneces between p3 and p3ec like Original duration, remaining duration. so i changed those in p3ec. and somehow managed the -ve total float to -1 now.
I think, that remaining -1 total float is because of level of effort which was hammock in p3.
I am unable to specifically tell you why your project is giving negative float but here are some things to think about.
All scheduling products calculate differently and importing a schedule is a data conversion not a project conversion and when I end up with the same answer after converting anything but a simple project especially one with progress I would consider myself very lucky.
To find the problem you should look at the start and finish dates and floats of the activities one at a time from the start until you find difference. At this point you may wish to check the calendars, lags and lag calendar. Primavera Enterprise has an option of 4 lag calendars, not just the predecessor as in P3. Check the autocost rules maybe the Remaining Duration has calculated differently or you may find a constraint has been handled differently. I have noticed that P3e handles Expected Finish Constraints differently to P3 when an Activity has progress, but I have not work through the issues to find out why.
Member for
16 years 9 monthsRE: P3 to P3ec 3.5.1 conversion - errors
We have the same problem, but caused by calendar, not sure why
Suresh Kumar
Member for
22 years 8 monthsRE: P3 to P3ec 3.5.1 conversion - errors
Thanks Paul for your views and suggestion.
I found the differneces between p3 and p3ec like Original duration, remaining duration. so i changed those in p3ec. and somehow managed the -ve total float to -1 now.
I think, that remaining -1 total float is because of level of effort which was hammock in p3.
Anyway, thnaks a lot.
Dhananjay
Member for
24 years 7 monthsRE: P3 to P3ec 3.5.1 conversion - errors
I am unable to specifically tell you why your project is giving negative float but here are some things to think about.
All scheduling products calculate differently and importing a schedule is a data conversion not a project conversion and when I end up with the same answer after converting anything but a simple project especially one with progress I would consider myself very lucky.
To find the problem you should look at the start and finish dates and floats of the activities one at a time from the start until you find difference. At this point you may wish to check the calendars, lags and lag calendar. Primavera Enterprise has an option of 4 lag calendars, not just the predecessor as in P3. Check the autocost rules maybe the Remaining Duration has calculated differently or you may find a constraint has been handled differently. I have noticed that P3e handles Expected Finish Constraints differently to P3 when an Activity has progress, but I have not work through the issues to find out why.
Regards
Paul E Harris
www.eh.com.au