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.

Define Early and Must Finish Date

3 replies [Last post]
Wed, 2007-08-22 11:23
Kevin Murdock
User offline. Last seen 16 years 24 weeks ago. Offline
Joined: 24 Jul 2007
Posts: 7
Groups: None
I am trying to figure out the difference between the early finish date and must finish date. I need to know what one should be the same as the contract completion date.
Top

Replies

Thu, 2007-09-06 03:46
#1
James Barnes
User offline. Last seen 1 year 22 weeks ago. Offline
Joined: 6 Sep 2007
Posts: 243
Groups: Petro-Chem / Oil & Gas
There is a "must finish" date in the project overview, but I think you’re talking about activity level constraints, right? In which case I assume you mean Mandatory start / finish constraints

My mentor (the bloke who taught me P3) described the use of Mandatory dates as akin to swearing in church, by which I assume he meant blasphemy. They circumvent the logic in your plan. I don’t use them.

I’ve just reread your post and realise that I probably misinterpreted what you’re after. the above still stands but I think you mean the Early Finish and Must finish dates in the project overview?

If so, then what the 2 previous posters say is accurate. The Early Finish date is the last Early Finish date that appears on any of the activities in your project. This is calcualted by the schedule and so you can’t set it. You can set a Project Must Finish by date. Setting a "Project Must Finish by" date effectively puts a "Late Finish" constraint on whatever activity has the latest Early Finish on your project. If you have an activity with an Early finish date that is later than your stated "Project Must finish by" date then a path of negative float will be generated, showing that teh analysis says you cannot finish your project on time. Personally, I have only found this useful for very simple plans. Much better is to build a high level plan, above your detailed plan, which contains your completion milestones fro each phase, work area, etc. Then you can set late finish constraints on these milestones. That way each of them will generate a negative float path if their finish dates are under threat, you will also get more detailed float information for embedded activities, where you will see teh float on that activity before it affects the relevant milestone (or the nearest one, if it attached to many of them).
Top
Mon, 2007-09-03 04:45
#2
Christian Adrian ...
User offline. Last seen 5 years 4 weeks ago. Offline
Joined: 3 Jun 2003
Posts: 193
Groups: None
Kevin

The "Must finish date" can be the contract completion date when establishing a baseline, but for analysis purpose it is better to remove this constraint.
Top
Wed, 2007-08-22 18:45
#3
Deepak Jain
User offline. Last seen 10 years 24 weeks ago. Offline
Joined: 14 Jan 2006
Posts: 31
Groups: Petro-Chem / Oil & Gas
Early Finish date is generated by Time-Analysing the Schedule and signifies the earliest date you can finish a schedule. Must Finish defines Mandatory date or a constraint that the Project must end by. Must finish date can be the Contract Completion Date, if you own the Program Float.
Top