Re: Month by month resource leveling results in overallocated reso

Hi,

Also see Steve's post on this.
Insofar Summary tasks don't have resources of their own, yes, their priority
is ignored (as is the priority of any task without resources)
HTH

--
Jan De Messemaeker
Microsoft Project MVP
http://users.online.be/prom-ade
"AprilPM" <AprilPM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E4B9EBA4-6654-49C7-BAA0-CBAD5862BA89@xxxxxxxxxxxxxxxx
No, good guess, but that's not it. I'm living with it as is. It's not
doing
exactly what I want it to do, as I am having to drop the priority to 500
to
get it to work, but it's close enough for what I'm trying to do.

I did a little experiment to try to figure out the rules about priority of
summary task vs. sub-tasks. Summary task A is a priority 900, summary
task B
is a priority 500 and has a sub task, Bsub1 that has a priority of 800,
and
summary task C has a priority of 700 with a sub task, Csub1 with a
priority
of 600. What will be the order of the tasks? It worked as I expected,
which
is it took the priority of the sub-tasks and seems to ignore the priority
of
the summary task. Is that your understanding of how this is supposed to
work? I was wondering if that was my problem, but it doesn't seem to be.
--
April


"Jan De Messemaeker" wrote:

Just a one-before-final guess.
Is "Level only within available slack" on? That may also explain it!
Greetz,

--
Jan De Messemaeker
Microsoft Project MVP
http://users.online.be/prom-ade
"AprilPM" <AprilPM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BFB252E-105B-4364-AE85-E68637370AB6@xxxxxxxxxxxxxxxx
"Can Level" is set to yes for all resources. I have a few "start no
earlier
than" constraints on some tasks, but no constraints on the task I'm
having
trouble with. No actuals are logged, no task is assigned higher than
the
maximum resource, and no summary tasks have resources allocated to
them.
That's very generous of you to offer to look at it. If nothing turns
up
in
the next few days, I may take you up on it.
--
April


"Jan De Messemaeker" wrote:

Hi,

There may be a number of reasons for the bad results of leveling in
this
case.
One you can check is insert the columln "can level" in the resource
***
and verify it is Yes for all resources.
I suppose you don't have compelling constraints such as Must
something?
They
stop any task form moving as well.
Your work isn't set to Actual is it? Actual work won't move
There are no tasks that have the reosurce allocated for more than its
max
units? That leveli,g can't resolve either
You haven't assigned a resource to both a task and its summary task?

Short of that, you may sent the file to jandemesAT prom-ade.be I'll
have
a
look.
--
Jan De Messemaeker
Microsoft Project MVP
http://users.online.be/prom-ade
"AprilPM" <AprilPM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C7347BBD-3DED-4129-8436-E88594280983@xxxxxxxxxxxxxxxx
I am having trouble with resource leveling. I'm using MSP
Professional
Desktop edition.
I have a resource, "software," who is available 500% (7.2 FTE's at
about
70%
utilization).
I have a number of in-process tasks that I don't want to affect, so
I
set
them to priority 1000.
Future tasks have various priority, all less than 1000.
I have "month by month" leveling set.
The leveling order set to "Priority, Standard."
All other checkboxes in "resolving allocations" are unchecked.
I "clear leveling," then "level now."
I would expect to see no more than about 860 hours per month for
this
resource after all the priority 1000 tasks are out of the way.
However, I see 1012 hours in January '08. In fact, December through
May
are
all over allocated with more than 900 hours (only December and
February
are
flagged as red, but I ignore the color.too deceiving.)
Upon investigation, I see that MSP has started a 900 priority task
which
requires a big portion of my "software" resource at this point in
time.
Why would it not wait until resourses are available?
(My tasks are very long in duration in this timeframe..many
months..I'm
doing a program-level "look-sie" at my organizations long-range
resource
forecast, so each "task" in this timeframe is in fact a "project."
The
Priority 1000 tasks are from currently committed and executing
projects.)
Any ideas about what's happening?
--
April








.