Last week, I announced my intent to spend the next couple of weeks examining the Resource Analysis component of the Portfolio Analysis module in Project Server 2010. My general goal is to use an Excel spreadsheet I developed, which I will refer to as “The BHS” to demonstrate the various calculations within the Analysis module. “Why an Excel sheet?” you may ask. Because sometimes an abacus just won’t suffice.
Just to get you caught up on previous posts in this series:
Organizational capacity planning is the component of Resource Analysis that assesses the available resources and develops a timephased model of resource supply. To review the last post, this feature is governed by a couple of settings that are configured when the analysis is initially created:
Planning Horizon and Granularity – Specify the planning horizon and the level of planning granularity. Resource capacity data and project resource requirements outside the planning horizon will not be included. Projects that fall both within and outside the planning horizon cannot be moved, and only resource requirements data within the horizon will be considered.
This tells us the start and end dates for the capacity to be considered.
Resource role custom field – Each resource should be mapped to a primary role based on a preconfigured custom field. Specify the custom field representing the resource role here. Time-phased project resource analysis will be performed at a role-level.
This tells us how we will group the various resources to assess capacity.
Within the BHS, the capacity planning appears as follows on the Planning worksheet:
Note that this is assuming a monthly granularity as configured on the Analysis Settings page that we discussed in the last post.
In the Resource Analysis module, this view is evident in the Requirements Details view:
Whereas in the BHS, you can manually configure FTE quantities, Project Server is pulling the data from each resource and more specifically each resource calendar included within the system….and aggregating that data by the resource role field specified in the Analysis Properties screen.
It’s important to note that Project Server is pulling all resource data from the system – not just the resource data for resources with assignments in the given projects. This means that you must select all projects for the analysis that utilize the same shared resource pool. What happens if you don’t select all of the projects sharing a resource pool? Those projects that are not selected will still have their assignments decremented against the organizational capacity.
Here’s what that means in a nutshell:
1) I have one resource in a specific role.
2) That resource is assigned full time to two projects in the same timeframe.
3) One of those projects is selected as part of the analysis. The other project is not included in the analysis.
4) The capacity for that role will appear as 0 for the duration of the unselected project.
Here’s what that looks like in Project Server. You’ll note that for the duration of the unselected project, the capacity for Role1 and Role2 drops.
I’ll touch on this a bit more in my next post.
Coming up next: Baseline Resource Calculations