Leveling problems with Egg

[Dave]

1. Create generic enterprise resource 'Egg'
2. New project -> build team from enterprise -> add Egg
3. Create 3 tasks 1 day each and assign to Egg
4. Level project -> Tasks are leveled correctly
5. Save Project as EggProject1
6. New Project
7. Create 3 tasks 1 day each and assign to Egg
8. Level project -> Tasks are leveled correctly
9. Save Project as EggProject2
10. Level project -> Tasks are leveled but now occur 3 days later because
Egg is working on EggProject1

Bahh! But I haven't published any assignments yet!

This basically means that only 'Final' projects should go into Project
becuase draft resource assignments are taken into account even when they are
not yet published.

This is really really really REALLY annoying.

Dave

 

[Dale Howard]

Dave --

Projects saved in the Project Server database may include planned future
projects as well as production projects that are already underway. In
either case, the database is very useful for determining and leveling
overallocations in future time periods across all projects. That's the way
the the tool is meant to work.

The act of Publishing the project simply means that you are making the
project "available to the public" so that your executives can see the
project and your team members can see their assignments in PWA. Publishing
has little or nothing to do with leveling resource overallocations. Hope
this helps.

 

[Dave]

I think I kind of get it. As soon as you save a project to the server it's
resource allocations are saved and used when leveling also. Publishing
assignments only lets other know what their tasks are.

I guess I have to live with this but it is annoying there there is no way to
save to the server without the resource allocations being affected. I guess
this is why you use generic resources right?

Thanks again.

Dave

 

[Dale Howard]

Dave --

Yes, if you are using human resources (versus Generic resources) in a future
project plan, and you save the plan to the Project Server database, then
those resource allocations are saved in the database and are used in
determining resource overallocations. I think that is the way it should be,
since you would want to kow where your potential bottlenecks are in future
planned projects to make sure that you have enough resources.

If you are not absolutely certain who will work on a future planned project,
then as you said, it would be better to use Generic resources. I think you
are on the right path now. Hope this helps.