J
Judy
I am working on a project has mulitple install dates at multiple sites.
I need the tasks for the install dates to match the dates I gave to the
customer since I need to coordinate these dates with the customer. I know it
is bad to put date constraints on my tasks. It seems I have a couple options
to make the dates come out correctly.
1. Put on deadline on the correct date - look at the total slack of a
predecessor and put that much lag on the predecessor. Then my total slack
goes to zero.
2. Add edays to the leveling detail. (I can't figure out how to calculate
edays from total slack - just did it by trail and error). Still my total
slack goes to zero.
I would love to find a way to move the task out to the adversised date and
still see my total slack numbers. The only way I can find to do this is to
put a "must start on" contraint on the install task. But I hate to do that.
Do you have any suggestions to get a task to fall on the correct date and
still be able to see the total slack of the tasks that come before it?
I need the tasks for the install dates to match the dates I gave to the
customer since I need to coordinate these dates with the customer. I know it
is bad to put date constraints on my tasks. It seems I have a couple options
to make the dates come out correctly.
1. Put on deadline on the correct date - look at the total slack of a
predecessor and put that much lag on the predecessor. Then my total slack
goes to zero.
2. Add edays to the leveling detail. (I can't figure out how to calculate
edays from total slack - just did it by trail and error). Still my total
slack goes to zero.
I would love to find a way to move the task out to the adversised date and
still see my total slack numbers. The only way I can find to do this is to
put a "must start on" contraint on the install task. But I hate to do that.
Do you have any suggestions to get a task to fall on the correct date and
still be able to see the total slack of the tasks that come before it?