Setting Up Project Portfolio Management

This section provides an overview of Project Portfolio Management options and discusses how to:

Establish system options and security.
Establish supporting data.
Establish portfolio analysis preferences.

Understanding Project Portfolio Management Options

You must establish the following options before you use the system to create and analyze project requests:

System options.
Supporting data.
User preferences for portfolio analysis.

System Options

The system options are application-wide settings that:

Establish the records that the system uses for department and account data.
Control how project request IDs are generated.
Define discount rates.
Define currency conversion rate types.
Define workflow options.
Define integration options.
Define the dimensions and measures available for portfolio analysis.
Identify which users can edit project request data.

Supporting Data

The supporting data that you define establishes:

Initiative types, which are used to map a specific type of project to a particular project owner.
Priority selections, which are used to rank the importance of project requests.
The database records that the system uses to determine the allowed departmental budget amounts for project requests.
The measures and dimensions that are available for use in project portfolio analysis.
Risk elements, which are used to categorize risks.
Milestones for project requests and risk elements.

User Preferences for Portfolio Analysis

These preferences establish the default business unit, scenario, fiscal year, and period that a user views when analyzing project portfolios, and any additional measures to include.

Establishing System Options and Security

To establish system options and security use the PPM Preferences (BC_GENERAL_PREF), Security (BC_PROJ_ROL_VW), and Privileges for Project Requests and Templates (BC_PROJ_ROL_ST) components.

This section discusses how to:

Define prompt tables for department and account data.
Define how the system generates project request IDs.
Define the discount rate.
Define the currency conversion rate type.
Specify workflow options.
Define integration settings.
Define dimensions.
Define security for project requests and templates.

Pages Used to Establish System Options and Security

Page Name	Object Name	Navigation	Usage
PPM Prompt Tables	BC_SETUP_PROMPT	Project Portfolio Management, Administration, PPM Preferences, PPM Prompt Tables	Specify which tables the system uses to prompt for department and account data.
Project Request ID Sequencing	BC_PM_OPTIONS	Project Portfolio Management, Administration, PPM Preferences, Project Request ID Sequencing	Specify how to generate project request IDs.
Discount Rate	PPK_DISC_RATE	Project Portfolio Management, Administration, PPM Preferences, Discount Rate	Specify the discount rate to use to calculate monetary values such as net present value and return on investment.
Conversion Rate Type	PPK_RT_TYPE	Project Portfolio Management, Administration, PPM Preferences, Conversion Rate Type	Specify which rate type the system should use to convert currency amounts.
Workflow Options	PPK_WF_OPTIONS	Project Portfolio Management, Administration, PPM Preferences, Workflow Options	Establish application-level workflow options for project request approvals.
Integration	PPK_PG_SETUP	Project Portfolio Management, Administration, PPM Preferences, Integration	Specify whether to integrate Project Portfolio Management with PeopleSoft Program Management.
Analysis Dimensions	PPK_DIM_LIST	Project Portfolio Management, Administration, PPM Preferences, Analysis Dimensions	Specify the fields to use as dimensions for portfolio analysis.
Security	BC_PROJ_ROL_ST_VW	Project Portfolio Management, Administration, Security	Review security for projects and templates by role and status.
Privileges for Project Requests and Templates	BC_PROJ_ROL_ST	Click Add Role or click a role name on the Security page.	Specify security for project requests and templates by role and status.

Defining Prompt Tables for Department and Account Data

Access the PPM Prompt Tables page.

Department Prompt Table

Select the name of the PeopleSoft record that contains department data.

The system uses this record as a prompt for valid department values on the Cost and Benefit pages of the Project Request component (BC_PROJ_REQUEST). It is very important to select the record that accurately depicts the department hierarchy as defined within the general ledger business unit. The record that you enter must be keyed by setID and contain a DESCR field.

Note. The system is delivered with the value DEPARTMENT_TBL in this field. Most organizations simply accept this value, which is the standard department record that is used in the PeopleSoft Enterprise Financial Management and PeopleSoft Enterprise Performance Management databases.

Account Prompt Table

Select the name of the PeopleSoft record that contains account data.

The system uses this record as a prompt for valid account values on the Cost and Benefit pages of the Project Request component. It is very important to select the record that accurately depicts the account hierarchy as it's defined within the general ledger business unit. The table must be keyed by setID and contain a DESCR field.

Note. The system is delivered with the value GL_ACCOUNT_TBL in this field. Most organizations simply accept this value, which is the standard account record that is used in the PeopleSoft Enterprise Financial Management and PeopleSoft Enterprise Performance Management databases.

Defining How the System Generates Project Request IDs

Access the Project Request ID Sequencing page.

Project Request ID Sequencing

Sequence Type

Specify how project request IDs are assigned. Options are:

Automatic Numbering: Select to have the system automatically generate unique project request IDs for new project requests by adding the project request ID prefix to the beginning of the next number in sequence after the value that appears in the Project Request ID Sequence field.

Manually Entered: Select to enter project request ID numbers manually when new project requests are created.

Project Request Prefix

Enter a prefix to use for project request IDs. The system appends the next available project ID sequence number to this prefix to generate project request IDs.

Use the Overrides grid to specify different prefixes for specific business units.

This field is unavailable for entry when the sequence type is set to Manually Entered.

Project Request Sequence

Enter the initial number to use for project request IDs that are automatically generated. This number increases by one when a new project request is created.

This field is unavailable for entry when the sequence type is set to Manually Entered.

Note. Although you can edit the Project Request Sequence field, you should not change it after project requests exist because doing so could cause project request ID conflicts. Also, project request IDs must be unique throughout the system, regardless of the business unit with which they are associated, to integrate with PeopleSoft Enterprise Project Costing.

Overrides

Complete this grid to specify different project request ID prefixes for individual business units. Sequence numbers increase by one across all business units; only the prefix can differ. This grid is unavailable for entry when the sequence type is set to Manually Entered.

Defining the Discount Rate

Access the Discount Rate page.

Discount% (discount percentage)

Enter the rate that the system can use to discount the project request cost and benefit amounts to calculate financial metrics. The system uses this rate when calculating the KPI values for present value of benefits, return on investment, and net present value.

Effective Date

The date upon which the discount percentage goes into effect. This enables you to change over time the rate at which the organization discounts cash flows.

Defining the Currency Conversion Rate Type

Access the Conversion Rate Type page.

Rate Type

Select the rate type to use for currency conversions.

Currency conversions apply to several pages: the Project Request component pages, the Portfolio Analysis page, and the Project Request Analysis by Department page.

See Also

Converting Currency

Specifying Workflow Options

Access the Workflow Options page.

Enable Workflow

Select to enable worfklow functionality for project request approvals. This workflow sends submitted project requests to the worklist of the person who is designated as the owner and approver on the project request based on the initiative type that the requester selects; the owner can then either change the approver to someone else or decide whether to approve, cost, return, or deny the request himself. Use the Workflow Options group box to activate additional workflow options.

Workflow Options

These options are active only when the Enable Workflow check box is selected.

Require Funding Department Manager approval

Select to additionally require funding department manager approval for project requests. The system first routes submitted project requests to the project request approver for review and approval. If the approver approves the request, the project request status changes to Operationally Approved, and the manager (the funding department manager) of each unique department ID that is specified on the Project Request component's Costs page receives the project request for approval. Requiring funding department manager approval means that both of these roles must approve the project request before the system changes its status to Approved and activates its corresponding program or project.

Note. If funding department manager approval is required, then every department needs to have a manager identified.

E-mail Notifications

Select one or more options to control when the system sends email notifications. Options are:

Notify when Project Request is submitted: Select to have the system send email notifications to the project sponsor and funding department managers when the project request is submitted.

Notify when Project Request is updated: Select to have the system send email notifications to the project sponsor and funding department managers when a project requester resubmits a returned project request.

Notify when Detail Plan is created: Select to have the system send email notifications to the project sponsor and funding department managers when a project manager clicks the Send to Project Request button on the Project Request Estimate Summary page in the Program Management application to update the project request's cost estimate.

Notify when Project Request is approved: Select to have the system send email notifications to the project owner, project sponsor, project requester, and project manager when the final required approver approves the project request.

Notify when Project Request is denied: Select to have the system send email notifications to the project owner, project sponsor, project requestor, and project manager when either a project approver or a funding department manager declines the request.

See Also

Approval Workflow

Defining Integration Settings

Access the Integration page.

Integration Setup

PeopleSoft Program Management Enabled

Select if you are also implementing PeopleSoft Program Management. When you select this check box, the system displays several fields on the Project Request component pages and the Project Approval page that are otherwise hidden.

Note. Portal node definitions must be defined for integration to work.

Current Portal

The values in these fields provide the information that is required for the system to link to the General Information page (PROJECT_GEN_01A) in Program Management from the Project Request page in Project Portfolio Management. This group box does not appear unless the PeopleSoft Program Management Enabled check box is selected. The default values for these fields are delivered as system data. You do not need to change them unless modifications have been made to Program Management that require that you to link to a page other than PROJECT_GEN_01A to view project data.

Market	Select the market category for the portal application.
Portal Name	Select the portal name.
Xfer Node Name (transfer node name)	Select the transfer node.
Menu Name, Component ID, and Page Name	Enter the names for the menu, component, and page to access when your users click the Project ID link on the Project Request page.

See Also

PeopleSoft Enterprise Portal Solutions PeopleBook: Enterprise Portal Application Technology

Enterprise PeopleTools PeopleBook: Internet Technology

Defining Dimensions

Access the Analysis Dimensions page.

Define the project request-related dimension fields that are available for use in portfolio analysis by inserting rows and selecting the field name. The dimensions that are defined when you use this page are the dimensions that are available for users to select when they use the Define Measures/Dimensions page to define their portfolio analysis dimensions.

Defining Security for Project Requests and Templates

Access the Security page.

Use the pages within this component to define which roles within an organization are able to edit project request templates and project requests based on their status.

This page lists currently defined roles and their assigned edit privileges for project request templates (the Template column) and for project requests that are in the following statuses: approved, pending, submitted, canceled, declined, returned, operationally approved (the Op. Appr. column). You can either add a role or modify an existing privilege definition.

Note. Use PeopleSoft security to limit access to this page to the appropriate users within the organization.

Add Role	Click to add a role and define its edit privileges. The role must already exist. You establish roles by using PeopleSoft security.
<Role Name>	Click a role name within the grid to modify its privileges.

Specifying Privileges

Access the Privileges for Project Requests and Templates page.

Edit Page

Select to permit this role to edit a project request when it has the status that is listed in the current row. When this option is not selected, the role has only view access.

Note. Use the delivered demo as a guideline for how you should establish edit privileges for the various roles that participate in the project request entry and approval business process. The key roles to consider emulating in the implementation are project requester, project owner, project manager.

Edit Project Request Templates

Select to permit this role to edit project request templates.

View Privileges for All Roles

Click to view a list of roles with defined privileges.

Delete Privileges of this Role

Click to delete this role's edit privileges.

See Also

Establishing Project Requests

Establishing Supporting Data

To establish supporting data, use the Department Budget Source (BC_PRBUD_FLT), Priority (PPK_PRIORITY_UPD), Initiative Type (PPK_INITYPE_TBL), Milestone (PPK_MILESTONE), Risk Elements (PPK_RISK_ELEMENT), and Measures and Dimensions (PPK_MSRS_DIM) components.

This section provides overviews of milestones and measures and dimensions, and discusses how to:

Define budget record data.
Define project request priorities.
Define initiative types.
Define milestones.
Define risk elements.
Define measures and dimensions.

Understanding Milestones

Milestones represent a significant task or activity in a project that must be accomplished on time or the project may be delayed or at risk. You define and maintain milestones independently from project requests and store them in a shared library by using the Milestone page. This enables an owner to be associated with each milestone that can differ from the project request owner. After a milestone has been defined, only the individual that is specified as the milestone owner can modify it. Two types of milestones exist:

Standard milestones.
Risk milestones.

Standard Milestones

This type of milestone provides a measurement of the progress of a project request. Typically, these milestones are used to indicate certain key tasks that must be achieved by a given date, and the person who is responsible. You associate these milestones with a project request by using the Project Request - Milestones page.

Risk Milestones

This type of milestone is used to track and measure identified risks (risk elements) that are associated with a project request. Their primary function is to affect the net score for the primary risk score group by considering the probability that they will occur on time and their status. You associate a risk milestone with a risk element by using the Project Requests - Risk Elements page. Risk elements are associated with the individual risk categories that make up the risk score group that indicates a project's relative risk.

You can define the level of confidence that a risk milestone will be completed on schedule as a percentage value between 0 and 100; this percentage is used when the system computes the project's net relative risk score. Optionally, you can have the system automatically update the probability that a risk milestone will occur based on changes to its status, start date, and due date by running the Update Milestone Probabilities Application Engine process. This option is set individually for each risk milestone when you establish the milestone.

Understanding Measures and Dimensions

The project request data that you can analyze by using the Portfolio Analysis component is determined by definitions that are established for measures and dimensions. These dimensions and measures are the data that is available to use for the various elements of portfolio analysis. Measures and dimensions are established at implementation and stored in a shared library that is available to all users. However, security is enforced when you are using the Portfolio Analysis component, and as a result, users view only the data to which they have been granted access. Also, you must specify how the system should aggregate (roll up) amounts at the summary node levels on the project portfolio tree.

Measures

Measures are numerical data that can be used in the Portfolio Analysis component. The data source for a measure must be a key performance indicator (KPI); either use the KPIs that are delivered with Project Portfolio Management, or define your own KPIs.

The Portfolio Analysis component uses a project portfolio tree to determine the project request data to view. When defining a measure, you must specify how the system should compute the values for summary nodes on the project portfolio tree by aggregating the values within a subordinate child node. Options are to either compute a weighted average of the values of the subordinate nodes (child nodes), or sum together the values of the subordinate nodes. If you use the weighted average method, you need to specify on which field the weighting is based; typically, implementations use estimated cost to evaluate the measure relative to a project request's costs.

You also need to define how the system should determine the assessment of KPIs at summary node levels of the project portfolio tree. The following options are available:

Best.

The assessment for a summary node is the highest-ranked assessment of the child node.
Most Often.

The assessment for a summary node is the most commonly returned assessment of the child node.
None.

No assessments are available for summary nodes.
Rollup Score.

The assessment for a summary node is the highest-ranked assessment that is received in the subordinate (child) node.
Worst Case.

The assessment for a summary node is the lowest-ranked assessment that is received in the subordinate (child) node.

If you use the Rollup Score option, you must complete the assessment grid to indicate the assessment rules to use. If you select Most Often, you need to indicate how to determine the assessment in the event that no particular assessment was received more frequently than any other.

Dimensions

Dimensions are non-numerical (character-based) data that can be used in the Portfolio Analysis component. The data source for a dimension must be one of the following columns from the project request database record: KPI assessment, investment type, owner/manager, project request ID, status. Dimensions enable you to analyze project requests by grouping them according to their dimension value. For example, you can view project requests by their initiative type, status, or any of the other valid dimensions.

To define an assessment-based dimension, which returns assessment results for a KPI, you also must specify the KPI for which to analyze assessments and the method by which the system determines the assessments at each summary node of the project portfolio tree.

Pages Used to Establish Supporting Data

Page Name	Object Name	Navigation	Usage
Department Budget Source	BC_PRBUD_FLT	Project Portfolio Management, Administration, Building Blocks, Department Budget Source	Indicate which database records contain budget data. This information is used to determine the departmental budget amount that is allowed for project requests.
Priorities	PPK_PRIORITY_UPD	Project Portfolio Management, Administration, Building Blocks, Priorities	Establish priority ratings to assign to project requests.
Initiative Type	PPK_INITYPE_TBL	Project Portfolio Management, Administration, Building Blocks, Initiative Types	Set up unique identifiers that map different types of project requests to specific project owners.
Milestone	PPK_MILESTONE	Project Portfolio Management, Administration, Building Blocks, Milestones Project Portfolio Management, Project Requests, Project Requests, Milestones Click Create New Milestone.	Establish milestones.
Risk Element	PPK_RISK_ELEMENT	Project Portfolio Management, Administration, Building Blocks, Risk Elements	Establish risk elements.
Define Measures/Dimensions	BC_PRJ_KPI_RULE	Project Portfolio Management, Administration, Building Blocks, Measures/Dimensions	Establish the data that is available to use when you are analyzing project portfolios.

Defining Budget Record Data

Access the Department Budget Source page.

Budget Data

Record (Table) Name	Select the database record that contains the budget ledger data.
Amount Field	Select the field within the budget ledger record that contains the budgeted cost amounts. Typically this is the account field.
Delete Department Budget Source	Click to delete the currently defined budget source.

Budget amounts are shown on the Variance Analyzer page and enable you to compare department budget amounts to estimated project costs.

(Optional) Filter Criteria

Complete the fields within the filter criteria grid to specify criteria by which to limit the accounts used for budget amounts. If you leave this grid blank, all accounts are used to generate the budgeted cost totals. However, the system selects only budget amounts that have a Project ID specified.

You should define your filter criteria to select the budget accounts that your organization uses for budgeting project-related expenses, such as labor, materials, travel, and so on.

Defining Project Request Priorities

Access the Priorities page.

To define priorities, insert rows as needed and enter a priority number and description for each priority. Five priority levels and their corresponding descriptions are delivered. The data that you define in this page is used as the source for the valid priorities that appear in the Priority drop-down list box on the Project Request page.

Defining Initiative Types

Access the Initiative Type page.

Initiative Type ID

Specify a unique identifier for the initiative type. Initiative types are categories that are used for the purpose of classifying the various types of projects within your organization. When you use the portfolio analysis page, you can analyze project requests based on their initiative type.

Owner ID

Select the individual that is associated with this initiative type.

When you create a project request that is associated with an initiative type, the system automatically populates the project request's Project Owner and Approver fields with the owner ID of the individual who is specified as the owner of the assigned initiative type.

Defining Milestones

Access the Milestone page.

Milestone Definition

Owner	Select the individual who is primarily responsible for this milestone. After a milestone is defined, only the owner can update it.
Status	Select the milestone's current status. Options are: Not Started, In Progress, Completed, and Canceled. When the Update Milestone Probabilities process runs, it evaluates the status.
Start Date	Enter the date on which the milestone begins. When the Update Milestone Probabilities process runs, it evaluates this date.
Due Date	Enter the date on which the milestone should be completed. When the Update Milestone Probabilities process runs, it evaluates this date.
Delete	Click to delete the current milestone from the system. You can delete only milestones that are not associated with project requests.

Risk Milestone

Risk Milestone

Select this option if the milestone is a risk milestone. Only risk milestones can be associated with risk elements; non-risk milestones can be associated only with project requests.

Probability Automatic Update

Select this option to enable the system to update the milestone's probability, based on the current milestone status, when the Update Milestone Probabilities process runs. If the probability does change, it impacts the primary risk net score of the associated project request.

This field is available for entry only when Risk Milestone is selected.

Probability of Occurrence (%)

Enter a value that indicates the probability that the milestone will finish on time. This field is available for entry only when Risk Milestone is selected. The Update Milestone Probabilities application engine process can also update this field.

Project Requests that Use the Milestone

This grid lists the project requests to which this milestone is assigned.

Project Request

Click a project request ID to access the Project Request page, where you can view the project request definition.

Establishing Project Requests

Defining Risk Elements

Access the Risk Element page.

Enter a description of the risk element. Risk elements are shared among all project requests. They categorize a type of a risk.

Defining Measures and Dimensions

Access the Define Measures/Dimensions page.

Dimension and Source Dimension

Select Dimension to return the value from a project request field, and then specify which field by making a selection from the Source Dimension drop-down list box. You establish the dimensions that are available for selection by using the Analysis Dimensions page.

The Assessment dimension source returns the assessment results of the KPI that is selected in the Source Measure field. If you select Assessment, then you must also complete the Source Measure field. If you are defining a dimension based on any other dimension source, no other fields are required and the remaining fields are unavailable for entry.

Project Count

Select this option to return the number of project requests. When this option is selected, the only other required fields are Description and ID. The remaining fields are unavailable for entry.

Source Measure

Select the KPI that serves as the source of the data.

This field is required when you are defining a measure or when you are defining a dimension that uses Assessment as the source dimension.

Rollup Using

Indicate how the system calculates the totals on summary-level nodes of the project portfolio tree. Options are:

Average: Select to compute an average of the values from subordinate nodes.

Sum: Select to add together values from subordinate nodes.

Weighting: Select to compute a weighted average of the values from subordinate nodes. If you select this option, you must also complete the Weighted By field.

Weighted By

Select the KPI on which to base the weighted average for summary-level node totals that use weighting.

This field is available for entry only when the Rollup Using field is set to Weighting.

Assess Using

Indicate the method by which the system determines the assessments at each summary node of the project portfolio tree.

Tie Breaker

Specify the assessment to assign if the assessments for summary nodes are determined by the most common assessment result and no single assessment was received more often than any others. This field is available for entry only when the Assess Using field is set to Most Often. Options are:

Best Case: Select to use the best assessment result.

Worst Case: Select to use the worst assessment result.

Assessment Rules

For measures that are assessed based on their rollup score, complete this grid to define how the system determines assessments by designating the range of values that receive a particular assessment. This is required for measures when the Assess Using field is set to Rollup Score .

Sequence	Enter a number to associate with each target rule. The rules are evaluated in ascending order based on this sequence number, not their order in the list. The row that contains the first true condition is used as the assessment. Leave intervals between your sequence numbers so that you can insert additional rules later, if necessary, without having to renumber each row.
Operator	Select the type of comparison (greater than, less than, and so on).
% of Target (percentage of target)	Select the percentage of the KPIs target value to which this rule applies.
Assessment ID	Select the assessment ID that is used when the condition is true.

Establishing Portfolio Analysis Preferences

To establish portfolio analysis preferences, use the User Portfolio Preferences (PPK_USER_PREFER) component.

This section provides an overview of the portfolio analysis preferences and discusses how to:

Define portfolio analysis defaults.
Specify additional measures for portfolio analysis.

Understanding Portfolio Analysis Preferences

Portfolio analysis preferences are set individually by each user, and establish:

The default business unit, scenario, portfolio tree, and time period to use for portfolio analysis.
Any additional measures to include.

These settings are associated with the user ID that is specified at login. These options enable users to control which data they view by default when they access the Portfolio Analysis component.

Pages Used to Establish Portfolio Analysis Preferences

Page Name	Object Name	Navigation	Usage
Portfolio Analysis Defaults	BC_PRJ_KPI_DFLT	Project Portfolio Management, Administration, User Portfolio Preferences, Portfolio Analysis Defaults	Specify, by user, the default business unit, scenario, portfolio tree, and time period to use for portfolio analysis.
Additional Portfolio Measures	PPK_ADDL_MSRS	Project Portfolio Management, Administration, User Portfolio Preferences, Additional Portfolio Measures	Specify, by user, up to four additional measures to view on the Portfolio Analysis page.

Defining Portfolio Analysis Defaults

Access the Portfolio Analysis Defaults page.

Specify the defaults to use for portfolio analysis. The system automatically displays the data from this business unit, scenario, and time period—using the specified portfolio tree—when you view the Portfolio Analysis page.

Business Unit	Select the default business unit to view.
Scenario	Select the default scenario to view.
Portfolio Tree	Select the default portfolio tree to view.
Current	Select to use the most recent assessment results.
Choose	Select to use the assessment results of a specified accounting period; select the specific fiscal year and accounting period.

Specifying Additional Measures for Portfolio Analysis

Access the Additional Portfolio Measures page.

Select up to four additional measures to include when analyzing project portfolios. These measures appear in the Additional Measures tab on the Portfolio Analysis page.

You establish measures by using the Define Measures/Dimensions page.

See Defining Measures and Dimensions.

Discount% (discount percentage)	Enter the rate that the system can use to discount the project request cost and benefit amounts to calculate financial metrics. The system uses this rate when calculating the KPI values for present value of benefits, return on investment, and net present value.
Effective Date	The date upon which the discount percentage goes into effect. This enables you to change over time the rate at which the organization discounts cash flows.

Edit Page	Select to permit this role to edit a project request when it has the status that is listed in the current row. When this option is not selected, the role has only view access. Note. Use the delivered demo as a guideline for how you should establish edit privileges for the various roles that participate in the project request entry and approval business process. The key roles to consider emulating in the implementation are project requester, project owner, project manager.
Edit Project Request Templates	Select to permit this role to edit project request templates.
View Privileges for All Roles	Click to view a list of roles with defined privileges.
Delete Privileges of this Role	Click to delete this role's edit privileges.

Initiative Type ID	Specify a unique identifier for the initiative type. Initiative types are categories that are used for the purpose of classifying the various types of projects within your organization. When you use the portfolio analysis page, you can analyze project requests based on their initiative type.
Owner ID	Select the individual that is associated with this initiative type.

Dimension and Source Dimension	Select Dimension to return the value from a project request field, and then specify which field by making a selection from the Source Dimension drop-down list box. You establish the dimensions that are available for selection by using the Analysis Dimensions page. The Assessment dimension source returns the assessment results of the KPI that is selected in the Source Measure field. If you select Assessment, then you must also complete the Source Measure field. If you are defining a dimension based on any other dimension source, no other fields are required and the remaining fields are unavailable for entry.
Project Count	Select this option to return the number of project requests. When this option is selected, the only other required fields are Description and ID. The remaining fields are unavailable for entry.
Source Measure	Select the KPI that serves as the source of the data. This field is required when you are defining a measure or when you are defining a dimension that uses Assessment as the source dimension.
Rollup Using	Indicate how the system calculates the totals on summary-level nodes of the project portfolio tree. Options are: Average: Select to compute an average of the values from subordinate nodes. Sum: Select to add together values from subordinate nodes. Weighting: Select to compute a weighted average of the values from subordinate nodes. If you select this option, you must also complete the Weighted By field.
Weighted By	Select the KPI on which to base the weighted average for summary-level node totals that use weighting. This field is available for entry only when the Rollup Using field is set to Weighting.
Assess Using	Indicate the method by which the system determines the assessments at each summary node of the project portfolio tree.
Tie Breaker	Specify the assessment to assign if the assessments for summary nodes are determined by the most common assessment result and no single assessment was received more often than any others. This field is available for entry only when the Assess Using field is set to Most Often. Options are: Best Case: Select to use the best assessment result. Worst Case: Select to use the worst assessment result.