Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Project completion date changed but TotalFloat rem

3 replies [Last post]
Fri, 2003-02-14 05:34
P3 Scheduler
User offline. Last seen 19 years 38 weeks ago. Offline
Joined: 16 Feb 2002
Posts: 18
Groups: GPC Malaysia
Project completion date brought forward but Total Float still remains the same. Why?
---------------------------------------------------------------------

I have an ongoing project whereby the contract completion date is
3FEB03.

At the latest update the project is delayed by 72days (Total Float =
-72days) due to reasons beyond the control of the contractor. An
extension of time claim was made by adding the necessary activities to
the schedule to prove that the delay was contributed by other
interfacing contractor. Based on the EOT claim, the contractor was
awarded an EOT of 72days and the revised completion date has been brought forward by 72days from 3FEB03 to 16APR03.

From the menu File->Project Overview...", I have changed the "Project
must finish by:" from 3FEB03 to 16APR03 to reflect the revised
completion date. However when I re-schedule the project the Total Float still shows a -72day instead of zero! Why is it that the Total Float calculation is not based on the "new" completion date?

Any feedback will be very much appreciated.

Best regards,
CS Ong (arlie@pd.jaring.my)
Top

Replies

Mon, 2003-02-17 16:55
#1
Ed van der Tak
User offline. Last seen 12 weeks 4 days ago. Offline
Joined: 5 Mar 2002
Posts: 86
Groups: Regional Representatives
Gents,

I understood you used the "project must finish date" as a ultimate "wall" for the end of your project. You already found out that projects can be delayed or in other cases activties are still to be planned/executed.

In most cases it is better to leave the PMF date open or at the end of the year (f.i. 31-12-2003) and put a mandatory finish contraint at a "final" milestone. The PMF date puts a limit to (calendar) calculations P3 makes and also the timeframe of the screen and print layout.

So good luck next time!

Ed van der Tak
ARAM Planning Consultants
The Netherlands
Top
Mon, 2003-02-17 10:33
#2
P3 Scheduler
User offline. Last seen 19 years 38 weeks ago. Offline
Joined: 16 Feb 2002
Posts: 18
Groups: GPC Malaysia
Hi! Tara,

Yes, you are correct! I removed the mandatory finish constraint on the Finish Milestone and everything is ok.

Thank you and best regards,
CS Ong
Top
Mon, 2003-02-17 00:38
#3
Tara Muddappa
User offline. Last seen 17 years 1 week ago. Offline
Joined: 17 Dec 2002
Posts: 26
Groups: None
Hi,

The only reason I can think of is you also have finish milestones with Mandatory Finish Constraint or even a Late Finish Constraint.

Please remove this and try rescheduling,this should work.
Top