- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
57m ago
Use Case: Automating SPW Goal Progression with Target Automation via Benefit Plans
In this article, we’ll be walking through how to automate goal progression within Strategic Planning by using a scripted Target Automation Source that allows to easily connect benefit plan progression of aligned items with a given target/parent goal.
Contents:
- How the automation works for the end-user
- How are the calculations running exactly
- Do you need to understand how the Goal Framework for SPM works? You should go through this great walkthrough/demonstration by the product team: Youtube: Strategic Planning Workspace: Strategy and Goals.
- Do you need to understand how target automation sources work and how to build your own? You’re encourage to go through our previous article on this topic: Example: Automating SPW Goal Progression with Target Automation.
Disclaimer: The specific solution described is achieved through configuration. There is no liability for ServiceNow to provide support, apply changes, fix defects and review impact during future upgrades for the specific use-case that we provide in this article.
How the automation works for the end-user
We’ve made a short video demonstration showing how the end-user experience is on using the Benefit Plan automation of this article:
Some important takeaways:
- Only benefit plans attached under aligned planning items to the current target or parent goal are included in the calculations.
- There is no need to adjust any settings – you simply turn on actual value automation and pick up the Benefit Plan target automation source.
- Additional Conditions and/or Aggregation options are available for further configuring which specific benefit plans may be included in the final calculation and/or how the actual values (in case of multiple benefit plans) are aggregated into one value for the target.
How are the calculations running exactly
The automation is built for convenience and light user interactions. First, we start by pinpointing which benefit plans are included for the calculations for a given target. Multiple variables affect this:
- First, we filter the benefit plans under aligned Planning Items to the current target or parent goal.
- Then, we filter the benefit plans depending on the Unit of measure for the given target:
- Currency filters Monetary Benefit Plans only.
- Count filters Non-Monetary Benefit Plans of measure
CountorScore - Days filters Non-Monetary Benefit Plans of measure
DaysorHours - Percentage filters Non-Monetary Benefit Plans of measure
Percentage
- Then, a filter is applied based on the fiscal period; only benefit plans that are taking place within a current fiscal period are taken into consideration and the rest are filtered out from the calculation.
- The last filter is optional and user-driven. That’s the “Additional Conditions” variable that is available and may be used to apply further filters on top of the ones applied automatically above. E.g. we might have a “Currency” type target that only needs to fetch Monetary Benefit Plans of subcategory “Revenue” .
Of course, after filtering out the relevant benefit plans, this might still get us more than one relevant benefit plans. In that case, we aggregate the results. By default, a SUM aggregation runs, adding together all actual values collected from the different benefit plans into one value for the target.
The “Aggregation” variable is also available for the end-user to change this aggregation to AVG, MIN or MAX depending on the target and the desired result.
We must also review what value of each benefit plan is aggregated. It differs based on the type of the benefit plan and the Check-in frequency of the target itself.
Monetary Benefit Plans
For monetary Benefit Plans we always collect the Actual Benefit (actual_benefit) value from the breakdown record that corresponds to the current date. This is straight forward when we use an update frequency for the target of Monthly, Fortnightly, Weekly or Daily.
However, when using a Quarterly or Yearly frequency, the calculation makes one more step. It sums up all the breakdown actuals for the given Fiscal Quarter or the given Fiscal Year. In the case that we have a Quarterly frequency with a 13-period fiscal calendar (where we have no definition of fiscal quarters) the current calendar quarter is used.
Non-Monetary Benefit Plans
For non-monetary benefit plans, the calculation is more straight-forward. We always use the Non-monetary actual benefit (nm_actual_benefit) value of the Benefit Plan record itself. This is to allow for the aggregation options that exist OOTB (Aggregation mode field on Benefit Plan records) on the Non-Monetary benefit plans to apply before us picking an actual value – that is already done at the benefit plan record itself – thus why we rely on it.
Examples
Let’s run two quick examples to understand how the calculations run. Let’s assume we have a Goal and a Target. Let’s also assume two Projects aligned with the target or goal with the following Benefit Plans:
Project 1
Monetary Benefit Plan 1.1
Subcategory: Cost Savings
Breakdown Values:
| Fiscal Period | FY26: M10 | FY26: M11 | FY26: M12 |
|---|---|---|---|
| Actuals | 1000 | 1500 |
Monetary Benefit Plan 1.2
Subcategory: Cost Savings
Breakdown Values:
| Fiscal Period | FY26: M01 | FY26: M02 | FY26: M03 |
|---|---|---|---|
| Actuals | 5000 | 5000 | 6500 |
Monetary Benefit Plan 1.3
Subcategory: Revenue
Breakdown Values:
| Fiscal Period | FY26: M10 | FY26: M11 | FY26: M12 |
|---|---|---|---|
| Actuals | 20000 | 30000 |
Project 2
Monetary Benefit Plan 2.1
Subcategory: Cost Savings
Breakdown Values:
| Fiscal Period | FY26: M10 | FY26: M11 | FY26: M12 |
|---|---|---|---|
| Actuals | 500 | 600 |
Non-Monetary Benefit Plan 2.2
Subcategory: Process Efficiency
Measure: Percentage
Breakdown Values:
| Fiscal Period | FY26: M10 | FY26: M11 | FY26: M12 |
|---|---|---|---|
| Actuals | 10 | 15 |
Scenario 1
Now, let’s assume that the aligned target is of type “Currency” and set to “Monthly” frequency with Start/End dates: 01/10/2026 – 31/12/2026.
When we run the calculation at 30/11/2026, without setting/changing any of the default variables/values we’ll get:
Target Actual = (1500) + (5000) + (30000) + (600)
Scenario 2
Now, let’s assume that the aligned target is of type “Currency” and set to “Quarterly” frequency with Start/End dates: 01/10/2026 – 31/12/2026.
When we run the calculation at 30/11/2026, without setting/changing any of the default variables/values we’ll get:
Target Actual = (1000+1500) + (5000+5000+6500) + (20000+30000) + (500+600)
= (2500) + (16500) + (50000) + (1100)
Scenario 3
Now, let’s assume that the aligned target is of type “Currency” and set to “Quarterly” frequency with Start/End dates: 01/10/2026 – 31/12/2026.
When we run the calculation at 30/11/2026 while changing the “Aggregation” option to MIN
Target Actual = (1100)
Scenario 4
Now, let’s assume that the aligned target is of type “Currency” and set to “Monthly” frequency with Start/End dates: 01/10/2026 – 31/12/2026.
When we run the calculation at 30/11/2026, without changing the “Aggregation” (keeping it SUM) but by setting a filter condition “Subcategory = Revenue OR Work = Project 2”):
Target Actual = (30000) + (600)
Summary
This article describes a Target Automation Source that was build out of some specific use-cases we’ve seen in some customers. An update set is attached under this article to allow customers/partners to have a head-start when trying to build target automations around benefit plans. While the target automation source is fully functional, please remember to treat this as an additional configuration and not as an official component provided by ServiceNow.