Task interruption after resource levelling

[Olaf Seidel]

Hi NG,

first I created a baseline, then I started controlling.

After entering actual working hours of a resource at a task, I started resource
levelling to get the finishing dates updated.

Result of this:
The task is interrupted for more than one year. :-(
In this time the resource is doing nothing, as can be seen in the resource table.

But there is still enough work to do in the task.
And there are many successor task for the resource - all defined "start as soon
as possible".

Does anybody know the reason of the interruption?
And how to avoid it?
But updating the finishing dates is important!


TIA

Olaf

 

[Jan De Messemaeker]

Hi Olaf,

First, have a look at the resource information.

Isn't this a profiles availability, in other words didn't you define the
resource as available from-to?
This may be a booby-trap because after the last period Project considers the
resource as no longer available.
In other words, obnce you enter anything in the contoures availability
table, the default for the periods non mentioned is 0% availability, not
100%

If it isn't this, it's something to do with your tasks. Maybe your resource
is allocated to a summary task?

Here there are so many possibilities that I have to suggest you send me the
file if you do not get out.

Because LEVELING IS NOT BUGGY, when it gives curious resoults it's because
you asked for it (be it innocently )

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620

 

[Mike Glen]

Hi Olaf,

Welcome to this Microsoft Project newsgroup

After entering the actuals, did you go to Tools/Tracking/Update
Project.../Reschedule uncompleted work to start after...?

FAQs, companion products and other useful Project information can be seen at
this web address: http://www.mvps.org/project/

Hope this helps - please let us know how you get on

Mike Glen
Project MVP

 

[Olaf Seidel]

Hello Jan, hello Mike,


thanks for your help.

I located the problem yesterday (but don't understand it):

I'm using a resource pool.
In the resource pool and in every connected project I found about a dozen copies
of the standard calendar.

The standard calendar itself was mixed up with non-working days, standard
working days and non-standard working days in a very ugly way.

After deleting all copies of the standard calendar everything was ok with the
calendar.

Now I recognized, that many tasks, which I defined as "start as soon as
possible" changed to "Don't start before" with some key date in 2049 and some
other strange years.

Setting them all back to "start as soon as possible" and some manually shifting
of tasks, everything looks well again.

Automatically calculating and levelling leads no longer to strange results.

If someone has an explanation for this behaviour of MSP, I would be appreciate
to hear about it.


Thanks to all, who taxed their brains.


Bye

Olaf

 

[Steve House]

Sure sounds like the file's been corrupted somehow. Do you have a backup?

 

[Olaf Seidel]

Hi Jan,

I've seen similar problems happening with P2000 non-SR1

Oh, sorry - bad beginner's mistake.
I forgot to tell you the environment.

I've MSP 2002 and Win2k SP3.

Do you really think, the SR version maybe a problem to MSP?


Bye

Olaf

 

[Jan De Messemaeker]

To the best of my knowledge there is no SR for 2002.

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620