This is a question that comes up pretty regularly….how do generic resources impact enterprise capacity in Project Server 2010?
Take this as an example. Let’s say that I have 5 named developers in my resource pool. As part of my enterprise processes, I would assign a generic developer to my projects until they get to a certain stage in the planning process. Then, I would replace the generic resource with a named resource.
The question always comes up however, if I have 5 named developers and 1 generic developer in my resource pool, does the system show them indeed as being 6 available resources? Or does it only show the 5 named resources?
To test this out, I fired up a blank environment (SP1, June 2011 CU) and threw in a couple of resources.
I have a generic work resource, and Bob, a named work resource.
Note that I also have my administrator account configured as a resource.
Let’s see what happens when I select the two new resources, and then review the Resource Availability screen.
I see that the generic resource does in fact contribute to the available capacity – and does in fact skew the results. Looking at this graphic, I’d conclude that I have two developers, even though I know I only have one real developer and one placemarker.
What happens if, when I create the resource, I set the Max Units to zero? Let’s take a look. I change the generic resource Max Units.
….then again take a look at the Resource Availability screen…
That’s starting to look more like what I was expecting. I see only a total of 40 hours / week for the resource pool – which means we’re counting Bob, but not our Developer.
So the moral of the story is that if you want generics to not count towards available resource capacity, you need to set their Max Units to zero.
What are the implications of setting resources to a Max Units of zero within Microsoft Project Professional though?
Microsoft Project Professional & Resources with Zero Units
So to play around with this, I create a new project, add my two resources to the pool, and assign them each to a single task. As could be predicted, my Developer shows up as overallocated immediately.
…which may not be a big deal. Maybe your company is ok with overallocated resources in this stage of planning and only looks to resolve overallocations once the named resources have been swapped into the plan, bring with them all of the the annoying holidays and vacation time that generic resources don’t have.
There’re a couple of tricks that you could use here if you really want to see if your generic is overallocated though. One of the tricks is to look at the Resource Graph for the resource and see if you can’t smooth the work out a little more evenly.
That at least lets you eyeball the work allocation for obvious issues.
The other trick is to go to the Resource Sheet and modify the Max Units temporarily for the generic resource.
See how my resource is no longer highlighted in red and therefore overallocated? That allows you to do a quick check to confirm that you haven’t really overallocated the resource in the project plan.
Since this is indeed an enterprise resource though, the change won’t last. The next time you close and reopen the file, the generic resource will be set back to a Max Units of 0.
Next up….the generic resource in Portfolio Analysis…