Leveling resources

[D. Albert]

Hi all,

I'm trying to "level resources", sounds great, but doesn't work the way I
want it to be. I got a recurring task of 2hrs every day on a resource, let's
say "DA". Now I know DA got a project that had to be finished on 2007/01/31
where she needs 16 hours for. So, my mind says that I got to start not at
2007/01/30 but already at 2007/01/29 to get it ready by end of january
(because of a calender saying DA got to work for 8 hours a day). But Project
is telling that it cannot resolve the overallocation... I tried similiar
features of the properties of project, so is there anyone who can help me?

Thanks,
D. Albert

 

[Jan De Messemaeker]

Hi,

If you define 2 hours a day as a task of 2 hours duration, resource @ 100%
you will get a proper result.
HTH

 

[D. Albert]

Hi Jan,

thanks so far for your answer, that worked a little bit better, but did not
solve the problem, now he's splitting nothing at all and tells that it can't
resolve any of the overallocations. But, what is curious at all: It is only
splitting when I leave the resource in the summary task, that combines all
the small tasks. If I handle it according to the errormessage and delete this
resource it's not splitting any more? Sorry, I'm a little bit confused...

Regards,
D. Albert

 

[Jan De Messemaeker]

Hi,
I suppose the "summary Task" is a recurrent task?
By all means, it is best to have the resources on the detail tasks.
They should have the highest priority (if you don't want them to move, 1000
is best); your leveling options should have "Leveling can split remaining
wiork" checked on
And the tasks to be split should NOT be fixed duration type.
Does that help?

HTH

 

[D. Albert]

Hi,

no, the "summary Task" is just something f.ex. named "maintenance 2007" and
includes now NO resources and NO Prio, they are on the detailed tasks. Prio
is done according to the Prio set to the tasks (highest 1000, lowest 0).
Leveling options are set to

- manual
- hour by hour
- Leveling order: Priority, Standard
- Level only within available stack
- Leveling can adjust individual assignment on a task
- Leveling can create splits in remaining work

I've looked through once again, now he's splitting a task of Prio 900
because of a task of Prio 600?!

Sorry, but I can't see any sense there :-(

What I really need: I got different task, what I know is the end date
(finish not later than) and a amount of hours I need for that (work), so the
task type is set everywhere on "fixed work".