SPM articles articles

Demystifying ServiceNow SPM Investment Funding: A Three Tier Governance Approach

Bill Martin — Mon, 22 Jun 2026 11:04:05 GMT

Managing budgets from the bottom up at the project level breaks down once your ServiceNow PPM footprint scales. Discover how to layer the Investment Funding module on top of standard PPM to build a clean, three tier governance structure that bridges the gap between top down enterprise finance and execution teams.

Demystifying ServiceNow SPM Financials: Bottom-Level Budget Approvals & Portfolio Rollups

Bill Martin — Mon, 22 Jun 2026 08:56:13 GMT

Discover how bottom-level cost plans, CapEx/OpEx allocations, and monetary benefits seamlessly roll up to portfolio targets in ServiceNow SPM.

Tell Us What's Working (And What Isn't) With SPM AI. Your Story Matters and we want to hear it !

MahatmaK0342012 — Fri, 19 Jun 2026 03:52:47 GMT

Tell Us What's Working (And What Isn't) With SPM AI. Your Story Matters and we want to hear it !

Project Q&A: Turn Questions into Instant Answers with 'Ask Now Assist' in Project Workspace

Vibha Sharma — Tue, 09 Jun 2026 08:44:35 GMT

Project Q&A: Turn Questions into Instant Answers with 'Ask Now Assist' in Project Workspace

AI Identified Risks in Project Workspace

Vibha Sharma — Mon, 08 Jun 2026 06:11:38 GMT

AI Identified Risks in Project Workspace

SPM/ Project workspace financial calculations and rollup flows

Md Asim Khan — Wed, 27 May 2026 12:55:50 GMT

Most engineers working on ServiceNow SPM can tell you what "Actual Cost" means. Far fewer can tell you where it comes from, why it can be zero with approved timesheets, or why demand actuals have no cost plan traceability while project actuals do.

This article covers the five financial data flows (planned cost, planned benefit, actual cost, budget, actual benefit), the exact tables and business rules behind each, breakdown types, budget v1 vs v2, baselines, and formulas for NPV, IRR, EAC, and ETC — all verified against platform source code.

SPM/Project Workspace Financials — System Properties Reference Guide

Md Asim Khan — Wed, 27 May 2026 12:50:47 GMT

A complete reference for the system properties that control SPM and Project Workspace financial behavior — covering budget allocation models, cost rollup, actuals processing, demand currency setup, and multicurrency configuration.

Share Your Resource Management Challenges

Vinitha Chukkala — Tue, 19 May 2026 20:55:40 GMT

Your feedback shapes our priorities. While the Resource Management customer feedback sessions have given us valuable insights, we want to make sure every voice is heard — not just those in the room.

If you're running into friction managing resources in SPM, we'd like to know. The information you share will be used to update our assumptions and inform what we work on next.

Please share your thoughts using the below survey

➡️ Resource Management - Mentimeter Survey

Anonymous Survey - You don't need to provide your name or email unless you'd like us to follow up with you.

Thank you!

Register Today! 2026 September SPM Vision Series - Roadmap, Customer Stories & much more...

Vinitha Chukkala — Tue, 12 May 2026 17:40:41 GMT

Strategic Portfolio Management Vision Series – September 2026

The pace of change isn’t slowing down — and neither should your strategy. Whether you’re navigating budget pressure, competing priorities, or the push to do more with AI, the SPM Vision Series is built for leaders and practitioners who need their plans to hold up in the real world. Join us this September for a live webinar packed with product direction, real-world success stories, and direct access to the SPM team

What’s on the agenda

Keynote by Yoav Boaz, GVP and GM, Strategic Portfolio Management
SPM product vision & roadmap presented by Carina Hatfield, Sr. Director, Inbound Product Management, and Lillian Yang, Sr. Manager, Inbound Product Management, CWM
Real-world success stories from leading organizations on achieving strategic outcomes with SPM
Live Q&A and key insights from the SPM Product Team
Sneak peek at upcoming events and resources

Register for your region

Select the session that works best for your time zone.

🌎 AMS / EMEA

September 17th, 2026

8 am PT | 11 am ET | 3 pm GMT | 4 pm CET

● Live session with Q&A

🌎 ANZ

September 18th, 2026

8:00 am AEDT | 10:00 am NZDT

● Recording with live Q&A

🌎 Asia

September 13th, 2026

8:30 am IST | 11:00 am SGT | 12:00 pm JST

● Recording with live Q&A

Can't make it live? Registered attendees get access to post-event resources shared exclusively.

If you any questions, drop them in the comments below or reach out to the SPM community team. We look forward to seeing you there.

Project Workspace: Introducing AI Project Plan and Task Generation

HayleyAlexander — Tue, 12 May 2026 15:00:04 GMT

Building a project plan and creating tasks is one of the most time-consuming parts of a Project Manager's week. Pulling together a WBS, sequencing tasks, updating project details, and creating templates — it's foundational work, but it's also the kind of work that pulls you away from the strategic conversations that actually move projects forward.

That's about to change. We're excited to announce Project Plan Generation using AI!

With Project Plan Generation, you can uploaded documents/multiple documents and the Planning Agent does the heavy lifting:

Generates project details (description, name, start/end dates)
Creates a WBS structure
Generates Tasks, Sub-tasks, child-tasks
Identifies start and end dates across the project
Returns a ready-to-refine plan inside your existing Project Workspace

Everything is proposed for your review before it commits to your workspace. You stay in control of the plan. The agent handles the setup.

Two ways to generate a plan

We've built this to meet you where the work starts:

1. Generate from uploaded documents. Upload one or more documents — SOWs, scoping docs, kickoff briefs, proposals — directly into a new project, and generate the plan from the content. No retyping, no rebuilding what's already been scoped.

2. Generate from a demand. If your project originates from a demand record, you can generate tasks within the actually project once its fully converted over.

Both paths land you in the same place: a structured project ready to refine, not a blank workspace.

Why we built it this way

Creating and structuring projects is the part of project management that pulls Project Managers away from the work that actually matters — managing stakeholders, navigating risk, driving outcomes. Project Plan Generation is built to give that time back.

This is one step in a broader set of AI capabilities coming to Project Workspace. More is on the way, and your feedback shapes what we build next.

Let's connect — 1:1 demo and feedback session

If you'd like to see Project Plan Generation in action and discuss it with me directly, I'd love to set up a 30-minute session.

In that time, we'll:

Walk through a live demo of both generation paths
Test the feature against a real planning scenario from your world
Discuss what's coming next for Project Workspace
Capture your feedback directly into our roadmap

Drop a comment below or send me a direct message to schedule. Your input at this stage genuinely shapes where we take this next.

Hayley Alexander, Inbound Principal Product Manager

What Project Insights Detects — Risks & Actions (RIDAC), Financials and Schedule

Vibha Sharma — Wed, 29 Apr 2026 05:50:23 GMT

Overview

This article outlines all the topics detected by the Project Insights engine, focusing on Risks & Actions (RIDAC), Financials, and Schedule. For each topic, it explains what is monitored, when an insight is triggered, the default thresholds, and the value it provides to your project team.

How to Read This Guide

Each insight topic includes:

What it does — A plain-language description of what the insight monitors
When it fires — The specific conditions that trigger the insight
Default configuration — Out-of-the-box thresholds and parameters
Data scope — The date range or project scope used
Severity — How urgency is communicated (where applicable)
Value delivered — What problem it solves for your team

Summary of Topics Covered

Risks & Actions (RIDAC)

These insights ensure that risks, actions, issues, decisions, and change requests logged in your project register are never forgotten after they are raised. Each topic keeps the relevant open items visible and prioritised.

1. Open Risks

Summarises all open project risks grouped by their potential impact.

2. Open Issues

Surfaces all open project issues organised by priority.

3. Open Actions

Tracks outstanding action items that have not yet been completed.

4. Open Decisions

Highlights decisions that are pending or have not yet been made.

5. Open Change Requests

Surfaces unresolved change requests that may affect project scope or timeline

Financials

Financial insights monitor the cost health of your project, comparing what you planned to spend against what is actually being spent and flagging drift before it becomes a serious problem.

6. Cost Variance Issues

Alerts when actual project costs are diverging from the plan.

7. Budget Variance Issues

Identifies when projected total spend is exceeding the approved budget.

Schedule

Schedule insights compare your current project timeline against the committed baseline, giving you and your stakeholders a clear, objective measure of delivery performance.

8. Schedule Variance

Shows how the current project timeline compares to the original baseline.

Final Note

These insights help shift project management from reactive tracking to proactive risk management, keeping your RIDAC register, financials, and schedule health visible and actionable at all times.

Related Articles

What Project Insights Detects — Resource Management

Vibha Sharma — Wed, 29 Apr 2026 05:53:28 GMT

Overview

This article outlines the topics detected by the Project Insights engine, focusing on Resource Management. For each topic, it explains what is monitored, when an insight is triggered, the default thresholds, and the value it provides to your project team.

How to Read This Guide

Each insight topic includes:

What it does — A plain-language description of what the insight monitors
When it fires — The specific conditions that trigger the insight
Default configuration — Out-of-the-box thresholds and parameters
Data scope — The date range or project scope used
Severity — How urgency is communicated (where applicable)
Value delivered — What problem it solves for your team

Summary of Topics Covered

Resource Management

Resource insights give you visibility into the people dimension of your project — who is overcommitted, who has spare capacity, who might become unavailable, and where cross-project conflicts are developing.

1. Resource Overallocation

Identifies team members committed to more work than their capacity allows.

2. Resource Underutilisation

Highlights team members with significant available capacity.

3. Resource Unavailability Issues

Flags unassigned resource assignment records where no matching resource is available to fill the role.

4. Unplanned Absence Issues

Detects when unplanned time off is consuming a significant portion of a resource's allocated hours.

5. Resource Conflicts

Detects team members being pulled across multiple projects simultaneously.

6. Contract Resource Issues

Warns when contractor or vendor contracts are nearing expiry.

Final Note

These insights help shift resource management from reactive tracking to proactive risk management, keeping your team's capacity, availability, and conflicts visible before they affect delivery.

Related Articles

What Project Insights Detects — Tasks & Milestones

Vibha Sharma — Wed, 29 Apr 2026 05:26:32 GMT

Overview

This article outlines all the topics detected by the Project Insights engine, focusing on Task Management and Milestones. For each topic, it explains what is monitored, when an insight is triggered, the default thresholds, and the value it provides to your project team.

How to Read This Guide

Each insight topic includes:

What it does — A plain-language description of what the insight monitors
When it fires — The specific conditions that trigger the insight
Default configuration — Out-of-the-box thresholds and parameters
Data scope — The date range or project scope used
Severity — How urgency is communicated (where applicable)
Value delivered — What problem it solves for your team

Summary of Topics Covered

Task Management

Task insights monitor the day-to-day execution health of your project, surfacing delays, stalled work, accountability gaps, and dependency risks across all project tasks.

1. Task Delay Issues

Alerts when project tasks have slipped past their planned completion date.

2. Task Overdue Issues

Surfaces high-priority tasks that have missed their deadline.

3. Tasks With No Progress

Identifies tasks stuck at 0% completion as their deadline approaches.

4. Tasks With No Clear Ownership

Flags tasks that have no assigned owner, active or upcoming.

5. Internal (Task) Dependency Issues

Highlights tasks at risk because their predecessors are behind schedule.

Milestones

Milestone insights focus on the key commitment points in your project, alerting you when milestones are missed, at risk from upstream delays, or lack a clear owner.

6. Missed Milestone Deadlines

Alerts when key milestones have passed their planned date without being achieved.

7. Milestones With No Clear Ownership

Identifies milestones that have no responsible owner assigned.

8. Milestone Dependency Delays

Warns when predecessor tasks to a milestone are running late.

Final Note

These insights help shift project management from reactive tracking to proactive risk management, enabling faster decisions and better project outcomes.

Related Articles

Project Insights Engine: Configuration and Severity Levels

Vibha Sharma — Wed, 29 Apr 2026 06:35:45 GMT

Overview

Once Project Insights is set up, it works out of the box with sensible defaults. But every project is different and this article explains how to customize which topics are enabled, what thresholds trigger an insight, and how to interpret the severity levels attached to each insight you receive.

Altering the Default Configuration

Topic configuration exists at two levels — a global default that applies to all projects, and a per-project override stored on the project-to-topic mapping record. The runtime engine also reads from a hardcoded script include, which means configuration changes made in the database take effect only when the script include is also updated.

Layer	Table / Object	Field	Scope
1 — Global default	sn_spm_gen_ai_insight_topic	default_topic_config (JSON)	Applies to all projects. One record per topic.
2 — Per-project override	sn_spm_gen_ai_m2m_work_item_topic	topic_config (JSON)	Applies to one project only. One record per project-topic pair.
3 — Runtime (code)	NAProjectInsightsTopicConifguration (Script Include)	TOPICS object — hardcoded config per topic	Used by generators at runtime. Currently overrides DB values.

Note: Configuration changes made only at the database level (Layers 1 or 2) will not take effect until the corresponding Script Include (Layer 3) is also updated. Always coordinate with your platform administrator when making threshold changes.

Understanding Severity Levels

Every insight is tagged with a severity level so you know what needs immediate attention versus what to keep an eye on. Here's what each level means:

Severity	What it means
Critical	Immediate action required
Moderate	Action needed soon
Minor	Monitor closely
Informational	Awareness only
No Severity Tiers	All qualifying items are reported equally

Availability

This feature is available for customers on Zurich Patch 7 and above with the it_project_manager role.

Related Articles

Project Insights Engine: What Gets Surfaced and Why

Vibha Sharma — Wed, 29 Apr 2026 05:36:18 GMT

What is Now Assist for SPM Project Insights?

Now Assist for SPM continuously monitors your project data and delivers AI-generated insights directly to project managers — surfacing risks, delays, and opportunities without requiring manual review of every task, resource, and budget line.

This article covers how insights are generated, how they reach you, and what cadence options are available.

How Insights Are Generated

Each time the insight engine runs a project, it executes a five-step pipeline. The first three steps are deterministic — they use rules and thresholds to evaluate project data. The last two steps use the Now Assist LLM to summarize and synthesize the results into human-readable output.

#	Step	What happens
1	Scheduled trigger	A daily scheduled job (SPM Email Insight Job) checks every project's Work Item Report Schedule Configuration. If a project's next due date has been reached based on its configured cadence (weekly / bi-weekly / monthly), it queues that project for an insight run.
2	Data fetch	For each enabled insight topic, the relevant data provider queries the ServiceNow database and loads the project's data — tasks, milestones, resource assignments, RAID items, cost plans, or the project record itself — scoped by the data scope rules described in each topic card below.
3	Rule-based analysis	Each topic's analyser evaluates the fetched data against its configured thresholds — days overdue, allocation percentages, variance amounts, open states, and so on. This step produces a list of raw insight objects, each with a plain-text description and structured metadata. No LLM is involved at this stage.
4	LLM summarization (per dimension)	The raw insight list for each dimension (task, milestone, resource, RAID, financial, schedule) is sent to the Now Assist LLM via the 'Project insights generation' skill. The LLM receives the list and returns a structured JSON response with insights classified into high, medium, and low severity buckets — in natural language suitable for a project manager audience.
5	Overall summary (cross-dimension)	Once all five dimensions have been processed, a second LLM call synthesizes the results into a cross-dimension overall project health summary. This summary is what appears at the top of the email and in-app insight view, giving the project manager a single narrative that reflects the project's full health picture.

Output structure

The final output stored per project run consists of: :

Per-dimension insights — Each of the five dimensions (task, milestone, resource, RAID, financial) produces a set of insights classified as high / medium / low. Schedule variance produces a single insight.
Overall summary — A synthesized narrative covering the project's health across all dimensions, highlighting the most critical items requiring immediate attention.
Record links — Each insight is linked back to the specific ServiceNow record it was generated from (task number, risk number, cost plan, etc.) so the project manager can navigate directly to the source.

How Insights Are Delivered

Delivery Channels

Now Assist for SPM delivers project insights through two channels simultaneously:

Email — A structured insight digest is automatically sent to the project manager's inbox on each run. The email summarises all active insights across all enabled topics, grouped by dimension and severity.

In-App — Insights are also surfaced directly in the Project Workspace within the ServiceNow platform, accessible to anyone with access to the project. The in-app view provides the same insight content with direct links to the underlying records.

Cadence

Insights are generated on a recurring schedule controlled by a daily scheduled job. The job checks each project's configured cadence and runs insights when the next due date is reached.

Cadence Option	Frequency	Typical Use
Weekly	Every 7 days	Fast-moving or high-risk projects requiring close monitoring
Bi-Weekly	Every 14 days	Standard projects — this is the system default
Monthly	Every 30 days	Lower-activity projects or executive-level reporting cycles

Note: Cadence is configured per project in the project's Work Item Report Schedule Configuration record. The default is bi-weekly. Changing the cadence also changes the data fetch window used when loading task and resource data for analysis.

Availability

This feature is available for customers on Zurich Patch 7 and above. You'll need Now Assist with it_project_manager role to access it.

Related Articles

Integrating Enterprise Agile Planning (EAP) with Azure DevOps (ADO) via SAFe — Complete Guide

NagendrabaM — Thu, 18 Jun 2026 18:05:54 GMT

Overview

This guide explains how to integrate Enterprise Agile Planning (EAP) with Azure DevOps (ADO) using a three-layer integration approach:

These steps apply exclusively to ADO teams integrated via SAFe, where Iterations/Sprints can only be created from EAP.

EAP → SAFe → ADO

EAP → SAFe: Custom Business Rules sync Planning Intervals, Sprints, Features and Stories from EAP tables to SAFe tables
SAFe → ADO: Existing OOB ADO integration syncs SAFe records to ADO work items
ADO → SAFe → EAP: Reverse sync flows back through the same layers through Internal integrations for Features and Stories

Who Should Use This Integration?

Organizations using Enterprise Agile Planning (EAP) as their planning tool and Azure DevOps as their execution tool
Organizations following the SAFe framework with Program Increments, Sprints, Features and Stories
This approach bridges EAP and ADO through SAFe as an intermediary layer.

Limitations of This Approach

Before proceeding, it's essential to be aware of the following limitations:

Direct EAP ↔ ADO integration does not exist yet — SAFe acts as intermediary
Planning Interval/Sprint creation must originate in EAP — sprints flow EAP → SAFe → ADO
Iterations should not be created from ADO / SAFe.
SAFe teams must be configured under EAP and SAFe Agile release train before creating Planning Intervals
Team Integrations Settings should be created for all the SAFe teams associated to ART before Creating Planning Intervals in EAP side under EAP ART.
Sprint calendar spans must exist for each PI before clicking "Create Next Planning Interval"
EAP Agile Release Train must be linked to SAFe ART field before clicking "Create Next Planning Interval".
Populate Assignment group(when creating Feature in EAP side along with Team(Team field should be EAP ART) and assignment group should be SAFe Team.
Sprint name will show as per SAFe Sprint naming conventions in Azure.

Steps to setup this integration:

Step 1: Import all below mentioned update sets in below order

1.EAP To ADO Integration - Azure DevOps Agile.xml

2.EAP To ADO Integration- SAFe.xml

2.EAP To ADO Integration- PP Shared.xml

3.EAP To ADO Integration- PP Internal.xml
4.EAP To ADO Integration- Portfolio Planning Core.xml

5.EAP To ADO Integration- Strategic Planning.xml

Step 2: Create Azure Devops(ADO) Project Of Work item process 'SAFe' in Azure and Discover projects.
Create and Configure External Integration Table/Field Mapping for User Story and Feature records under Process Mapping Related List > SAFe > Table Maps
If any additional field/choice mapping needed, create your own mapping from Process Mapping Related List.

For User Story Mapping:

1.Change Internal Table field from Story [rm_story] to sn_safe_story
2.Change System.Parent field map from sn_safe_epic to sn_safe_feature

For Feature Mapping
Create a new mapping for Feature table as mentioned below

Step 3: Modify the Business Rule conditions on SAFe feature and Story
1.Go to Business rules > Search for "Synch SAFe feature with Azure DevOps" BR and Remove the existing condition Value gs.getSession().isInteractive(); and replace with current.getValue('sys_updated_by') != 'system'

2.Go to Business rules > Search for "Synch Story with Azure DevOps" BR and Remove the existing condition Value gs.getSession().isInteractive(); and replace with current.getValue('sys_class_name') === 'sn_safe_story' && current.getValue('sys_updated_by') != 'system'

3.Go to Business rules > Search for "Sync PI with ADO Iterations" BR and Remove the gs.getSession().isInteractive(); from existing condition Value and replace with current.getValue('sys_updated_by') != 'system'

Final condition Value should be like this “current.getValue('sys_updated_by') != 'system' && ( current.operation() === 'delete' || (current.start_date.changes() || current.end_date.changes() || current.short_description.changes()))”

4.Go to Business rules > Search for "Sync Program Sprint with ADO Iterations" BR and Remove the gs.getSession().isInteractive(); from existing condition Value and replace with current.getValue('sys_updated_by') != 'system'

Final condition Value should be like this “current.getValue('sys_updated_by') != 'system' && (current.operation() === 'delete' || current.short_description.changes())”

Step 4: Check Internal Integration Table/Field Mapping for Story and Feature records under Strategic planning > Integrations > ServiceNow Internal(Record). If any additional field/chioce mapping needed on Story/Feature Tables , Create your own internal mapping.

For SAFe Feature(sn_safe_feature) Table Map

For SAFe Story(sn_safe_story) Table Map

Step 5: Add SAFe Team to EAP Agile Release Train in Enterprise Agile Planning and Add SAFe ART field to Enterprise Agile release Train (Default view)

1.Before adding SAFe Team to EAP Agile release Train, Create EAP Agile release Train and associate corresponding SAFe ART in EAP Side under Essential or Portfolio Configuration(Enterprise Agile planning > Settings >Agile Structures > Click + Sign on Essential or Portfolio Configuration and Add EAP Agile release Train
2.Sprint calendar spans must exist for each PI(Enterprise Agile planning > Settings > Planning calendars)

3.Go to sn_apw_advanced_agile_team.LIST

Click on New button
Enter SAFe team Name
Select Enterprise Agile configuration(Essential or Portfolio Configuration)
Select Parent(This should be EAP ART which is linked to SAFe ART)
Select User group(This should be SAFe team which is associated to SAFe ART and has Team Integrations Settings

Step 6: Add Assignment group field to EAP feature(EAP New view)

While creating feature in EAP, populate both Team as EAP ART and Assignment group(SAFe Team - As per the ADO team integrations created for SAFe teams which are part of SAFe ART)

Step7:After Creating Planning intervals in EAP. Go to Azure select ADO project > Project settings > Team configuration > Select the team for which Team integration settings mapped in Service now side and click Select iterations, Add your Sprints

By following these steps, you can successfully integrate Enterprise Agile Planning (EAP) with AzureDevOps (ADO). This setup enables users to track the progress of Planning intervals, Sprints, Features, Stories and other work items within EAP and SPW while ensuring smooth synchronization between ServiceNow and Azure DevOps (ADO).

Enterprise Agile Planning - Story Cards disappear from Planning Board columns after page reload

Anupam Pandey — Wed, 27 May 2026 05:59:07 GMT

Problem

For rm_story, when custom state choices are used as columns on the Enterprise Agile Planning (EAP) Planning Board, cards appear in the correct column when moved, but disappear after a page reload.

Cause

On page reload, the Planning Board does not determine column placement from the record's state value alone. Instead, it maps cards to columns based on state buckets configured in the dictionary for the state field on the rm_story table.

If a custom state choice is not added to the appropriate state bucket in the dictionary, the Planning Board cannot map cards to that column after reload.

Behavior when state bucket is not configured

You may observe the following sequence:

· Cards can be dragged into a column representing the custom state.

· The state change appears to work and the card is visible initially.

· After refreshing the Planning Board, the cards no longer appear in that column.

This is expected behavior when the custom state is not mapped in the state bucket configuration.

Resolution

Creating a custom state choice alone is not sufficient for it to work correctly on the Planning Board. You must also add the custom state to the appropriate state bucket through the dictionary configuration for the rm_story state field.

Procedure:

1. Navigate to System Definitions > Tables.

2. Search for the rm_story table and open its record.

3. From the Columns related list, locate the State column’s record and open it.

4. In the Dictionary Overrides related list of the State Dictionary Entry form, search for the rm_story table and open its record.

5. Update the Attributes field to include the new custom state choice in appropriate state bucket.

6. Save the changes.

Once the custom state is included in the appropriate state bucket, cards in that state persist correctly on the Planning Board, including page reloads.

Summary

Both of the following steps are required for custom states for rm_story table to work consistently on the Planning Board:

· Create the custom state choice.

· Add the custom state to the appropriate state bucket via the rm_story state field's dictionary configuration.

Resourcing just got a major upgrade in Project Workspace!

HayleyAlexander — Wed, 08 Apr 2026 19:29:25 GMT

We're excited to share that the Resource Page in Project Workspace is now available! Giving project managers the visibility they need to stay ahead of resourcing issues without disrupting the workflows resource managers depend on.

The problem we heard:

Project managers told us they were spending too much time chasing down basic resourcing information; who's on my team, are they overallocated, are there conflicts I should know about? That lack of visibility meant PMs were often reactive, only learning about resourcing issues after they'd already impacted timelines.

Meanwhile, resource managers were fielding status questions that pulled them away from the higher-value allocation and planning work they do in Resource Management Workspace.

What's new:

With the new Resource Page, project managers now get a dedicated view, right inside Project Workspace, of the resourcing picture for their projects. In one UI, you can:

See your assigned people and teams- clear visibility into who's working on your project and in what capacity.
Monitor capacity at a glance- understand where your team stands without having to request updates or wait on reports.
Surface conflicts proactively- get early visibility into resourcing issues so you can flag them and collaborate with resource managers before timelines slip.

This is about giving each role the right lens into the same data. Resource managers continue to own allocation strategy, cross-project balancing, and long-range capacity planning in their dedicated workspace. What's changed is that project managers no longer have to operate blind in between those conversations. When a PM spots a conflict early, that's a better starting point for the RM too.

Get started:

The Resource Page is available now in Project Workspace. Within Project Workspace in the latest release, you'll notice a new page 'Resources.' We'd love to hear how it's working for your teams!

Strategic Portfolio Management Functional Data Model

shankarkattaman — Tue, 31 Mar 2026 07:12:02 GMT

Introduction

Strategic Portfolio Management (SPM) in ServiceNow provides organizations with a unified platform to align strategy with execution.

The ServiceNow Strategic Portfolio Management (SPM) functional data model centers on the "Plan Item" table, which acts as the foundational entity for strategic and work-related items. This unified Plan Item approach provides a flexible and configurable data structure, enabling organizations to define hierarchies and relationships that represent both strategic and operational portfolios, and to plan and track work effectively.

This article provides the functional data model of Plan Item and its related entities, which enables organizations to plan strategically, manage intake efficiently, and execute work effectively using SPM.

Note: This functional model is current as of March 2026

The Core Table: Plan Item

The foundation of the ServiceNow Strategic Portfolio Management (SPM) functional model is the Plan Item. It serves as the core table from which all major entities within SPM are derived.

Entities Derived from the Plan Item:

Strategic Items:

Initiative
Capability
Strategic Program
Strategic Portfolio

Intake Items:

Demand Planning Item (synchronized with dmn_demand)
Product Idea

Execution Work Items:

Project Planning Item (synchronized with pm_project)
Epic Planning Item
CWM Board Planning Item

One of the key strengths of this model is its extensibility. Organizations can extend the Plan Item table to create additional entities tailored to their specific planning or work-tracking requirements.

Strategic Items: Defining Your Organization's Direction

Strategic Items represent the high-level planning elements that define and organize work across your enterprise. These include capabilities, initiatives, strategic programs, value streams, and organizational structures like portfolios and business areas.

You can also enable Strategic Items for Roadmap Planning to support long-term planning and alignment before breaking down work into detailed plans.

Building Your Strategic and Organization Hierarchy

The Alignment Lens (sn_align_core_lens) allows you to create hierarchies among plan items.This flexibility is crucial—organizations can structure their hierarchies and specific needs to plan and track the execution rather than being constrained by a rigid Out of Box Lenses.

Hierarchy enables you to:

Perform high-level planning: Build initiative roadmaps before detailed execution
Link execution to strategy: Connect projects, demands, or epics to strategic or organization items for comprehensive planning and tracking. Helps to view work from Various lenses
Track the execution: Monitor progress and performance of work connected to strategic items

Enterprise Goals

Strategic Planning Workspace provides Goal Framework for organizations to define their Enterprise Goals(sn_gf_goal). These Goals can be associated to any Owning Entity, which can be any Plan Item Table(Organization or Strategic Tables) as desired by organization.

The Goal Framework also incorporates Targets (sn_gf_goal_target), which define measurable outcomes with their own assigned entities for clear progress tracking

Aligning Work with Goals

Strategic alignment is achieved through direct linkage execution plan items to organizational goals. These Plan items contribute to attainment of the Goals.

How

Plan Item has a reference to a Goal (sn_gf_goal), allowing organizations to assign a primary goal. These intake and execution plan items fulfill the goal.
In scenarios where multiple work items needs to be associated to the goal, the Goal Relationship (sn_gf_goal_m2m_relationship) table helps in the association.

Capacity and Financial Planning

Once strategy is defined and prioritized, organizations must assess whether they have the resources—people, skills, and funding—to execute the strategy effectively.This is where capacity and financial planning on the execution items helps to prioritize and roadmap it based on resources and/or funding availability.

Capacity Planning:

Helps in Demand vs. Capacity Analysis of Resources. Analyze resource requirements against available capacity across configured groups, roles, skills or any configured resource attributes as defined by Organization to decide which work item can be executed in what time frame.

Below Tables are essential for performing demand-versus-capacity analysis.

CPAAM Capacity Table: Maintains baseline capacity for resources across defined time periods, derived from user schedules, availability rules, and organizational calendars.

Generate Capacity Module in SPW: Automates capacity record creation by pulling data from user schedules, holidays, and availability configurations. Organizations typically schedule this job periodically or trigger it after major changes.

CPAAM Effort Table: Stores monthly aggregated effort based on attributes like role, skill, or group

Financial Planning with Investment Objects

The Investment Object serves as the financial core table, containing all financial data for plan items. It consists of three key components:

Cost Plan and Breakdown: Defines estimated and actual costs, with breakdowns by expense type, fiscal period, or cost type for detailed financial planning.
Benefit Plan and Breakdown: Captures expected and realized benefits, providing visibility into benefit categories, timelines, and measurable outcomes.
Funding (Budget) Breakdown: Represents funding sources allocated to investments, tracking by source, fiscal period, or funding type.

These financial components are shared between strategic planning items and actual execution items, ensuring consistency across the planning and execution lifecycle.

Intake Work Items: Managing Ideas and Demands

Demands

SPM maintains two objects for demands: Core Demand object - dmn_demand and Demand roadmapping Object -sn_align_core_demand.

sn_align_core_demand is purely used for only roadmap planning and tracking purposes in SPW to show alongside of other planning items, this is bidirectionally sync with dmd_demand.

For all other purposes of Demand Intake, Demand Assessment, Demand approvals, Conversion Core Demand object -dmn_demand is used.

Demand (dmd_demand) are synchronized with their respective Demand Planning Items. The Alignment Integration (sn_align_cmn_int_integrations_setup) ensures key columns sync between planning and execution layers.

Demands can be converted to various execution work items, providing flexibility in how organizations move from intake to delivery.

Product Ideas and Feedback

The Feedback application (sn_align_core_feedback) simplifies gathering and analyzing user feedback. Product Ideas (sn_align_core_product_idea) can be created and linked with other feedback, planning items, or non-planning items through the Feedback Relation many-to-many table.

Execution Work Items: Getting Work Done

Projects:

SPM maintains two objects for Projects: - Core Project Execution object - pm_project and Project Roadmapping Object -sn_align_core_project.

sn_align_core_project is purely used for only roadmap planning and tracking purposes in SPW to show alongside of other planning items, this is bidirectionally sync with pm_project.

For all other Project execution, Projects (pm_project) are actual execution items used in project workspace.

Projects (pm_project) are synchronized with their respective Project Planning Items. The Alignment Integration (sn_align_cmn_int_integrations_setup) ensures key columns sync between planning and execution layers.

Key Project-Related Entities:

Project Task (pm_project_task): Individual units of work, including milestones
Requirements (dmn_requirement): Stores project or demand requirements
Story (rm_story): Captures user stories for agile project management
Status Report (project_status): Time-based snapshots of project health
Baseline and Baseline Item: Captures project and task dates for variance analysis
RIDAC: Framework for tracking Risks, Issues, Decisions, Actions, and Changes
Project Financials: Project is associated to Investment Object which has Cost Plans, Benefit Plans and Budget
Project Resources: Project Resources are managed through Resource Assignments

Resource Assignments

Resource Planning ensures the right resources—people, roles, groups, skills, or attributes—are available and optimally assigned to work.

Resource Assignments: Requests for roles, groups, users, or other resource planning attributes. This is a shared model between plan items and actual items.

Resource Allocations: The actual assignment of people or groups to fulfill resource assignments. When allocated, the system creates:

Resource Allocation Dailies: Daily-level allocation tracking
Resource Aggregate Weekly: Weekly consolidated views
Resource Aggregate Monthly: Monthly high-level analysis

This multi-granularity approach supports operational, tactical, and strategic decision-making.

Labor and Non-Labor Cost Plans

Labor Cost Plans define planned financial costs for labor resources based on rate cards, roles, and allocated hours. These are automatically created from resource assignments.

Non-Labor Cost Plans encompass expenses unrelated to human resources, such as hardware, software, and travel, typically entered manually.

Timecards and Actuals

Time tracking integrates with resource planning to maintain consistency between allocated effort, actual work, and financial impact:

Users submit Timecards (time_card) against assigned tasks
Each timecard references the corresponding Resource Assignment
When processed, timecards generate Expense Lines (fm_expense_line)
Expense lines update actuals in corresponding Cost Plans which rolls up the data to project

Benefit Plan Actuals can also be reported directly from breakdown details within benefit plans.

Enterprise Agile Planning (EAP)

SPM's Plan Item structure inherently supports flexible Agile execution. Organizations can configure their Team Hierarchy for Enterprise Agile planning by setting team levels and specific work item types.

Key EAP Concepts

Agile Entities: Epic, Capabilities, Features, and Stories extend the Plan Item model

Team Hierarchies: Teams organized hierarchically with one or more plan items/agile entities mapped

Planning Calendars: Each team type follows a planning calendar (ARTs use Planning Intervals, Agile teams use sprints)

Jira Integration: Bidirectional sync enables work planned in EAP to be executed in Jira, with automatic updates reflected in both systems

Collaborative Work Management (CWM)

CWM provides a central hub to plan, visualize, manage, and collaborate on work without switching between multiple tools.

Core CWM Entities

CWM Space (sn_cwm_space): Collaborative workspace containing boards, tasks, and documents
CWM Board (sn_cwm_board): Visual board for tracking work items (also a Planning execution item)
CWM Task (sn_cwm_task): Individual work items managed on boards
CWM Doc (sn_cwm_doc): Documentation associated with spaces or boards
CWM Sprint (sn_cwm_sprint): Time-boxed iterations for agile management

Team Agile in CWM

CWM Boards handle team-level Agile management, including sprints and backlog management. The "connect work into board" feature can unify backlogs by bringing in various task work.

EAP Integration: When an EAP Agile team connects with CWM, a Space and Board are automatically created, with assigned stories brought in as connected work. EAP Sprints and CWM Sprints remain synchronized.

Resources

For more detailed information on implementing and configuring SPM, visit:

Quick Story Generation: Create Stories Quickly Using AI in Agile Development & EAP

Vibha Sharma — Tue, 31 Mar 2026 05:11:34 GMT

What’s New in This Release:

Quick Story Generation

Generate a single story at a time with the new “Generate story” button. Provide 1–2 lines of story context (persona, goals, etc.) and AI instantly creates a complete story with title, description and acceptance criteria. Perfect for when you need one focused story quickly - review, edit and save.

What Makes It Special:

Generate Story: Click “Generate story” to create one story at a time. Provide brief context, review the generated title, description and acceptance criteria and save. Perfect for targeted story creation.
Review & Edit: Generated content is editable - refine before saving to ensure it meets your requirements.
Time Saving: Turn story context into a complete, structured user story in seconds.

How It Works:

Navigate to the Stories related list in Agile or EAP.
Click the “Generate Story” button located above the story list.
Enter story context (1–2 lines): Example: "progress tracking for onboarding steps to help users visualize their journey"
Click “Generate”.
Review the generated title, description, and acceptance criteria.
Edit if needed.
Click “Save story”.

Note: Use “Generate story” to quickly create a single story with focused context. Use “Create stories” to generate a full epic breakdown with multiple stories and conversational refinement. For more details on “Create Stories”, refer article: Agile Story Generation.

Try it out and share your feedback or questions in the comments below.

Frequently Asked Questions:

1. What role is required to generate stories?
Ans:The role required is sn_apw_advanced.eap_user or sn_apw_advanced.eap_read_only , with now_assist_panel_user

2. We’re using Agile Development, not EAP. Can we still use this feature?
Ans: The “Generate story” feature is available in both Agile and EAP.

3. What should I enter in the "Generate story" context field?
Ans: Provide 1–2 lines describing the story focus with persona, goals, metrics, or pain points.

Examples:

"mobile user needs fast checkout, goal is to reduce cart abandonment by 20%"
"admin dashboard showing user activity metrics"

4. Can I edit the generated story before saving?
Ans: Yes. The generated title, description, and acceptance criteria are all editable in the preview modal. Review and refine before clicking “Save story.”