A slow moving car on a one way street can slow down all behind him.
Try using a milestone after the activity and set the finish no latter than to this activity while you apply the start no earlier than constraint to the first activity.
Member for
14 years
Member for14 years
Submitted by Hlami Baloyi on Mon, 2011-12-05 12:35
If you constraint an activity to "finish not later than", you will destroy your critical path, after updating when you reschedule, all activities with a "Finish not later than" constraints will not move their finish dates and hence your critical path will be destroyed.
You should never use constraints in a construction programme - it distorts the logic and criticality.
If you must have a window for any particular task then set up a calendar with non work periods either side of the work window - but do not be surprised at the bizarre results that occur when progressing the predecessors.
And another point - I never let the software do my resource levelling because it will destroy the planned sequences in nanoseconds and you have no idea what it has done to the programme.
Member for
21 years 8 monthsThere are constraints and
There are constraints and there are constraints.
A slow moving car on a one way street can slow down all behind him.
Try using a milestone after the activity and set the finish no latter than to this activity while you apply the start no earlier than constraint to the first activity.
Member for
14 yearsG T If you constraint an
G T
If you constraint an activity to "finish not later than", you will destroy your critical path, after updating when you reschedule, all activities with a "Finish not later than" constraints will not move their finish dates and hence your critical path will be destroyed.
Hope it helps.
Member for
19 years 10 monthsHi GT You should never use
Hi GT
You should never use constraints in a construction programme - it distorts the logic and criticality.
If you must have a window for any particular task then set up a calendar with non work periods either side of the work window - but do not be surprised at the bizarre results that occur when progressing the predecessors.
And another point - I never let the software do my resource levelling because it will destroy the planned sequences in nanoseconds and you have no idea what it has done to the programme.
Best regards
Mike Testro