In this post I will list the Essbase best practices to make a smooth running Hyperion Planning / Oracle PBCS implementation. Enjoy and please use them!
many implementations are just plain wrong
There are many ways of implementing business requirements into Essbase – read Hyperion Planning – but most of them are plain wrong. I can say this with certainty, as I have been asked to rescue and redesign many sluggish Essbase implementations over the years. At each particular malfunctioning implementation, I enforced these Essbase best practices and the result was a smooth-running engine. The result: all performance issues solved, an implementation partner that should be a bit wiser and a happy client. I am happy to share these best practices with you, so you can build and design good planning solutions from the start.
sharing proven Essbase best practices
After fiddling around for a couple of years with Essbase in the beginning of my Essbase career I stumbled upon this very specific Essbase design pattern when I joined a group of seasoned Essbase performance optimizers in The Netherlands. Maybe they invented the pattern, maybe they copied it and perfected it. I really do not know. But what I do know, is that this design pattern has proven to be the “golden standard” for Hyperion Planning solutions tuned for good performance.
This pattern has been copied among lots of consultants in Europe, but I still see and discover that many of them do not really understand the pattern as I see the pattern being implemented incorrectly. The consultants that do understand the value of this pattern keep their mouth shut as it was one of the great secrets of the world … only if they could, which of course is not possible. In my opinion, good design and best practices should not be a secret, they should be shared and taught to improve the overall quality and business success when using Oracle’s EPM solutions.
the Dutch School on Essbase Design (DSED)
In this blog posts and the next to follow, I want to tell you the ‘secrets’ of this design pattern listed as Essbase best practices for Hyperion Planning implementations (and PBCS); which I will from now on call the “Dutch School on Essbase Design”. I do this, because in “Essbase land” there are many expert Essbase consultants with each having their own opinion on how to best implement business requirements in Essbase. Each consultant has its own — most of the time — specific design pattern. But in all Essbase discussions on the internet on what is best in Essbase, the context of the design patterns used is lost; what is good for one pattern could be disastrous when using another design pattern. The result is you being confused with contradicting advise.
So, please keep in mind, I will discuss “The Dutch School on Essbase Design”. With ample proof that it works and brought relief when redesigning many existing sluggish Planning implementations. When you follow this design pattern you will ensure — for almost 95% — that your solution will be (1) fast, (2) enable the implementation of almost any financial requirement and (3) is easy to maintain.
So here we go.
the Essbase best practices revealed
What are the Essbase best practices for Planning, what is the “Dutch School on Essbase Design”? And let’s follow Oracle’s fondness of abbreviations and refer to it as the DSED.
The best-practices of the DSED for Hyperion Planning are:
the right design
optimized for performance
Efficient business rules
These Essbase best practices work best when implemented all together. If you leave one best practice out, you might run into a sub-optimal solution (and I have seen a couple of examples of this). I will detail on each single best practice in the coming blog posts.
share this post