Re: Locations as constraint by davegb
davegb
Mon Apr 24 08:57:20 CDT 2006
Rod Gill wrote:
> I would do this by grouping all tasks for a single location together under
> one summary task, then copy the summary task for the next location. This is
> one scenario where linking two summary tasks works as it forces all tasks
> for the first location to complete before the next location starts.
>
> --
>
> Rod Gill
> Project MVP
> Visit www.msproject-systems.com for Project Companion Tools and more
>
>
> "Torben Andresen" <TorbenAndresen@discussions.microsoft.com> wrote in
> message news:682200A8-BF93-437F-A17E-86F4EDC689A0@microsoft.com...
> > Hi all.
> >
> > I need to specify the physical location of where a task is to be performed
> > and then have Project re-schedule so that the same resource is not
> > performing
> > multiple tasks at different locations. So even if the resources assignment
> > units is only 20% on to tasks they shouldn't be allowed to be scheduled at
> > the same time due to the fact that they're in to different locations. Is
> > this
> > possible in Project?
> >
> > Thanks in advance,
> >
> > --
> > Torben Andresen
> >
With all due respect to Rod, you should also be aware than linking
Summary lines will invalidate your critical path, may easily cause
problems with circular relationships, and will make tracking, resource
leveling and Earned Value, should you be using any of these features,
invalid in most cases.
I would reccommend adding a Custom field for location, then grouping by
it and checking to make sure you don't have resources jumping around.
Hope this helps in your world.