S
ssilk99
Hi everyone,
I have a project where I want to schedule backwards for the
predecessors of a certain mid-point task, and forwards for those after
it. Here's a detailed description of the problem.
The tasks in the project, in order, are Estimate, Design, AFE,
Construction, Records Updated, and Close.
The only date that is rigid is the end date of Construction, which is
the date the customer needs delivery. Other than that, I just want to
schedule things in the most efficient timing possible. So, I want to
set a fixed end date for Construction, then make the first three tasks
schedule backwards from there so I can figure out when each should
start. So, if customer requires item by January 10th, and Construction
will take 5 days, it should start on the 5th. Then, if AFE takes three
days, it should start on the 2nd, and so on. After the Construction end
date, the remaining tasks should schedule forward.
When all this is done, if I enter a longer task length for any of
Estimate, Design, AFE, or Construction, I should see the start date of
the project move back, whereas if I enter a longer length for Records
Updated or Close, I should see the end date of the project move
forward.
Right now when I try to do something like this, I get a scheduling
conflict, with two tasks happening simultaneously, and flow arrows
looping back in time.
I'm using Project 2000.
Thanks.
I have a project where I want to schedule backwards for the
predecessors of a certain mid-point task, and forwards for those after
it. Here's a detailed description of the problem.
The tasks in the project, in order, are Estimate, Design, AFE,
Construction, Records Updated, and Close.
The only date that is rigid is the end date of Construction, which is
the date the customer needs delivery. Other than that, I just want to
schedule things in the most efficient timing possible. So, I want to
set a fixed end date for Construction, then make the first three tasks
schedule backwards from there so I can figure out when each should
start. So, if customer requires item by January 10th, and Construction
will take 5 days, it should start on the 5th. Then, if AFE takes three
days, it should start on the 2nd, and so on. After the Construction end
date, the remaining tasks should schedule forward.
When all this is done, if I enter a longer task length for any of
Estimate, Design, AFE, or Construction, I should see the start date of
the project move back, whereas if I enter a longer length for Records
Updated or Close, I should see the end date of the project move
forward.
Right now when I try to do something like this, I get a scheduling
conflict, with two tasks happening simultaneously, and flow arrows
looping back in time.
I'm using Project 2000.
Thanks.