k14 Hfm Diet

(1)

The 200 GB diet

_or

“how I archived off the

first 10 years of my application!”

(2)

Focus

Services

People

Methodology

Customers

Partnership

15 Years 15 Years 700+ clients 700+ clients 1000+ projects 1000+ projects

About Edgewater Ranzal

(3)

We offer a full spectrum of EPM/BI Services We offer a full spectrum of EPM/BI Services

Dashboards & Scorecards, Financial Analytics & Reporting, Operational Analytics,

What-if Analysis, Query & Reporting, Visual Exploration

Financial performance, Legal, Segment & Mgmt Reporting, Financial Close HFM Optimization, Performance Lab SOX Compliance Support

Strategic Finance, Planning, Budgeting, Forecasting, Workforce Planning, Capital Planning, Project Financial Planning

Data Integration, Financial Data Management, Data Warehousing, Master Data Management &DRM, ETL Services, Automation

Project/Program Mgmt, EPM Road Maps, Application Reviews, Business Requirements, Process Change, Documentation Installation, Upgrades,

Migration, System Monitoring, Backup and Recovery, Disaster Recovery, Load Testing, Hardware Sizing, Exalytics

Benchmarking Consolidation Consolidation Business Business Intelligence Intelligence Enterprise Enterprise Planning Planning Infrastructure Infrastructure Training & Training & Support Services Support Services Project Project Management Management Data Data Services Services Costing & Costing & Profitability Profitability Mgmt Mgmt

Support Services – Infrastructure & Application Support Contracts Key Teach Course Delivery: Planning, Essbase,

Financial Reporting, Smart View, HPCM, HFM, FDM, DRM, OBIEE

Custom Training Delivery: Process & Reporting

HPCM Standard & Detailed Models, Waterfall Allocations, Activity Based Costing, Customer, Product & LOB Profitability

(4)

To

(5)

On Average Applications:

 that are 2-3 years old can

average 10GB to 15GB  25GB to 50GB are also common  100GB to 300GB are rare  500GB and 1TB are mythical

Too much of a good thing…

(6)



Determine the current

DB/schema size



Every Scenario/Year

has its own table



1 GB = 1024 MB =

1,073,741,824 Bytes

Data Analysis

(7)



A large application doesn’t inherently

mean slo!"



!emem"er - #B and application

per$ormance are independent

● "%t #B per$ormance can in$l%ence app



Application per$ormance is a $%nction o$

data %sage

● And r%les& And application tier hard'are&

Before you #egin

(8)

There is no Archive Data"Archive Data" $eat%re(

$an %&M do this automatically'

It’s D(I()(

But How?

(9)



#e$ine )

*

● Need to access the historical data ● Reduce the data set going forward



+reate a second read only )historical*

application



,eep only re%ired scenarios

● Act%al. Act%al at B%dget rates. Act%al at /orecast

rates

The patient must minister to

himself…

(10)

Ans'er 2 %estions:

1& ill  go to ail

i$  delete this data4

2& +o%ld  "e $ired

i$  delete this data4

*is+ Assessment or

Lets !ill all the

law"ers…

(11)

$ase Study, $odename

-enti

$ase Study, $odename

-enti

 11GB o$ data in non-essential scenarios

(12)

#hats $one is $one…



%istorical application

%istorical application 'ill only contain data

that 'as reported

(13)

Tomorrow% and Tomorrow% and…

 To restrict the

e8pansion o$ the ne' application. instit%te policies that 'ill limit si9e

 ,eep /orecasts

only 2 years

 Other scenarios

'ill "e %sed as needed then the data 'ill "e

dropped a$ter 12 months

(14)

Good &iddance…



_{Old application 'as}

_25GB



e' Applications are

;3GB



A reduction of ..0B or

1



nstit%te policies to prevent

gro'th $or non-essential

scenarios

(15)



<aying good"ye to old data. no' 'hat4



'pgrading??

● $ yes. then leverage converted Application $or

data validation and create 2 ne' apps

● $ not. can the environment handle another

application4



Bene$its o$ ne' applications =

no (un!)

● nvalid records and %nnecessary data(

● ,eeping only relevant data >smaller applications?

*arting is such sweet sorrow…

(16)



T'o choices:

●

Old data in ne' str%ct%re

●

Old data in a static str%ct%re

A lean and h

A lean and hungr" loo!…

ungr" loo!…

Don’t overthink

history!

(17)



Application Type:

$lassic

$lassic or

+*,A

4



$ @MA 'hen4

● <tart proect in @MA ● or convert later4

Synchroni2e Applications

(18)



Beginning "alances4

● #o yo%r c%stoms have ad%stment mem"ers4 ● ill yo%r r%les 'or 'ith a ne' start year4



Cistorical #ata4

● Do%rnals or not4 E@+TF can "e loaded to

E@+F

● oad in local c%rrency. not in arent +%rrency

3uestions to $onsider'

(19)



One r%le $ile or t'o4

● One r%le $ile is easier to maintain "%t the

c%rrent $ile 'ill need to "e %pdated

● everage Cs&Applicationame>? sAppame H C<&Applicationame>?

$ sAppame H )e'App* Then

Do something…

@lse Do something else…

*ules

(20)



#oes the r%le $ile have a

start "ear

varia"le4

● $ yes. create a condition in 'hich the varia"le

has t'o options

sAppame H C<&Applicationame>?

$ sAppame H )e'App* Then

nStartYear = “00”

@lse

nStartYear = “1""”

● n not. add an empty year to the "eginning o$

the applicationn<tartIear -1

*ules4 cont(

(21)



_{M%ltiple Iear ,s}

● ill ca%se some overlap

in years "et'een applications 

+ash $lo'

● oad entire TB in st%" period >12J200K?

*ules4 final thoughts5

(22)



ho sees the Cistory4



Maing the App !ead Only

● Mae <cenario sec%rity classes !ead only

● <ec%rity +lass access is most restrictive to least

restrictive



Lsers 'ill see the st%" year

● Iears do not have sec%rity ●

Over comm%nicate this d%ring Training and Testing

Security

(23)



<mart ie'

● e' application connections are

needed

● +omm%nicate via Training and

Testing



/inancial !eports

● +an only connect to one

application

● Only certain reports access

the Cistorical app

*eporting

(24)



Data -alidation

● hat level o$ detail needs to

"e validated4

● Tools to %se4 /#M4 @8cel4

● !esponsi"ility4

● Data validation can derail yo#r

pro$ect if not properly defined!

-omething wic!ed this wa" comes…

(25)

 Migration rocess

● _{2 Applications no'}

● Lifec"cleLifec"cle

,anagement.

,anagement. nownow moves data))) moves data))) ● #ata retention policy ● !esponsi"ility4 /inance /inance vsvs 1T 1T ● #e$ine clearly. please4

Brave New #orld…

(26)



!ed%ced #B



+reated a process to limit #B gro'th



,ept Cistory

&inal 6houghts or

(27)