Steps: Set Up Adaptive Planning Models
Receive an Adaptive Planning instance with sign-in credentials.
The Adaptive Planning model functions for:
- Financial planning.
- Sales planning.
- Workforce planning.
Each data point in Adaptive Planning corresponds to an intersection of dimensions. All Adaptive Planning instances come with these dimensions:
- Time: Months, quarters, and years from a calendar that runs from January to December.
- Versions: 1 actuals version and 1 plan version. Use actuals version for past data. You can create actuals sub-versions to slice your actuals data or to use journal entries. Use plan versions for future data. Example: Budgets, what-if scenarios, forecasts. You can create as many plan versions as you require.
- Accounts: Standard general ledger accounts with standard account codes. You can further build your general ledger. You can also build metrics, assumptions, and create custom accounts outside of your general ledger.
- Levels: 1 top-level representing your company. You can build out your level hierarchy according to your business needs. In general, levels mimic the structure of your organization. Example: Cost centers, departments, subsidiaries.
You can also add custom dimensions and attributes to your model. Custom dimensions provide an additional coordinate to the intersections of your data. Attributes group the dimensions and the associated data. You can reference attribute groupings in reports and formulas.
You can also use APIs and integration loaders to build your model.
- SelectModelingfrom the main menu.From theModelingpage, access all of the links required to build your model.You can use the breadcrumbs to return toModelingafter you complete each step.
- (Optional) ClickTime.Add time strata to the structure, extend the calendar, and create time rollups that differ from your structure.
- (Optional) Create Plan Versions.ClickVersionsto create new plan versions or manage the settings of your plans. You can also create new actuals sub-versions.
- (Optional) Create Custom Dimensions.Create additional dimensions to support your unique business needs, and create the values.
- (Optional) Create Attributes.Use attributes to tag levels, accounts, and any custom dimension with attribute values. Example: A product group attribute tags your product dimension values.
- (Optional) Create Accounts.
- (Optional) Add or Change Account Formulas and Overrides.Formulas reference other dimensions and accounts to calculate data for accounts across levels, and versions. Add formulas in the account settings.From sheets, calculated accounts are read-only. Users can change the contributing data and watch the calculations update in real-time.
- (Optional) Create Shared Formulas.Shared formulas calculate data for accounts at specific levels and versions.From sheets, users can still edit the formula for specific cells, or enter values instead of using the formula.
- Build standard sheets.Add your general ledger, custom, metric, and assumption accounts to standard sheets.
- (Optional) Build modeled sheets.Modeled sheets have their own account hierarchies.They contain records that drive calculations in modeled accounts.
- (Optional) Build cube sheets.Build cube account hierarchies for each cube sheet so that users can pivot the sheet through multiple dimensions during planning.
- (Optional) Add general ledger and custom accounts to cube sheets.Add general ledger and custom accounts to your cube sheets to use dimensions and attributes for planning your standard accounts.
- (Optional) Link data from cube and modeled sheets to standard accounts.Pull the dimensions and data that you gathered in modeled and cube sheets into your general ledger or custom accounts.
- Get your data into your model.Enter data in sheets, or load data throughIntegration.
From the main menu, select:
- Reportsto build and share ad hoc reports.
- Dashboardsto transform data into visual charts.
You can also use OfficeConnect to stream the data into Microsoft Excel, PowerPoint, and Word.
Use the
Planning Center
to regularly monitor the performance and usage of your model. See: