Load leveling tears up jobs

A

andrewandrew

I have a question: my clients use Project to plan large industrial jobs in
which each task necessarily comes immediately after the predecessor task.
There are lots of jobs happening simultaneously in each project, and they
would like to use Project's Leveling feature. However, leveling inserts
Leveling Delay in the middle of a job, which is unacceptable. For example, a
typical job might involve changing a (very large) motor. First an electrician
disconnects the motor, then a mechanic removes it and installs a new one,
then the electrician comes back and connects it. Since there are different
resources involved, we like to plan this as several tasks. And we do not want
there to be any delay between tasks. However we might need to change 20 such
motors, and would like Project to automatically space out each job so that
the electrician is scheduled to run from job to job. Right now we would need
to very delicately balance the priority fields to get Leveling to behave as
required--this is difficult and if anything changes it needs to be reset. As
a result we end up linking these independent jobs together with task
dependencies. Is there any way we can specify that the job (a collection of
tasks) should not be broken up ever, but can be level delayed as a unit? Are
there plans to implement such a feature?
 
J

Jan De Messemaeker

Hi,

You will not be 100% sure but a ciustomer of mine handles this as follows:
Link the tasks to be done consecutively
Make sure the reason why the tasks must be consecutive (the motor or the
spot it is on) is there as a resoruce
Give the first one a rather low priority
Give the following ones a priority of 999

That does it.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top