Newbie help

[Craig]

Hello all,

I am setting up a project that will take a set
implementation plan that is duration (date)
driven.Resources will be assigned but for sorting and
status reporting only. Then duplicate it to 4 different
areas of our plant. The plan consists of 4 Summary tasks
with each task based on a start/finsh relationship. On the
completion of Sum.task #1 i would like to start the second
area. As the second area completes Sum.task #1 then start
the 3rd area and so on.
I would like to set up a master plan that would allow me
track and modify any variations to the finish date of each
area and to the overall finsish date of the project.

Any advice on the most efficient way to do this would be
greatly apreciated,
Thanks...Craig

 

[Steve House]

Even though sum.task.1 has the same name in each of the 4 areas, they really
are discrete activities. So when you replicate the first set of tasks to
the other groups, creating a total of 4 sets of tasks, it might not be a bad
idea to give them unique names, just to make jugglin it in your mind easier.
It's not required that you do so but as I say, it can help with the mental
gymnastics. So each occurance of "sum.task.1" would be renamed to
sum.task.1.area1, sum.task.1.area2 etc etc. Now link the last subtask under
sum.task.1.area1 and link it FS to the first subtask under sum.task.1.area2
and the same for the rest of the areas and you're home free. That makes
Area 1, 2, 3, and 4 into what are really broad phases of the project as well
as names of places.

FYI - you say your project is a set implementation plan that is date driven.
Don't make the mistake of supplying those dates as you input, using
constraints to force the plan to conform to them. Just give it the start
date and flag those manadatory dates by using deadline entries. If Project
doesn't calculate a work schedule that complies with your required
implementation schedule, when you work the schedule as you've conceived it
you won't meet your deadlines in the real world either. You'll have to do
something concrete such as changing the order of tasks when possible, maybe
it is possible to start Area 2 before you're completely done with Area 1, or
changing the length of time it takes to do some of the subtasks by getting
more resources to work on them, as examples, so that the calculated schedule
in Project conforms itself to the schedule your implementation program
requires. That way you have a fighting chance of actually being able to
meet your requirements.