new & emerging _ soner bekir _ the 5 most common pitfalls when implementing epm suite.pdf

The most comprehensive Oracle applications & technology content under one roof The most comprehensive Oracle applications & technology content under one roof

The 5 most common pi.alls when implemen2ng EPM Suite…and how

to avoid them

Soner Bekir

The most comprehensive Oracle applications & technology content under one roof

About me

•  22 years of varied IT Experience •  7 years implemen>ng Hyperion environments •  5 years in EMEA, 2 years in APAC •  No func>onal knowledge to speak of •  Officially (if there is such a thing) an EPM Technical Consultant


A show of hands

•  How many group finance oriented staff? •  How many IT Technical staff? •  How many Func>onal consultants? •  How many Oracle staff? •  How many people in the wrong session?


Another show of hands

•  Anyone here who is planning on implemen>ng an EPM environment, but hasn’t done so yet?

•  Anyone here on a pre-‐System 11 environment looking to upgrade?

•  Anyone on EPM 11.1.2 ?


Ques>ons

•  Welcome at any >me – just grab my aYen>on

•  Does anyone have a ques>on they would like to see answered in this session?


The Art of EPM War

If ignorant both of your enemy and yourself, you

are certain to be in peril

Sun Tzu


What’s the Goal?

•  Project should be delivered on >me/budget •  Environment should perform well •  Stability should be good •  Availability should be good •  Users should be happy


No. 1 -‐ The clue is in the name

Enterprise Performance Management

•  Not “run it on my laptop” performance management or Hyperion Enterprise v4.0

•  Needs lots of resource(s) to run well….


EPM Install Guide


Sizing

•  Art or Science? •  No subs>tute for stress tests •  Plaeorm is a marriage, sofware is a fling •  Budget for life>me of environment •  Choose the right plaeorm for you


No. 2 – “What do you mean 90-‐days to get an environment we can use?”

Mee;ngs are indispensable when you don’t

want to do anything

John Kenneth Galbraith -‐ economist


Corporate IT

•  The 4 p’s – Planning “Surprise – we bought a business cri>cal applica>on”

– Procurement “What do you mean it takes 30 days to buy some servers?”

– Procedures “Do we really need management sofware”

– Policies “Company policies dictate that nothing that does anything useful should work”


Reality check

•  90 days •  Group Policies can cost you tens of thousands in consultancy & mee>ngs

•  List of what to order – Catch-‐22 •  Death by mee>ngs (minutes?)


No. 3 – “Yes, I can install it on anything, but anything is not

supported”

Two things are infinite: the universe and human stupidity; and I’m not sure about the universe

Albert Einstein


Choices

•  Plaeorm & Sofware – Now + 3 Years – Server Opera>ng Systems – Database Choices – Office Produc>vity Suite Choices – Browser Choices – Client Opera>ng System Choices


KISS Methodology in design

•  If 80% of the user community use it, it’s probably been tested

•  Be the first, be the worst (especially for upgrades) – have a really good reason

•  Just because you can, doesn’t mean you should


No. 4 – “What do you mean on-‐going maintenance?”

It is the neglect of ;mely repair that makes

rebuilding necessary

Richard Whately – 1826 Logician


No. 4 – “What do you mean on-‐going maintenance?”

•  The 3 P’s – Patching, Patching & Patching

•  Clean it up or slow it down

•  DP (always beYer than DR)


See Point 1

•  Plan & Budget for maintenance •  Communicate your cri>cal periods Issues caused by normal IT maintenance is the biggest single cause of down;me for all the

EPM environments we support Soner Bekir -‐ Infratects


No.5 – “and here’s another thing we forgot…”

•  Access Methods – Web, Smartview, Citrix •  User Loca>ons – Time-‐zones/network •  Support – users, IT, func>onal administrators •  Training -‐ users, IT, func>onal administrators


The end is nigh

•  Involve IT early and start the design process as soon as you have commiYed to the sofware

•  Consider the life>me of the environment, how it will be used and how it may grow & change when sizing it

•  Make mainstream choices that fit your corporate IT competencies


The end is nigher

•  Communicate your financial repor>ng calendar and work out when your environment is used

•  Build a maintenance calendar around your financial repor>ng calendar

•  Map-‐out your support organisa>on and work on your training plan

•  Budget for everything!!!


Ques>ons?


Many Thanks

Ques>ons (if you have any) can be sent to

[email protected]

new & emerging _ soner bekir _ the 5 most common pitfalls when implementing epm suite.pdf

Technology