Run Rate Widget

Modified on Thu, 24 Sep at 3:44 PM

The Run Rate Widget is a resource effort tracking tool. It displays how planned (Target), actual, allocated, approved, and requested person-time (and optionally cost) are trending over a configurable date range, month by month. Every label in the configuration screen — Target Person, Actual Person, Approved Person, Allocated Person, Requested Person, Month, and all their Cumulative counterparts — corresponds directly to a column in the widget's underlying data grid. When the widget is placed on a dashboard, those labels become the column headers in that grid (and legend labels in the chart).

image-20260826-153726.png

Where to Find the Run Rate Widget Settings

  1. Navigate to any Project Dashboard, Executive Dashboard, or Strategy Dashboard that has the Run Rate Widget placed on it.

  2. Click the gear / settings icon on the Run Rate Widget tile. This opens the RunRateSettings.aspx dialog.

Configuring the Widget (Settings Dialog)

Setting

What to do

Widget Title

Type a custom display name for the widget header. Max 100 characters. Required.

Show (swap-list)

Move items from the left "Available" list to the right "Selected" list to choose which data series appear. Options: Actual, Allocated, Approved, Delta, Requested, Target (always available), and — if the General Reporting Requirements feature is enabled — Actual Complete %, Actual Cost, Target Complete %, Target Cost.

Date Range

Pick a preset range (e.g., project duration, current year) or set custom From/To dates. Maximum span is 5 years from the To date. Both dates are required.

Show Cumulative Values

Tick to add the "Cumulative …" columns to the grid and chart legend.

Exclude Non-Production Task (if visible)

Tick to suppress tasks flagged as non-production in all calculations.

Display Time (if visible)

Choose FTE (person-months), Hours, or Days for all person-time figures.

Detail Display / Show Data By (if visible)

Switch between aggregating data by All Account Sub Groups, Specific Account Sub Groups, or Specific Account Codes.

Reading the Column Headers in the Configuration Screen

The left column labels (Target Person, Target Complete % Person, Target Cost, Actual Person, Actual Complete % Person, Actual Cost, Approved Person, Allocated Person, Requested Person, Month) and the right column labels (all the "Cumulative …" equivalents) are the grid column headers you will see when you expand the widget. They are drawn from the system's localisation catalogue and are displayed here so administrators can verify or adjust their translated names. They are not user-configurable input fields in a data-mapping sense — they represent the widget's internal schema.

Tips and Gotchas

  • Date range too large: If you select a span exceeding 5 years, the widget automatically clips the To date to 5 years from the From date. A warning banner appears: "Date range selected is too large".

  • Cumulative columns: The "Month" column appears only on the left (period) side; there is no "Cumulative Month" because the date label doesn't accumulate — this is why the right column ends at "Cumulative Requested Person" with no equivalent Month column.

  • "Target Person" vs "Target Cost": The "Person" suffix indicates a resource-effort figure (FTE months, hours, or days depending on the Display Time setting). "Target Cost" and "Actual Cost" are monetary values computed separately from planned and actual user cost records.

  • "Requested Person": This is derived automatically as Allocated – Approved, not a separately recorded value.

  • Show Cumulative must be on for the right-side Cumulative columns to appear in the live widget, even though they always appear in the configuration screen.

  • SCM values: If a Target/Planned figure comes from Strategic Capacity Management (SCM), the corresponding grid row shows a tooltip "Strategic Capacity Management Value" and a special CSS class.

  • To reset the date range to the system default, click the "Reset to Default Date Range" button on the widget itself (not in the settings dialog)

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article