Why does leveling impact resource time that is already allocated?

[kraus]

I work in a small organization that shares resources across different
projects. To manage this we utilize the leveling functionality to ensure we
don't have resources overallocated.

What I have seen is that my resource, allocated at 70%, is scheduled for
1.45 days of work. The other project has since added the same resource,
allocated at 80%, for the same week and levelled. As a result, when I go into
my plan and level first thing my 1.45 days scheduled has reduced to 1.4 days.
This then waterfalls on until the .05 of a day can find a home, which
depending on the resources allocation on other projects could push out a long
time.

It is my understanding that once a resource is allocated and levelled
against the organization then that resource is "spoken for". All other
projects that require the same resource would then be forced to work around
the time frame that my project requires the resource. It doesn't appear to be
happenning in this instance. Any suggestions?Neither plan has set any
priority specific work (if it helps)

Thx

 

[Joe]

For what you are trying to do, I STRONGLY suggest you don't use resource
leveling. This sill not work for your needs.

 

[Jan De Messemaeker]

Hi,

Uncheck "Leveling can create splits in remaining work"
HTH

 

[Jan De Messemaeker]

Who says so?
I've seen several customers work like that and it works well.
You have to think about the parameters, and not introduce unlevelable tasks.
Leveling is an entire part of Project's scheduling engine and I fail to see
why one would not use it.
HTH

 

[kraus]

Hi Joe,
What would you recommend then? I need to ensure our resources are not
overallocated and MS Project provides this for us.

 

[kraus]

Hi Jan,
Thanks for the suggestion.

That actually makes things worse. It's my understanding that MSP allocates
the tasks based off of any available time which result in splitting tasks. If
I prevent the tasks from splitting then if their isn't enough time to finish
the task before another task starts on another project then the entire task
gets pushed instead of a portion.

My concern is not that the task has split but rather if I have earmarked a
resource and levelled the plan, no other plan should be able to push these
dates but rather they must work around these dates. I know if you have two
plans opened at the same time then levelling works across all open plans, but
this is not the case here.

Please let me know if that makes sense.

kraus

 

[Jan De Messemaeker]

Hi Kraus,

OK got a better insight now.
If your point is, once a project has been leveled the other projects
shouldn't move any task of it, then in Project Information for that Project
set a priority of 1000.
HTH

 

[Steve House [MVP]]

Nothing says that once a plan is leveled its dates are fixed in granite and
all other plans must work around them. Your particular business rules might
say that but Project makes no such assumption. Jan's suggestion on the
Project level priority setting is how you get Project to conform to your
needs in that regard.

 

[kraus]

I'll give that a try thanks.

Nothing says that once a plan is leveled its dates are fixed in granite and
all other plans must work around them. Your particular business rules might
say that but Project makes no such assumption. Jan's suggestion on the
Project level priority setting is how you get Project to conform to your
needs in that regard.