What one thing would you have done differently in implementing Hyperion Planning? It might be something technical, or something involving getting buy-in, or how you worked with your vendor... or really anything. But if you could have done just one thing differently, what would it have been?
Hyperion Planning -- Implementation Pitfalls to Avoid?
Answers
Don't buy it. I consider Hyperion Planning overpriced.
1
Agree with Patrick. Overpriced and architecture is overly complicated. Lots of potential functionality to be sure, but at what TCO vs. benefits realized?
Get out a big marker board and design architecture that supports the end users. Draw it all out. What will be the parent/child hierarchies? What level of detail will you enter? Will every cost center look the same? Form a team of people and get input – which will get you buy in.
The decisions about versions, time, cost center, to forecast W&S by job codes, or head count, or individuals, all should be thought through carefully. My advise – spend three times more than your implementation time line planning out all the details.
<
Filed Under:
FP&A