Seismi were invited to present a recent case study of a recent Oracle Hyperion DRM (Data Relationship Manager) and EPM installation. The case study outlines the benefits that Oracle DRM can deliver particularly the elimination of the risks of human middleware and the introduction of a fully automated and integrated financial process.
There is a description by Seismi's client's CFO and project sponsor at the outset as well as the client's reaction to the solution, which Seismi continues to support.
The case study highlighted the flexibility of DRM to be at the core of its network and its ability to integrate with multiple vendors
5. Why
masterdata
governance
(
)?
INTEGRATED
SYSTEMS
AND
AUTOMATED
PROCESSES
(With
Masterdata
Governance)
Vs
SILOED
SYSTEMS
AND
MANUAL
PROCESSES
(Without
Masterdata
Governance)
6. Agenda
1.
Masterdata
Governance
Overview
2.
Case
Study
|
Context
3.
Case
Study
|
Solu4on
4.
Ques4ons
7. Case
Study|
Technical
Overview
ERP
–
Mincom
Ellipse
En44es
–
More
than
15
ERP
Account
Codes
–
Approximately
220,000
account
codes
organised
into
mulBple
charts
of
accounts
Group
Consolida4on
Tool
–
Oracle
Hyperion
Financial
Management
Rela4onal
Repor4ng
Tool
–
Business
Objects
Analy4cal
Repor4ng
Tool
–
Oracle
Essbase
8. Pain
Points
|
Ini4al
Situa4on
(Feb
2010)
“In
our
Company
we
recognised
that
we
needed
to
make
our
financial
processes
and
supporBng
IT
infrastructure
more
effecBve.
The
issues
we
faced
included:
• an
inconsistent
chart
of
accounts;
• mulBple
off-‐book
adjustments;
• core
financial
reports
that
were
produced
using
several
applicaBons
and
sources
of
data;
• a
systems
landscape
that
had
proliferated
following
historic
mergers;
and
finally,
• an
integraBon
with
the
Group
consolidaBon
tool
which
relied
heavily
on
manual
processes.”
Chief
Financial
Officer
9. CFO|
Objec4ves
(1)
Repor4ng
&
Analysis
-‐
provide
a
standard,
efficient
method
for
generaBng
reports,
and
free-‐up
expensive
business
resource
to
P
analyse
informaBon
Standardise
-‐
create
a
standardised
view
of
Company
allowing
direct
comparison
between
mining
operaBons
on
different
Charts
of
Accounts
&
finance
system
plaXorms
P
Auditable
-‐
provide
consistent
audited
data
allowing
the
business
to
understand
the
calculaBons
underpinning
every
reported
P
number
Budge4ng
-‐
Align
budgeBng
processes
to
the
chart
of
accounts
P
Cost
Saving
–
cut
head
count
&
reduce
cost
in
the
Finance
&
IM
funcBons
P
10. CFO
|
Objec4ves
(2)
Rapid
Deployment
-‐
deliver
measurable
business
benefit
within
6
months
P
Control
-‐
single
point
of
governance
for
the
ERP
Ellipse,
ReporBng,
BudgeBng
and
mapping
to
HFM
P
Future
Proof
-‐
deliver
a
finance
hub
that
will
adapt
to
the
Company s
evolving
strategy
of
organic
and
acquisiBon
based
P
growth
Integra4on
-‐
Automate
data
transfer
between
key
applicaBons
P
Systems
Consolida4on
–
remove
unnecessary
applicaBons
and
simplify
systems
landscape
P
Data
Integrity
-‐
eliminate
off-‐book
adjustments
P
11. Tes4monial
|
Sponsor
(Sep
2010)
The
reac4on
to
Seismi s
new
solu4on
has
been
overwhelmingly
posi4ve.
It
has
given
the
finance
team
the
control
we
need
over
our
repor4ng
solu4ons,
whilst
the
reports
themselves
provide
accurate,
reconcilable
informa4on
to
our
management
in
a
4mely
and
effec4ve
manner.
It
is
envisaged
that
significant
management
4me
previously
spent
reconciling
systems
will
be
saved
as
a
result
of
the
project.
Its
flexibility
and
scalability
will
allow
us
to
adapt
to
ongoing
Group
or
local
ini4a4ves
that
my
finance
team
will
face.
he
work
performed
by
Seismi
has
been
expertly
managed
T
and
executed
in
all
areas.
We
believe
that
the
solu4on
they
have
delivered
is
world-‐class."
Chief
Financial
Officer
12. Agenda
1.
Masterdata
Governance
Overview
2.
Case
Study
|
Context
3.
Case
Study
|
Solu4on
4.
Ques4ons
14. Logical
Solu4on
|
DRM
No
limit
to
the
number
of
reports
that
can
be
defined
Reports
Ability
to
drill
in
to
transacBons,
work
orders,
Layer
equipment,
etc
Standard
view
of
the
Company
mining
business
Standardisa4on
Standardised
calculaBon
library
for
KPIs
Layer
(financial
and
non-‐financial
informaBon)
Controls
the
creaBon
of
accounts
in
CoA
Layer
(General
Ledger
General
Ledger
Governance)
Validates
each
account
created
is
mapped
to
the
standardisaBon
layer
15. Impact
on
End
Users
Minimal
change
management
–
with
the
excepBon
of
the
7
key
users
there
was
minimal
impact
on
end
users
and
as
such
no
disrupBve,
risky
and
costly
change
management
project
required.
Self
sufficiency
-‐
the
intuiBve
interface
allows
the
7
key
users
to
manage
DRM
without
costly
external
technical
support.
Stable
and
robust
–
only
two
Bckets
have
been
raised
to
our
Level
2
support
providers
(Seismi).
16. Solu4on
Component
|
DRM
Audit
capability
-‐
every
acBon
is
logged
and
Bme
stamped
Control
and
integrity
-‐
enforce
correct
data
entry
and
validate
against
defined
business
rules
Security
-‐
limit
access
by
business
funcBon
and
/
or
geography
and
limit
access
according
to
needs
Logical
hierarchy
-‐
align
CoA
to
key
business
hierarchies
to
opBmise
reporBng
and
increase
transparency
Versioning
-‐
take
copies
of
reporBng
hierarchies,
CoA
and
reports
to
allow
a
snapshot
of
the
business
at
any
given
term
Centralised
-‐
single
source
of
the
truth
for
all
core
business
metadata
(CoA,
Management
Reports
&
Mappings)
Vendor
agnos4c
–
requirement
for
a
tool
that
would
work
with
any
applicaBon
provider
given
the
different
tools
and
vendors
16
17. Benefits
(1)
Governance
Repor4ng
Integra4on
Month
End
20%
ReducBon
in
effort
during
the
month
end
process
ProacBve
not
reacBve
Reduced
reconciliaBon
Rapid,
automated
&
masterdata
governance
burden
reliable
integraBon
Improved
management
ProacBve
error
trapping
Accuracy
confidence
in
reported
through
business
rules
not
numbers
reacBve
error
resoluBon
through
human
Accurate
and
Bmely
middleware
informaBon
provided
from
both
the
general
ledger
and
EPM
soluBons
Deployment
Core
business
masterdata
Core
business
reports
can
can
be
rapidly
deployed
to
be
rapidly
deployed
to
new
new
acquisiBons
acquisiBons
Flexibility
Core
EPM
soluBon
"de-‐coupled"
from
ERP.
A
change
to
the
ERP
will
not
fundamentally
effect
the
EPM
reporBng
layer
18. Benefits
(2)
Governance
Repor4ng
Integra4on
Maintenance
Maintaining
the
Reduced
cost
deploy
new
Decommissioning
masterdata
across
mulBple
reports
applicaBons,
simplificaBon
applicaBons
requires
less
of
systems
landscape
and
people
improved
robustness
reduce
support
burden
Change
EffecBve
change
EffecBve
change
management
of
core
management
of
core
Management
business
masterdata
business
reports
Minimal
Impact
on
organisaBon
(people,
infrastructure).
PosiBve
change
for
Finance
Ownership
ApplicaBon
masterdata
Reports
owned
and
Mappings
owned
and
owned
and
changed
by
changed
by
business
changed
by
business
business
people
people
people
Risk
Internal
and
External
audit
approved
(removed
red
flag)
Month
and
year
end
risk
reduced
19. Future
–
Easing
future
implementa4ons
BO
OBIEE
Essbase
HFM
EBS
Hyperion
Planning
Business
Modelling
Strategy
&
OBI
Apps
&
Chart
Design
Architecture
FDQM
DRM
EPMA
Fusion
ERP
&
EPM
Integration Legacy
HSF
Solu4ons
Systems
Data
Ellipse
Other
ERP
ODI
Warehouse
Technologies
20. Agenda
1.
Masterdata
Governance
Overview
2.
Case
Study
|
Context
3.
Case
Study
|
Solu4on
4.
Ques4ons