Project Status Detail

ccppmop158
The Project Status Detail report displays detailed information about the project team allocations, key milestones, risks, issues, and change requests, including the most relevant project indicators.
The following image shows the Project Status Detail report with team allocations, key milestones, risks, issues, and change requests.
Image displaying the Project Status Detail report with team allocations, key milestones, risks, issues, and change requests.
Image displaying the Project Status Detail report with team allocations, key milestones, risks, issues, and change requests.
 
This report runs numerous queries to retrieve the required  to populate the report and might result in many pages of data being displayed if filters are not applied. Avoid running this report wide open so that only reasonable amounts of data are displayed. If you do not do this, then you can experience performance issues.
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 status report indicators, status report update, key accomplishments, and upcoming activities are based on the most recent project status report. So at least one status report must be completed on the project for the indicators to calculate and for the information in the frames to be displayed. 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 project must have a team, milestones, risks, issues and change requests for those report sections to display data. Milestones must have the key task field checked to display in the report.
  • The project must have team members that are assigned to tasks with estimates to calculate labor hours.
  • The project must have actual hours posted through timesheets, transaction entry, or imported into
    Clarity PPM
    to calculate actuals and actual cost.
  • The project must have a baseline for baseline (hours or cost), projected effort variance, projected effort variance %, projected cost variance, and projected cost variance % to display data in the report.
  • The project cost amounts are dependent upon running the
    Update Cost Totals
    job. This job is available in the Actions pull-down on the task list or baseline list. The
    Update Cost Totals
    job runs the following: Runtime extraction of rates (calculates rates based on the matrix but does not populate the data mart rate table),
    Update % Complete
    job, and
    Update Earned Value and Cost Totals
    job. If you want to update costs across several projects instead of updating costs for only one project, run the
    Update Earned Value and Cost Totals
    job from the Reports and Jobs menu. The
    Update Earned Value and Cost Totals
    job from the menu is the same as the
    Update Cost Totals
    job in the Actions pull-down, except it updates all the projects meeting the parameter criteria instead of updating only one project.
Report Properties
The following values list the report properties:
Name:
Project Status Detail
Resource ID:
CSK_PRJ_ProjectStatusDetail
Description:
Project Management (PMO Accelerator)
Folder:
CA PPM/Reports/Project Management/Project Status Detail
Path:
/ca_ppm/reports/project_management/CSK_PRJ_ProjectStatusDetail
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 Manager
projectManagerKey_1
Multiple-select
Query
Project Manager
projectManagerKey_1
No
Project
projectKey_1
Multiple-select
Query
Project
projectKey_1
No
Project Status
projectStatusKey_1
Multiple-select
Query
Project Status
projectStatusKey_1
No
Work Status
workStatusKey_1
Multiple-select
Query
Work Status
workStatusKey_1
No
Amount Type
amountType
Single-select
List of Values
Amount Type
amountType
Yes
Hours
Risk, Issue, and Change Request Priority
riskIssueChangePriorityKey_1
Multiple-select
Query
Risk, Issue, and Change Request Priority
riskIssueChangePriorityKey_1
Yes
Low, Medium, and High
Risk, Issue, and Change Request Status
riskIssueChangeStatusKey_1
Multiple-select
Query
Risk, Issue, and Change Request Status
riskIssueChangeStatusKey_1
Yes
Open, Work in Progress, and Resolved
Include Inactive Projects?
includeInactiveProjects
Boolean
Include Inactive Projects?
includeInactiveProjects
No
Unchecked
Include Inactive Resources?
includeInactiveResources
Boolean
Include Inactive Resources?
includeInactiveResources
No
Checked
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:
Work Status:
Requested, Active, On Hold, Canceled, Complete
Amount Type:
Cost, Hours
Risk, Issue, and CR Priority:
Low, Medium, High
Risk, Issue, and CR Status:
Open, Work in Progress, Resolved, Closed
Parameter Explanations
The following list describes the parameters:
  • The Project OBS Type is a cascading parameter that determines which units are listed in the Project OBS Unit parameter. This parameter is not used to directly control which projects display in the report.
  • The Project OBS Unit parameter displays values based on 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 that you select.
  • The Work Status parameter is associated to the Work Status lookup in
    Clarity PPM
    . This lookup is configurable so lookup values might be added, modified, or deactivated.
  • The Amount Type parameter allows you to determine if the report displays amounts as cost or hours. When you select cost as the amount type, the report displays a section heading of (Cost) and displays the amounts as cost. When you select hours as the cost amount type, the report displays a section heading of (Hours) and displays amounts in hours.
    Cost
    –The report displays a (Cost) heading. The baseline, actual, ETC, EAC, and projected variance amounts are represented as cost.
    Hours
    –The report displays an (Hours) heading. The baseline, actual, ETC, EAC, and projected variance amounts are represented in hours.
  • 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 displays the project name, project ID, project manager, project type, goal, status, progress, project objective, stage, finish date, baseline finish date, days late, cost or effort amounts, and project indicators. The project indicators include: schedule to baseline, alignment, risk, issue, and change.
If the amount type parameter is set to cost, then the report displays the following columns: baseline, actuals, ETC, EAC, projected cost variance, and projected cost variance %. If the amount type parameter is set to hours, then the report displays the following columns: baseline, actuals, ETC, EAC, projected effort variance, and projected effort variance %. Programs and templates are excluded.
The report displays the status report date and status report update from the latest project status report and the following status report indicators: overall, schedule, scope, and cost and effort. The previous report date is from the prior project status report, based on report date. The status report indicator trending arrows compare the current status report to the prior status report. An upward pointing arrow indicates that the status has improved, a downward pointing arrow indicates that the status has gotten worse, and a right pointing arrow indicates that there is no change in status or there is no prior status report for comparison.
The project team information in the report includes resource name, project role, start, baseline start, finish, baseline finish, booking status, request status, allocation hours, actual hours, and ETC hours. Labor roles are also included. Equipment, expense, and material roles are excluded.
The key milestones in the report include project milestone name, ID, status, finish, baseline finish, days late, and schedule. Milestones are included but tasks are excluded.
The report also displays detailed information about risks, issues, and change requests. The risk information includes: risk name, ID, description, priority, probability, impact, status, response type, and target resolution. The issue information includes: issue name, ID, description, priority, status, and target resolution. The change request information includes: change request name, ID, description, priority, status, and expected close.
To align with the enhanced productivity introduced in the CA PPM 15.x New User Experience, we updated the 14.4 PMO Accelerator. Starting with Release 14.4 and higher, the following changes appear in report status lookups, portlets, and reports:
  • Green
    : On Track
  • Orange
    : Needs Help (the former default value was
    Minor Variance
    )
  • Red
    : At Risk (the former default value was
    Significant Variance
    )
The documentation may refer to the previous values, even in 15.x releases. This is intentional. The explanations are still valid for new and existing users. Existing users can verify how the subtle changes appear after an upgrade. New users can understand how the values relate to the magnitude of the variance. Also note that your values and display mappings may vary.
This report contains the following calculations:
  • Overall
    . This value is the overall status field from the project status report. The overall status is a calculated field in
    Clarity PPM
    that is the sum of the schedule status, scope status, and cost and effort status fields on the status report. The stoplight color is determined as follows:
    Green= On Track (<40)
    Yellow= Minor Variance (>=40 and <90)
    Red= Significant Variance (>=90)
    The trending arrow is determined as follows:
    Upwards= Overall Status better than the previous Overall Status
    Rightwards= No variance
    Downwards= Overall Status worse than the previous Overall Status 
Database view and column:
dwh_inv_status_report.overall_status
  • Schedule
    . This value is the schedule status field from the project status report. The schedule status is determined by the selection of the On Track, Minor Variance or Significant Variance status option. The stoplight color is determined as follows:
    Green= On Track 10
    Yellow= Minor Variance 20
    Red= Significant Variance 30
    The trending arrow is determined as follows:
    Upwards= Schedule Status is better than the previous Schedule Status.
    Rightwards= No variance
    Downwards= Schedule Status is worse than the previous Schedule Status.
Database view and column:
dwh_inv_status_report.sr_schedule_status_key
  • Scope
    . This value is the scope status field from the project status report. The scope status is determined by the selection of the On Track, Minor Variance, or Significant Variance status option. The stoplight color is determined as follows:
    Green= On Track 10
    Yellow= Minor Variance 20
    Red= Significant Variance 30
    The trending arrow is determined as follows:
    Upwards= Scope Status is better than the previous Scope Status.
    Rightwards= No variance
    Downwards= Scope Status is worse than the previous Scope Status.
Database view and column:
dwh_inv_status_report.sr_scope_status_key
  • Cost and Effort
    . This value is the cost and effort status field from the project status report. The cost and effort status is determined by the selection of the On Track, Minor Variance, or Significant Variance status option. The stoplight color is determined as follows:
    Green= On Track 10
    Yellow= Minor Variance 20
    Red= Significant Variance 30
    The trending arrow is determined as follows:
    Upwards= Cost and Effort Status is better than the previous Cost and Effort Status.
    Rightwards= No variance
    Downwards= Cost and Effort Status is worse than the previous Cost and Effort Status.
Database view and column:
dwh_inv_status_report.sr_cost_effort_status_key
  • Alignment
    . This value displays a stoplight based on the project business alignment, which is the average of the scores for each factor that is selected on the business alignment project properties. A higher value indicates better alignment. The stoplight color is determined as follows:
    Red= Poor Alignment (<34)
    Yellow= Average Alignment (>=34 and <67)
    Green= Good Alignment (>=68)
Database view and column:
dwh_inv_investment.business_alignment
  • Risk.
    This value displays a stoplight that is based on the project risk score, which is the combined risk level for the project based on all the selections made in the risk factors section of the risk rating project properties. A lower value indicates lower risk. The stoplight 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
  • Issue
    . This value displays a stoplight that is based on the highest project issue priority. The stoplight color is determined as follows:
    Green= All issues that exist on the project are low priority.
    Yellow= At least one medium priority issue and no high priority issue exist on the project.
    Red= At least one high priority issue exists on the project.
Database view and column:
dwh_inv_summary_facts.issue_high_priority_count
dwh_inv_summary_facts.issue_med_priority_count
dwh_inv_summary_facts.issue_low_priority_count
  • Change
    . This value displays a stoplight that is based on the highest project change request priority. The stoplight color is determined as follows:
    Green= All change requests that exist on the project are low priority.
    Yellow= At least one medium priority change request and no high priority change request exist on the project.
    Red= At least one high priority change request exists on the project.
Database view and column:
dwh_inv_summary_facts.cr_high_priority_count
dwh_inv_summary_facts.cr_med_priority_count
dwh_inv_summary_facts.cr_low_priority_count
  • Projected Cost Variance.
    The projected cost variance field is on the project and displays the variance between the EAC cost and baseline cost.
    Formula:
    ((ETC Cost + Actual Cost (ACWP)) - BAC Cost)
Database view and column:
dwh_inv_summary_facts.eac_base_cost_var
  • Projected Cost Variance %.
    The projected cost variance % field is on the project and displays a stoplight indicating the projected cost variance as a percentage of BAC cost. The Projected Cost Variance % stoplight color is determined as follows:
    Green= The EAC cost is less than or equal to the baseline.
    Yellow= The EAC cost is between one and ten percent over baseline.
    Red= The EAC cost is more than ten percent over baseline.
    White= No baseline data exists.
    Formula:
    (((ETC Cost + Actual Cost (ACWP)) - BAC Cost) / BAC Cost) * 100
Database view and column:
dwh_inv_summary_facts.eac_base_cost_pct
  • Projected Effort Variance.
    The projected effort variance field is on the project and displays the variance between the EAC effort and baseline effort.
    Formula:
    (EAC Effort – BAC Effort)
Database view and column:
dwh_inv_summary_facts.eac_base_hours_var
  • Projected Effort Variance %
    . The projected effort variance % field is on the project and displays a stoplight indicating the projected effort variance as a percentage of BAC effort. The Projected Effort Variance % stoplight color is determined as follows:
    Green= The EAC effort is less than or equal to the baseline.
    Yellow= The EAC effort is between one and ten percent over baseline.
    Red= The EAC effort is more than ten percent over baseline.
    White= No baseline data exists.
    Formula:
    ((EAC Effort – BAC Effort) / BAC Effort) * 100
Database view and column:
dwh_inv_summary_facts.eac_base_hours_pct
  • Days Late.
    Days late displays the number of days late considering the following:
    • Whether a baseline exists
    • Project progress or task status
    If a baseline exists, then days late is calculated as project or task finish date minus baseline finish date. A positive number indicates that the project or task 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 or task finish date is the same as the baseline finish date, then the project or task is considered late if it is not completed and it was due before today's date. In this case, days late is calculated as today's date minus project or task finish date.
    If there is no baseline, then days late is calculated if the project or task is not completed and it was due before the current date. In this case, days late is calculated as the current date minus project or task finish date.
    There is no calculation for resource assignments so the days late will not be populated. Schedule stoplight 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)
Database view and column:
dwh_inv_investment.days_late
Report Security
Security is determined by project view rights.