Overview
Before you can start budgeting, forecasting, or running simulations in SAC, you’ll need a planning model. This model defines your data structure—like time periods, accounts, departments—and makes it possible to enter, store, and manage planning data.
Creating a Planning Model Step By Step:
Start a New Model
1
Go to the Modeler from the main menu.
2
Choose Create New Model > Start with a Blank Model.
3
When prompted, make sure to select Enable Planning. This activates planning-specific features like versioning, disaggregation, and data input.
Define Dimensions
4
At a minimum, SAC requires the following standard dimensions:
- Date: Time periods (years, quarters, months)
- Version: Public or private versions for planning scenarios
- You can also add custom dimensions like:
- Cost Center
- Product
- Region
Note
For each dimension, you can create a hierarchy to roll up values (e.g., Month → Quarter → Year).
Set Up Measures
5
At least one measure is required in every planning model. Without it, the model won’t support numeric planning values.
6
Measures are your numeric values—e.g. “Amount,” “Quantity,” or “FTE.”
7
You can build your model using:
- A single-measure setup (typically with an account dimension), or
- A multi-measure model to track values like units and revenue separately
Load Sample Data (Optional)
8
Add dummy data or import values from Excel or another data source.
9
This helps validate that your structure supports the planning use case you’re targeting.
Save and Name the Model
10
Give the model a clear name (e.g., “Corporate Budget 2025”).
11
Save the model. Once saved, it can be used in stories, value driver trees, allocations, and more.
Key Terms
Dimension
Categories used to slice data (e.g. Time, Region)
Measure
Numeric data stored in the model (e.g. Revenue)
Hierarchy
Structure that rolls values up from leaf to parent
Version
Public or private snapshot of your planning data
Best Practices
- Use clear naming for dimensions and members so others can easily understand them.
- Start small—create a basic model and test it in a story before adding complexity.
- Document dimension logic (e.g., which accounts are parent/child) to help with future edits.
