Database Reference
In-Depth Information
It may be a large or small company specializing in Essbase or it might be just a generalist
vendor. Companies, like individuals, are not all things to all men, so you must carefully
consider the strengths and weaknesses of each type of partner.
11.4.2.1.1 What Every Partner Must Have
It seems obvious that the partner you are
hiring must know Essbase. This expertise requirement needs to be stated up front, and
repeatedly, during your search and evaluation. Without it, only a measure of good luck
will ensure that your project actually finishes successfully. Do not trust fate, and do
not be shy when asking; the consulting company must have resources that can han-
dle the technical challenges that an Essbase implementation brings. Do not be shy
about requesting résumés. If you have read through some of the other chapters in this
book, you will understand that the world of Essbase is quite broad and the amount of
required knowledge is correspondingly high. good consultants will not know abso-
lutely everything there is to know about Essbase (and will not claim that they do), but
they must have the knowledge to know how and where to look it up and the ability to
apply what they discover.
Additionally, when you are interviewing potential partners, make sure that their
Essbase consultants can do more than just Essbase. Some of the necessary skills
include: scripting, SQL, project management (even if just working as a member of
a team), general oracle EPm product knowledge, and a modicum of infrastructure
expertise. A consultant who possesses all five of those skills and Essbase is a single
billable unit; do not get yourself and your company into the position of hiring six
resources where one decent consultant would suffice.
Finally, do your due diligence. research the firm's reputation and make sure to ask
for references. Check them out!
11.4.2.2 Gotchas
Be sure that the resource you interviewed is literally the person who
will be on the project or is representative of the caliber of Essbase consultant you will
get. What you do not want is to interview a “ringer,” i.e., the partner's sole Essbase hero
and then end up with something much less. There is nothing wrong in talking to star
power to give you a feel for the best the consulting company has to offer, but realism has
to temper this exchange. Ask specifically for representative consultants, not the oracle
ace, unless he/she will be on your project. to be fair to the consulting company, it is
almost impossible, particularly when the selection process and the actual implementa-
tion are months apart, to get the consultants in october who were presented in April.
Consulting income is tied to billable hours and, when consultants are on the bench, they
are a dead loss to their employer; they are going to get placed as soon as possible. It is up
to you to research the partner and make sure that they can backfill with similar quality
consultants. Then make your decisions quickly, or learn to accept equivalent substitutes.
What you never want to do is to end up being a school for consultants. It is imperative
that the Essbase consultant can hit the ground running and learn whatever particular
minor technology he needs, as required. you do not need to engage the guy who does
not know a dense block from his elbow or his aggregate view from his you-know-what.
you are paying for expertise and should get the same. If you are not getting the exper-
tise you expected, raise the issue with your engagement manager and, if you do not get
satisfaction, bounce him and maybe the partner out the door.
A last suggestion for everyone's sanity. make sure that you hire the right resources
for the project. hyperion consultants designing a data warehouse are not a pretty sight
