reschedule uncompleted work --constrains added

[Haixiang]

I am updating a schedule (input progress info. actual start, % complete ...),
some tasks were delayed. i'm trying to reschedule them to start on Status
Date, and all tasks move accordingly as driven by dependency, it can give me
a forcast of how the whole project will be.

So I use "Tools">"Tracking">"update project">"Reschedule uncompleted work
to start after:"
After reschedule constraints (start no earlier than) were added to all tasks
except those actually started. I don't like these contrains,it make me
difficult to tell which constraint is added myself,and which is by the
rescheduling. Can it work as Primavera, or just add constraints to those must
have constraints, for example, task A will be rescheduled to start on 1st
March, so constraints must be added to make it start no earlier than 1st
March, but all successors of task A do not need constraints, there start
dates are driven by links.
Anyway I can choose to reschedule selected tasks,but to select these tasks
that must have constraints is not easy.
Is there any better solution?
thanks in advance.

 

[Gérard Ducouret]

Hello Haixiang,

As far as I know, there is no other way than to select the tasks which
generated the delay.
I hope they aren't not too numerous in your plan ;-)

Gérard Ducouret

 

[Haixiang]

Gérard Ducouret,

Thanks.
I'm trying to make a filter to select the tasks that should have started
before status date. I hope it can minimize my work.

 

[Gérard Ducouret]

Haixiang,

An other criteria in your filter would be :
Resume < "Status Date :"?
It could minimize your work but not automate it.

Hope this helps,

Gérard Ducouret

 

[Steve House [MVP]]

AFAIK, the only tasks that get those constraints are those that should have
started before the status date but for some reason failed to do so. When
you reschedule uncompleted work it adds a constraint to bring those tasks up
to the status date. But subsequent tasks that would have started AFTER the
status date anyway but now need to be delayed will be pushed forward by
their links without SNET constraints being placed on them.

You can test this with a little Project conmsisting of 3 5-days tasks,
linked FS. Set Project Start to 21 Feb. Set the current date/status date
to 03 Mar. Mark the first task 50% complete. Use the Tracking Tools,
reschedule upcompleted work to start after 03 Mar.

The results should be ...
Task A: Actual Start 21 Feb, 50% progress, splits on Wed at noon and
resumes 03 Mar, 08:00, no constraints
Task B: Pushed out from originally starting 08:00 28 Feb to now start 13:00
08 Mar, SNET constraint of 17:00 03 Mar applied. Note the link pushes its
scheduled start even later than its constraint date.
Task C: Pushed out from originally starting 07 Mar to now start 13:00 15
Mar, but NO constraint applied.