Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« Improved Anaplan Experience with new UX | Main | "EPMLCM-13000: Service currently not available error" upon implementing SSL in EPM 11.2.2 environment »

Welcome Anaplan HyperModel!

Executive summary

In today's world, regardless the size or type of the organization, it's imperative for an organization to keep pace with the current challenges, transform itself or left behind. Lack of coordination between cross functional teams can make it difficult for the business leaders to take agile decisions. With Anaplan HyperModel, teams across organization can work together, build robust models tackling the operational complexity & enable the decision makers to take the correct approach.


HyperModel capabilities drive three key performance benefits

  • Robust - Every organization requires a robust modelling capability to accelerate the decision-making process. With HyperModel, teams can add more dimensions, years, scenarios, and data into a single model for extensive analysis & long-term planning. Furthermore, teams across the organization from different departments can come together & collaborate on a unified, robust model as part of connected planning.


  • Scalable - With HyperModel, teams can expand new plans, load more historical data, adjust forecast and update models as when it is required without archiving any data sets or splitting up the models. Furthermore, business does not have to rearchitect their models to avoid data storage issues.



  •  Adaptable - HyperModel with improve performance & functionality, can take care of any multi-dimensional scenarios with large-scale data sets for in depth analysis. Modelers can build more what-if scenarios incorporating potential business challenges to predict possible outcomes.

Things to consider before implementing HyperModel

  • Is the current model well-built? 

This is a very important analysis which should be carried out before implementing HyperModel. HyperModel uses the same best practices which are applicable for a standard model, hence if the current model is not well built then implementing HyperModel will not make much sense. Therefore, it's essential to review the current model & re-engineer it if required before implementing HyperModel

  • Is combining split models - a good idea?

Before we discuss on combining split models with the help of HyperModel, we must first understand the requirement of split models. If the split models were created to manage the data scalability, then with the use of HyperModel we can combine these split models provided they share common structures.

However, if the split models were created because of different process steps, different levels of granularity, then it will be best to keep the split models as it is. Having said that, we can still use Hypermodel to increase the scalability of these split models to manage more timelines, scenarios etc.



The standard model has a size limitation of 130 GB which is in some cases restricts further development or large-scale modelling. With HyperModel, business can create more robust business solution incorporating more future scenarios & predict a more accurate forecasting.

Though Anaplan hasn't confirmed the size of the HyperModel yet, however many Anaplan enthusiast like me estimate that Anaplan will increase the size from 130 GB to 700 GB. 

Size constraint was one the few challenges holding Anaplan back with respect to other planning tools, however with HyperModel, Anaplan has opened a new door full of possibilities. 

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles