KPIs by Project Type (Dashboard)

The KPIs by Project Type (Dashboard) report displays the key performance indicators of status, schedule, alignment, and risk as gauges, with column charts of these key indicators by project type. Resource allocation and actual hours are summarized by project type and displayed in pie charts. An issue, risk, and change request bar chart displays the number of each by project type and priority.
ccppmop156
The KPIs by Project Type (Dashboard) report displays the key performance indicators of status, schedule, alignment, and risk as gauges, with column charts of these key indicators by project type. Resource allocation and actual hours are summarized by project type and displayed in pie charts. An issue, risk, and change request bar chart displays the number of each by project type and priority.
The following image displays the KPIs by Project Type report with status, schedule, alignment, and risk details.
The image displays the KPIs by Project Type report with status, schedule, alignment, and risk details.
Report Prerequisites
Verify that you have completed the following prerequisites before you run this report:
  • The
    Load Data Warehouse
    and
    Load Data Warehouse Access Rights
    jobs must be run before you run this report. If the Data Warehouse is not populated, the report displays a message that there are no matching records. Also, most of the report parameters do not display options.
    The charts in the report are grouped by the project type field on the projects. To make the groupings relevant, the project type field must be completed. If the project type field is not defined, the project types display in the report as Undefined.
  • The status is based on the most recent project status report so at least one status report must be completed on the projects for this indicator to calculate. The status report with the greatest report date and a report status of final, or no value selected for report status, is considered the most recent.
  • The business alignment and risk rating properties on the projects must be completed to calculate the alignment and risk indicators.
  • Projects must have team members with allocation amounts to calculate resource allocations.
  • Projects must have actual hours posted through timesheets, transaction entry, or imported into 
    Clarity PPM
    to calculate resource actuals.
Report Properties
The following values list the report properties.
Name:
KPIs by Project Type (Dashboard)
Resource ID:
CSK_PRJ_KPIsByProjectTypeDashboard
Description:
Project Management (PMO Accelerator)
Folder:
CA PPM/Reports/Project Management/KPIs by Project Type (Dashboard)
Path:
/ca_ppm/reports/project_management/CSK_PRJ_KPIsByProjectTypeDashboard
Data Source:
CA PPM Data Warehouse Bean Data Source
Report Parameter Options
The following table lists the report parameter options.
Prompt Text
Parameter Name
Type
Input Control Name
Input Control Resource ID
Mandatory
Default Value
Project OBS Type
projectOBSTypeKey_1
Single-select query
Project OBS Type
projectOBSTypeKey_1
No
Project OBS Unit
projectOBSUnitKey_1
Single-select query
Project OBS Unit
projectOBSUnitKey_1
No
Project Type
projectTypeKey_1
Multiple-select query
Project Type
projectTypeKey_1
No
Project Manager
projectManagerKey_1
Multiple-select query
Project Manager
projectManagerKey_1
No
Project Status
projectStatusKey_1
Multiple-select query
Project Status
projectStatusKey_1
No
Risk, Issues, or Change Requests
risksIssuesCRs
Single-select list of values
Risk, Issues, or Change Requests
risksIssuesCRs
No
Issues
Database Schema
dwhDBSchema
Hidden
Not applicable
Yes
Passed through
Clarity PPM
UI Theme
ppmUserUITheme
Hidden
Not applicable
Yes
Passed through
Clarity PPM
Language
ppmUserLanguage
Hidden
Not applicable
Yes
Passed through
Clarity PPM
User ID
ppmUser
Hidden
Not applicable
Yes
Passed through
Clarity PPM
Parameter Lookup Values
The following values list the lookup values.
Project Type
: Major Project, Application Change, Infrastructure Deployment
Risk, Issues, or Change Requests
: Risks, Issues, Change Requests
Parameter Explanations
The following list describes the parameters:
  • The Project OBS Type is a cascading parameter and determines which units are listed in the Project OBS Unit parameter. This parameter is not used to control which projects display in the report.
  • The Project OBS Unit parameter displays values that are based upon the Project OBS Type selected. When you select an OBS unit in this parameter, the report displays the projects that are attached to the OBS unit and descendants of the unit you select.
  • The Project Type parameter is associated to the Idea and Project Type lookup in
    Clarity PPM
    . This lookup is configurable so lookup values can be added, modified, or deactivated.
  • The project statuses are displayed based on the existing project statuses in the environment such as test, dev, or prod. For example, if there are projects with only Approved status, then only the Approved project status displays.
Report Fields and Calculations
The report includes gauge components that are combined with regular column charts showing KPI average values and percentage of projects with critical status, schedule late, high alignment and high risk, categorized by project type. Amounts and percentages of resource allocation hours and actual hours are represented in two pie charts. The report also includes a bar chart showing the distribution of high, medium, and low priorities of issues, risks and change requests, which are categorized by project type. Programs and templates are excluded. This report contains the following calculations:
  • Status
    . The gauge needle displays the average overall status (sum of overall status that is divided by number of projects). This value is taken from the overall status field from the project status report. The overall status is a calculated field in CA PPM that is the sum of the schedule status, scope status, and cost and effort status fields on the status report. Each of these fields is ranked as on track with a value of 10, minor variance with a value of 20, or significant variance with a value of 30. The gauge indicator displays the average overall status (sum of overall status that is divided by number of projects). The Gauge color is determined as follows:
    Green= On Track (< 40)
    Yellow= Minor Variance (>= 40 and < 90)
    Red Significant Variance >= 90
Database view and column:
dwh_inv_status_report.overall_status
  • Critical Status
    . This value is the percent of projects with significant variance, when overall status is greater than or equal to 90, grouped by project type.
  • Schedule
    . The gauge needle displays the average schedule (sum of schedule that is divided by number of projects). The schedule is the number of days the project is late and considers the following items:
    • Whether a baseline exists
    • Project progress
If a baseline exists, then days late is calculated as project finish date minus baseline finish date. A positive number indicates that the project is late according to the baseline. A negative number indicates that it is early according to the baseline.
If a baseline exists and the project finish date is the same as the baseline finish date, then the project is considered late if it is not completed and it was due before today's date. In this case, the number of days late is calculated as today's date minus project finish date.
If there is no baseline, then days late is calculated if the project is not completed and it was due before today's date. In this case, the number of days late is calculated as today's date minus project finish date. The Gauge color is determined as follows:
Green= On Schedule (<= 0)
Yellow= Between 1 and 10 Days Late (>0 and <=10)
Red= More Than 10 Days Late (>10)
  • Schedule Late
    . This value is the percent of projects with number of days the project is late greater than 10 days, grouped by project type.
  • Alignment
    . The gauge needle displays the average business alignment (sum of business alignment that is divided by number of projects). The alignment indicator is the business alignment field on the project. The business alignment field is calculated as an average of the alignment factors that are completed on the project. Each of the alignment factors is ranked as low with a value of 25, medium with a value of 50, high with a value of 75, or very high with a value of 100. The Gauge color is determined as follows:
    Green= Good Alignment (>= 68)
    Yellow= Average Alignment (>=34 and <68)
    Red= Poor Alignment (< 34)
Database view and column:
dwh_inv_investment.business_alignment
  • High Alignment
    . This value is the percent of projects with good alignment, when business alignment is greater than or equal to 68, grouped by project type.
  • Risk
    . The gauge needle displays the average risk (sum of risk that is divided by number of projects). The risk indicator is the risk field on the project. The risk field is calculated as the weighted average of the risk factors that are completed on the project. Each of the risk factors is ranked as low with a value of 0, medium with a value of 50, high with a value of 100. The Gauge color is determined as follows:
    Green= Low Risk (< 34)
    Yellow= Medium Risk (>=34 and <68)
    Red= High Risk (>=68)
Database view and column
dwh_inv_investment.risk
  • High Risk
    . This value is the percent of projects with high risk, when risk is greater than or equal to 68, grouped by project type.
Report Security
Security is determined by project view rights.
: Starting with Release 14.4, the default
Status Report Status
lookup values change from
Minor Variance
to
Needs Help
and from
Significant Variance
to
At Risk
. The
On Track
value remains the same. See the PMO Accelerator Release Notes in the 14.4 edition of the English documentation set.