Simple, logical and efficient Anaplan models contain hierarchies which are natural, intuitive and robust. Why then do we see so many that are overextended, too long and clunky?
Hierarchies in your Anaplan modelling allow your to formalise relationships between lists and dimensions. They enable you to declare and solidify parent and child mappings between adjacent dimensions and use these structures to create far more intuitive modelling processes, data flows and end user reporting.
Well designed Anaplan for FP&A models are simple, logical and fast. To get the best return we must spend 'sparsity dollars' wisely....Here's why!
We use what we call modelling cohorts to effectively organise and structure our clients data. We advocate using a concept we refer to as sequential consolidation to move and prepare our clients data through their models from record to report. These ideas help us spend our sparsity dollars with wisdom.
From our experience bad Anaplan model design results from limited understanding of mutually exclusive and collectively exhaustive data structures...
Mutual exclusive is a term applied to the grouping of data items whereby there is zero overlap between groups. Items belong exclusively to a single group. Collectively exhaustive is when all possible items are accounted for in our classification in the relevant combination, group or association. Why is mutually exclusive and collectively exhaustive (MECE) import to model design?
Creating simpler Anaplan solutions for end users can mean adding more...this is what happened for one of our recent clients.
The model design combined two separate modelling processes into a single core data flow in an attempt to keep the model simple. It didn't work. This is how we simplified by adding more.
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.
We created a way to consolidate multiple forecast processes which would otherwise blow up your Anaplan model - this is the story of 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.
We build robust, reliable and scalable FP&A models in Anaplan because core to our model architectural designs is a concept we call sequential consolidation.
It is central to all our designs and relies on moving forecast outcome data through several transformational stages before mapping it into a final report.
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.