Hi Rafael,

good.your point is taken.

I was referring to my experience when i submitted in Impacted as planned method, without constraining finish date, using primavera.

Hi shahul,

Even if you use constraints, the early dates will get pushed off and will show delays.

But when you are not using any constraints, the client may look at your schedule and say ’’yes man you put the delays in but still there is positive float in all these activities, then how do you say that these items caused delay". I mean be prepared to face all that. Even if the consultants engineer know it very well, he might start the discusssion with these words. I personally had this experience. and many of those big managers sitting there do not really understand all these. be prepared not to loose the discussion just with a bad start.

But one thing, if you decide to use finish constraint, i think its better to use ’Finish No later than’ Constraint than using ’Must finish’ constraint.

Sahul,

Negative float will hide the most critical chain or longest chain and will make it very difficult to see the logic in your schedule. Mike calls Negative float an artificial result caused by constraints; I call it an aberration from a defunct Guru (not much of a Guru) that had nothing relevant to add and sold the idea to the Owners as to highlight project delays at the expense of the traditional meaning of float. He told Owners; you morons, you will get many negative float warnings so you know the job is behind. They are morons not because they cannot figure out if the job is or not behind schedule with the aid of a few fixed milestones, they are morons because they insist in such aberration.

Finish Constraints affects the backward pass computations only, your early dates will follow CPM traditional math, and any delay will be shown in the forward path early dates always no matter if job finish date is constrained.

If the Owner or Engineer of your job is such a moron that isists in use of negative lag you can use it, but remember just don’t use float as a measure of delay, and use the difference in the projected early finish date before and after the impact. Whether using or not job finish constraint dates the forward pass computations will always give you the impact. Remember under a resource constrained schedule float value is wrong if using software not capable of handling resource float.

Some CPM software such as Spider Project will not affect backward computations with their use of finish constraints, they will use traditional, or resource constrained float if resource leveled and will show the constraint with a fixed in time symbol on the constrained activity without need to add an additional milestone, you can toggle on and off this flag at will.

Best regards,
Rafael

Hi Shahul

All constraints should be removed before an delay events are impacted.

Best regards

Miie Testro