Overview
The SAFe Program Increments in Solution (SAFE_SOLUTION) plans mode loads Program Increment plans at the solution level — that is, from the portfolio project that sits above individual ART program projects in the Polarion SAFe project hierarchy. Columns represent coordinated PIs spanning all ARTs; swimlanes can be configured to show either Programs (ARTs) or Teams within the solution portfolio.
SAFe Program Increments in Solution (
SAFE_SOLUTION) mode requires the Siemens Polarion SAFe Solution to be enabled and a valid SAFe portfolio hierarchy to be configured in Polarion. Without it, the mode cannot discover portfolio, program, or team projects.Plans Mode Value
Set the widget parameter
plansMode to SAFE_SOLUTION to activate this mode.
How Plans Are Loaded
In SAFe Program Increments in Solution (SAFE_SOLUTION) mode, Planningboard identifies the portfolio project from the current Polarion project’s SAFe hierarchy and loads PI-level plans from that portfolio. The data service (PlanningBoardDataService) uses the SAFE_SOLUTION planning model to:
- Detect the SAFe portfolio root for the current project via portfolio detection logic.
- Retrieve all program-level project IDs within the portfolio.
- Load PI plans from the portfolio scope, filtered to the plan count window defined by
lastPlansandnextPlans. - Assign work items to swimlanes based on the configured SAFe assignment mode.
Compatible Swimlane Assignment Modes
SAFe Program Increments in Solution (SAFE_SOLUTION) mode is designed for use with the following assignment modes. Other assignment modes (such as Users (Assignee) (ASSIGNEE) or Parent Item (PARENT)) are available but are not the primary intent of solution-train boards.
SAFe Programs Assignment Mode
WhenassignmentMode is set to SAFE_PROGRAMS, each swimlane represents one SAFe program (ART) in the solution. Planningboard reads the program assignment from the field identified by safeProgramField on each work item.
SAFe Team Assignment Modes
WhenassignmentMode is SAFE_TEAM or SAFE_TRAIN_TEAM, each swimlane represents a team. The team assignment is read from safeTeamField on each work item.
For
SAFE_TRAIN_TEAM specifically, an ART ID parameter must be supplied to filter teams to a single ART. Refer to SAFe Train Team Mode for the ART ID field details.
Widget Parameters
The following widget parameters are relevant when configuring a solution-train board. See SAFe Parameters for the complete SAFe parameter reference and Plans (Columns) Parameters for all plan-column parameters.Plans (Columns) Parameters
Swimlane (Rows) Parameters
Work Items Parameters
Capacity Parameters
SAFe Project Hierarchy Detection
Planningboard uses internal SAFe hierarchy detection (viaSAFeImpl) to identify the portfolio context and enumerate programs and teams. The detection logic works as follows:
- When embedded in the portfolio project: all programs and their PI plans are in scope.
- When embedded in a program project: the portfolio is detected upward; PI plans from the portfolio are loaded, and team filtering can be applied.
project.id:(portfolioId). Program IDs and team IDs are retrieved as space-separated strings and used internally for work item filtering.
Configuration Example
The following example configures a solution-train board at the portfolio level, with SAFe Programs as swimlanes, showing the last 1 and next 3 PIs, with capacity tracking enabled.Comparison with Related Plans Modes
Limitations
- No multi-assignee effort distribution. Capacity bars reflect total effort per swimlane; effort is not split across multiple assignees within a single card.
- Parallel PI capacity. Capacity calculations across overlapping PIs may differ from Nextedy GANTT behavior. If your ARTs run concurrent PIs, validate capacity results against GANTT before relying on the numbers.
- Plan names with dashes. Fully supported from version 25.3.0 onward. Earlier versions have rendering issues with plan names matching SAFe naming patterns (e.g.,
PI-2401). - SAFe Solution requires Polarion SAFe. The SAFe Program Increments in Solution (
SAFE_SOLUTION), Programs (SAFe) (SAFE_PROGRAMS), Program / Solution Teams (SAFe) (SAFE_TEAM), and Agile Release Train Teams (SAFe) (SAFE_TRAIN_TEAM) modes require the Polarion SAFe Solution license and a valid SAFe project hierarchy. They cannot be used with standard Polarion project structures. - Configuration UI changes by plans mode. When switching between Project Plans (
PROJECT_PLANS) and SAFe modes in the widget parameter panel, some fields appear or disappear (e.g., plan stemming and sync-to-parent are only shown in Project Plans (PROJECT_PLANS) mode; the SAFe PI increment field appears only in SAFe Sprints in Program (SAFE_SPRINTS) / SAFe Sprints in Portfolio (SAFE_PFL_SPRINTS) modes). This is expected widget behavior, not an error.
Related Pages
- Plans Modes — overview of all plans modes
- SAFe Program Increments — PI planning at program level
- SAFe Sprints — iteration-level SAFe planning
- SAFe Programs Mode — swimlane assignment by SAFe program
- SAFe Team Mode — swimlane assignment by SAFe team
- SAFe Train Team Mode — swimlane assignment filtered by ART
- SAFe Parameters — all SAFe-specific widget parameters
- Capacity Parameters — capacity configuration reference