| Table of Contents | ||
|---|---|---|
|
Overview
A planning period (formerly known as an “allocation project”) is a time based container and supports company wide planning such as a QBR (Quarterly Business Review) or BRP (Big Room Planning) and stores data to specific periods to use in Planner and Forecast.
...
In
Planner, only the active period will be visible and used to store allocation data (demand requests, originating supply structures and approvals).In
Forecastit is possible to show as many periods as required (no hard limit), however there may be screen real estate challenges if too many are made visible at once.
Why are planning periods needed?
Provide process aligned communications in
PlannerandForecast(e.g. to communicate to users the cut off dates for submissions)Support customer defined configuration for process flow control, providing customer control over days worked, approval processes and much more.
Each planning period stores a single set of baseline data that is used in
PlannerforPoint in Time (aka PiT)reference of team compositions (a point in time snapshot)Each time box (or planning horizon) column created in
Forecastis its own planning period.
...
Limitations
It is only possible to have one active allocation at any point in time
There is no way to automatically generate planning periods
How to create and configure a planning period (aka allocation project)
| Info |
|---|
When should you create a new planning period? Planning periods are typically created:
|
FAQs
| Expand | ||
|---|---|---|
| ||
|
...
| Expand | ||
|---|---|---|
| ||
The purpose of non active planning periods is to allow the storing of macro-allocation data (FTE numbers only) against the specified time period in the Forecast module. |
Related information
| Filter by label (Content by label) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...