PLANS is the new standard for Anaplan modeling—“the way we model.” This covers more than just the formulas and includes and evolves existing best practices around user experience and data hubs. It is a set of rules on the structure and detailed design of Anaplan models. This set of rules will provide both a clear route to good model design for the individual Anaplanner and common guidance on which Anaplanners and reviewers can rely when passing models amongst themselves.
In defining the standard, everything we do will consider or be based around:
Performance – Use the correct structures and formula to optimize the Hyperblock
Logical – Build the models and formula more logically – See D.I.S.C.O. below
Auditable – Break up the formula for better understanding, performance, and maintainability
Necessary – Don’t duplicate expressions. Store and calculate data and attributes once and reference them many times. Don't have calculations on more dimensions than needed
Sustainable – Build with the future in mind, thinking about process cycles and updates
The standards will be based around three axes:
We will define the techniques to use that balance on the three areas to ensure the optimal design of Anaplan models and architecture.
As part of model and module design, we recommend categorizing modules as follows:
Data – Data hubs, transactional modules, source data; reference everywhere
Inputs – Design for user entry, minimize the mix of calculations and outputs
System – Time management, filters, list attributes modules, mappings, etc.; reference everywhere
Calculations – Optimize for performance (turn summaries off, combine structures)
Outputs - Reporting modules, minimize data flow out
Why build this way?