PPM_Demo and PPM CAPs

The purpose of the PPM_Demo and PPM Content Acceleration Packs (CAPs) is to provide a set of items (Scorecards, Contexts, KPIs, Metrics, and more) that automatically gathers information from across your enterprise to build key performance indicators (KPIs) related to PPM-related issues with OOTB data from Data Warehouse as well as Dashboard pages that display the relevant information. The CAPs include the Project Portfolio Management Perspectives. The CAPs provide broad and deep insight that should enable you to Align with Business Strategy, improve the Stewardship of IT Investment, Accelerate Agility, and Improve Project Execution. This CAP provides a 360 degree Project and Portfolio Managementview.

The PPM_Demo is based on data in .csv files that are part of the CAP package and PPM CAPs include data from data sources.

The relevant content pack is PPM. For details, see Integration with PPM.

ClosedUser Story

  1. Chris is the Project Management Officer of the IT Operation department. As part of his daily work, he’d like to log into the IT Business Analytics (ITBA) application to understand the overall performance of the projects and proposals within his organization and check if there is any critical issue on the table.

  2. He logs into ITBA and launches the PPM-PMO Overview page to view the latest updates of the overall business performance.

  3. Chris starts reviewing the PMO Scorecard and under the Project Management perspective, he notices that the status of Improve Project Execution objective is Red.

  4. To understand why the Improve Project Execution objective was not met, he clicks the objective and checks the related KPI in the KPI View Component. He notices that the reason for not meeting the Project Execution objective is due to poor performance of many of the KPIs.

  5. Chris decides to start his analysis with the Number of Delayed Projects KPI.

  6. He clicks the KPI in the KPI View component to view the historical trend of the KPI and check its forecast.

  7. He notices that lately, the behavior of this KPI got worse.

  8. The KPI granularity is Monthly. He wishes to find the specific day or week this KPI started to be breached. To do so, he clicks the Calendar icon and selects Weekly.

  9. The historical results of this KPI are now presented in a weekly resolution.

  10. He finds out the specific week when the KPI started to breach.

  11. Chris also noticed in the Forecast component that the KPI will continue to be breached in upcoming months and therefore understands that something needs to be done.

  12. He continues the drill down to understand which specific project is causing the delay.

  13. He clicks the KPI itself and selects Project Name to view a breakdown by projects.

  14. Once the component is refreshed with the new data, he changes its view of to Multiple Historical Trend to be able to compare between projects.

  15. He clicks each one of the projects listed in the legend and finds out that EPR Financial project is negatively affecting the main KPI result.

  16. Chris writes an annotation to Daniel, the owner of the EPR Financial project in the organization, requesting some clarifications.

  17. Daniel receives an email from Chris regarding the problematic KPI. He logs on to the ITBA application, checks the same KPI, and sees that indeed the project has been delayed over and over again during the past few months .

  18. Daniel sets a meeting with his team to find out why the project was delayed and together they write a plan to overcome the issues.

  19. He writes an annotation back to Chris stating that a plan was set to avoid delays and that Chris will see an improvement very soon.

ClosedPPM_Demo and PPM

User interface elements are described below (when relevant, unlabeled elements are shown in angle brackets):

UI Element

Description

Pages

PPM-PMO Overview Page

PPM-Project Portfolio Management Overview Page

Scorecards
  • PMO
  • ProjectPortfolioManagement
Business Contexts
  • PPM_Demo
  • PPM_Demand Management
  • PPM_FinancialManagement
  • PPM_ProjectPortfolioManagement

For details, see Semantic Layer - Contexts and Universes.

KPIs and Metrics

Note The Demo CAP includes KPIs with names followed by (Demo). The CAP includes the same KPIs with names that do not include (Demo). The KPIs are the same but have different names so that both the Demo CAP and the CAP can be activated at the same time.

  • Average Age of Active Demands KPI. The average age of active demands that are currently waiting for approval during the measurement period.

  • Average Age of Active Proposals KPI. The average age of active proposals that are currently waiting for approval during the measurement period.

  • Average Project Delivery Time KPI. The average project delivery time of new products/services defined as the time it takes from the conception of a project until it is delivered to customer (EndDate and StartDate used in this KPI. formula).

  • Average Project Initiation Time KPI. The average time it takes to initiate a project (until all resources are assigned and the planning is completed) during the measurement period.

  • Average Time to Evaluate Project Scope Change KPI. The average duration of the project scope changes from the time they are opened to the time they are closed during the measurement period.

  • Average Time to Evaluate Proposals KPI. The average duration of proposals from the time they are opened to the time they are closed during the measurement period.

  • Capex vs Opex Project Spending KPI. The capitalized expense relative to the operational project expense during the measurement period.

  • Demands Backlog KPI. The number of open demands.

  • Deviation of Planned Work Hours KPI. The sum of the actual effort and the remaining estimated effort, relative to the planned effort for project tasks started during the measurement period.

  • Number of Delayed Project Tasks KPI.

    The number of projects tasks that were delayed during the measurement period.

  • Number of Delayed Projects KPI. The number of projects that were delayed during the measurement period.

  • Number of Unhealthy Projects KPI. The number of projects that became unhealthy during the measurement period.

  • Percentage of Actual vs Planned Projects Cost KPI. The actual project costs relative to the planned project costs during the measurement period.

  • Percentage of Approved Project Scope Changes KPI. The number of scope changes that were approved relative to the total number of scope changes that were closed during the measurement period.

  • Percentage of Change in Project Cost KPI. The change in the cost of projects during the last period relative to the change in the cost of projects during the previous period.

  • Percentage of Healthy Projects KPI. The number of healthy projects relative to the total number of projects that are ongoing in the current month.

  • Percentage of Project Tasks on Time KPI. The number of project tasks completed on time relative to the total number of project tasks completed during the measurement period.

  • Percentage of Projects on Time KPI. The number of projects completed on time relative to the total number of projects that were completed during the measurement period.

  • Project Issue Backlog KPI. The number of open project issues.

  • Project Risk Backlog KPI. The number of open risks.

  • Project Scope Change Backlog KPI. The number of open scope changes.

  • Project Task Backlog KPI. The number of open project tasks.

  • Proposal Backlog KPI. The number of open proposals.

  • Total Actual Cost of Projects KPI. The total actual cost of projects during the measurement period.

  • Total Planned Cost of Projects KPI. The total planned cost of projects during the measurement period.

Data (External Tables)
  • PPM_Demo

ClosedPPM-PMO Overview Page

ClosedPPM-Project Portfolio Management Overview Page