WRK28 - Project/Portfolio Scheduled vs Actual Effort Analysis

Business Outcomes

• Project managers can analyze and understand the difference between planned resource demand and actual reported time in the context of their capacity by Project

Supporting Capabilities

• Time Reporting
• Project Planning and Scheduling

Report Performance Expectations

This report provides the user with very detailed data, at the named resource and activity level, with weekly (TIMEREPORT Period) pivoted columns. It is designed to be used at the project level to look at data for a single week. The design of this report means that, if executed with parameters that return a large volume of data then performance of the report will be slow, with potential time out issues. Large volumes of data will result if the report is run against a large portfolio and/or projects have large numbers of detailed activities, and/or large numbers of resources working on them and/or for a large time range. The detailed nature of this report (lots of rows and columns) means that table sizes can quickly exceed 1 million cells. This is well beyond any reasonable interpretation of the design intent of this report.

In order to address report execution performance issues identified in graphic-rich reports when executed through Report tiles, an alternative version of this report has been introduced in RPM Analytics Version 2.2.0. Two RDLs are now available;

• RPM-WRK28_v2_alt.rdl - This RDL has had all graphics removed from the Detail Table and replaced with text characters and background cell formatting. This is the RDL deployed by default by the installation process. This report will execute quickly and is recommended for larger portoflios/time horizons.
• RPM-WRK28_v2.rdl - This is the graphic-rich RDL that will execute slowly when accessed through a Report tile. It is recommended that this RDL is used with small portfolios/time horizons.

Summary Chart

This summary chart in this analytic, provides the project/portfolio manager with an overview of the weekly scheduled (planned) versus actual effort. Any work attribute, such as work type, customer, or project manager. Data is summarized for each Time Reporting (weekly) period.

The scheduled effort is snapshot of the reserves, allocations, and planned standard activities that were scheduled at the point at which the Progressing Engine is first run with a new Time Now.

This chart shows a visual representation of last scheduled effort vs the actual reported time, sliced by the selected attribute of your choice per period in the selected range.

Detail Table

The detail table shows resource and activity level detail for each time reporting period. The bars summarize the planned (blue) and actual (green) utilization (based on total resource capacity) for each activity. The variance indicates whether the actual time reported is less than or greater than the scheduled effort.

Columns for each week (Timesheet period), weeks shown are controlled by the First/Last Period Parameters.

Detailed Business Rules

• This report requires a specific version of the Progressing Engine (PE v2.0.0.6 or higher) to be installed and is therefore only available for customers using PVE 11.1 or higher with this version of the Progressing Engine. The report will show the following information if the installed version of the Progressing Engine is incompatible: TIME_PLANNED table is not installed. The newest Progressing Engine Version should be installed.

• Progressing Engine v2.0.0.6 to v 2.0.0.9
  In order for detailed weekly scheduled effort data to be captured by the Progressing Engine, for use in this report, the Progressing Engine must be executed incrementally through each Timesheet period/Time Now setting. If the Progressing Engine is executed only once per month and the Time Now is moved from the beginning of one month to the beginning of the next then detailed scheduled effort data will only be captured for the last Timesheet period in the month.
• Progressing Engine v2.1.0 and higher
  PE 2.1.0 was enhanced with the ability to capture planned effort by time period when progressing multiple periods at once. Time planned is now captured for each period, rather than as a total in the last period being progressed. This means if the customer “skips a week” and does not progress for each TImesheet period one by one then the data will still be saved for each Timesheet period progressed.

Report Parameters