We designed a scenario planning function in our clients Anaplan for FP&A model which reduced model size by two thirds. This is how we did it...
During our early time with Anaplan we wanted to design a better way to consolidate the numerous actuals, budget and forecast data that all FP&A models generate.
Great Anaplan for FP&A model design boils down to three core models; the actuals model, consolidation model and archive model.
Great Anaplan for FP&A model design boils down to three core models; the actuals model, consolidation model and archive model.
We believe all FP&A models in Anaplan should contain scenario planning as standard. In 6 steps this is how we implemented it for our clients...
We have designed an approach to delivering scenario planning which gives our clients access to this functionality without consuming excessive resources or disrupting business as usual.
An archive is core to how scenario planning functionality should be developed in your Anaplan models...
An archive is a location within the model which is disconnected from all live processes and retains data which can be retrieved via a mapping. The retrieval can be part of a scenario planning functionality or simply used to hold historical forecasts and budget for future reference.
Workspace capacity constraints are major issue for most Anaplan model designs. So, what can we do to minimise or mitigate the issue?
Here are a few design ideas we have implemented while working to redesign, redevelop and rebuild several large enterprise wide FP&A models for some of our global clients.
FP&A in Anaplan can become very large, very quickly.
FP&A models powered by Anaplan can become very large, very quickly. This is especially true when we look to retain access to prior forecasts and/or large libraries of prior year data. So how can we do it without adversely impacting model performance? Through archiving.