The Role Capacity portlet allows filtering by role name and ID, Capacity OBS, Demand OBS, and Investment OBS.
The following describes how filtering works for the different OBS filter fields:
This filter field drives the capacity aggregations based on your named resources and your Resource OBS structures (such as team OBS or Location OBS). The Capacity OBS filter calculates the capacity of named resources who belong to the selected Resource OBS. You associate a resource with an OBS from the Resource Properties page.
This filter field calculates demand for the listed roles based on the following team staff member settings:
Note: If the Demand OBS filter field is left blank, the portlet displays all demand per other specified filtering criteria. Use the Include Named Resources drop-down in conjunction with the Demand OBS to calculate demand for roles only or to include named resources.
To effectively use Capacity and Demand OBS filtering, select a single Resource OBS Type for use in modeling capacity and demand. When assigning a Resource OBS Type for staffing purposes, use the same OBS Type for the Default Project Staffing OBS and the Staff Team Member Staffing OBS. You can use different branches of the OBS to represent capacity and demand for different areas of the company. The goal for using a Resource OBS for staffing is to be consistent when using the Resource OBS to filter both capacity and demand. Using the Staffing OBS settings at the project level and the team level allow you to see results that accurately reflect capacity and demand.
This filter field restricts the capacity and demand results to those investments assigned to the selected OBS. Only team staff members for the selected investments are reflected in the resultant table.
A role does not need to belong to a specific Resource OBS to be included in the demand metrics that show up on the Capacity Planning portlets. However, when adding the role to a team, you must set the Staffing OBS on the role's Properties page to further qualify the demand request for the role.
| Copyright © 2010 CA. All rights reserved. | Email CA Technologies about this topic |