epma or drm—do i use one, the other, or both? · pdf filehierarchy management tool for...
TRANSCRIPT
EPMA or DRM—Do I Use One,
the Other, or Both?
Paul Hoch & Steve Davis TopDown Consulting
Paul Hoch – Experience Overview ● Over 15 years experience
delivering EPM solutions to Fortune 1000 companies
● Specializations include enterprise performance management, business intelligence, data warehousing, and custom application configurations
● Planning, Forecasting, and Analysis domain expert
● Hyperion Certified Trainer ● Product specializations include
Hyperion Planning and Hyperion Essbase and supporting products
Representative Sample of Clients ● Allianz Global Investors ● Blue Shield of California ● CooperVision ● Earle M Jorgensen ● Estée Lauder ● Lockheed Martin ● Northrop Grumman ● TransOcean
Steve Davis – Experience Overview ● Over 10 years of experience in all
phases of design, development, and implementation of EPM solutions
● Specialized in DRM implementations, including integration with HFM, FDM, Planning, Essbase, EBS, Peoplesoft, SAP, OBIEE, Datawarehouse (teradata), as well as various other applications
● Data manipulation and implementation expert
● Designed MDM solutions around legal and company requirements leading upgrade of a technical infrastructure project
Representative Sample of Clients ● JP Morgan Chase ● Dell ● Clorox ● UTMB ● Bimbo Bakeries ● Lockheed Martin ● Gilead Sciences
CORE ISSUE
These days, companies are under increasing pressure to improve value, accountability, performance, and quality in order to accommodate the demands of
stakeholders, customers, employees, government regulations, and reporting while simultaneously meeting the exacerbated demand to cut costs,
improve efficiency, and increase revenue.
An Example
Me!
Client Metadata
DEFINING TERMS
l Master data is shared across systems l Refers to the non-transactional data that describes a
business or other organization—e.g. ● Internal entities such as departments, employees
and products; ● External entities such as customers and suppliers;
and ● Organizational information such as reporting
hierarchies and the chart of accounts. l Masterdata is required to support transaction
processing, and to organize reporting and analysis
What is Master Data?
l Data about data 1. Data about the organization of data, such as the
columns and tables in a database and the relationships between them
2. Information about the content of data ● Summaries of contents, keywords for
searching, and information on the source and owner of the data.
l Essential component of information contained in the transactional systems across an organization
What is Metadata?
l Masterdata are typically the nodes in the hierarchies (Accounts, CostCenters, ProfitCenters, Departments)
l Metadata is the properties created to describe the Masterdata (description, parent, datastorage, etc)
It is also important to understand these applications manage the masterdata / metadata for other applications, but they also have their own metadata.
Metadata vs. Master Data
MANAGING YOUR METADATA
Oracle offers two different tools that operate as a single point of maintenance for metadata: l Enterprise Performance Management Architect
(EPMA) l Data Relationship Management (DRM)
Single Point of Maintenance
l HMS l Maslow l Razza l MDM l BPMA l DRM l EPMA
History Lesson
l Hierarchy management tool for the EPM suite of applications—Hyperion Planning, HFM, and Essbase Manages metadata like dimensions, hierarchies, data loads across product sets etc.
l Communicates directly with the Hyperion applications, which alleviates the need to write any custom integration
l Streamlines work with either the full suite or a subset of the applications by easing maintenance between them and maintaining consistency
l Analyzes data in a real-time architecture
EPMA – An Overview
l One interface for loading meta-data and data, managing and deploying application architecture etc.
l Create applications by dragging and dropping l Design application graphically within one environment l Create subject-specific application that use existing
artifacts l Graphically manage data flows l Upgrade applications from previous releases to place
them in the Dimension Library and Application library
How Does EPMA Work?
How Does EPMA Work?
l DRM is a hierarchy management tool l DRM helps manage master data across multiple
systems keeping them in sync l DRM creates one version of the truth l Simplify processes and responsibilities l Align dimensions across all systems l Apply data governance through audit and change
control l Mitigate risk of financial misstatement with
consistent workflows
DRM – An Overview
How does DRM work?
GL HR Legacy GL Supply Chain
Data Warehouse
Analytic Engines HFM Planning
Source Systems
Reporting & Analysis Tools Standard Reports, Adhoc Analysis, Data Mining, Dashboarding & Performance Scorecards
Data R
elationship Managem
ent
Copyright © 1997-2012 interRel Consulting presentation. All rights reserved.
MATCHING APPLICATIONS & TECHNOLOGY
Feature Sets – EPMA vs. DRM EPMA DRM
Aligns Hyperion Applications X X
Aligns Other Applications X
Imports Hierarchies from other sources X X
Validates the Hierarchies X X
Compare hierarchies from other systems X
Create custom properties X
Versioning X
Modeling X
Custom Validations X
Configurable exports X
Security down to the node level X
Audit Tracking X
SOX X
Workflow X
EPMA & DRM – REAL WORLD EXAMPLES
l Naming conventions
Common Scenarios
l Managing multiple, disparate applications ● A Global 2000 company managing four applications—the GL, HFM, Hyperion
Planning, and Essbase—decides to introduce a new account, which will be used for different purposes in each application: • GL: financial reporting • HFM: external reporting—e.g., reporting to “the street” • Essbase: internal reporting • Hyperion Planning: for anticipating future scenarios and needs
Common Scenarios
ESSBASE PLANNING HFM
Oracle GL
l Organization hierarchy
Common Scenarios
EPMA
ESSBASE PLANNING HFM
l Managing multiple, disparate applications using EPMA & DRM
Common Scenarios
EPMA
ESSBASE PLANNING HFM
Oracle GL HR
l Departmental vs Enterprise roll out
Common Scenarios
l Using EPMA where DRM is needed l Using Both EPMA and DRM
Case Studies
l EPMA – Ready for primetime? ● The ongoing “next” release
l EPMA - Shared Dimension Issues l Outline Load Utility for Planning l DRM – getting buy-in from IT l Justify the cost – Free vs additional license l EPMA – Other features (Calc Mgr, LCM, Data
Sync)
Gotchas, Alternatives, & Workarounds
FINAL THOUGHTS
QUESTIONS? COMMENTS?
THANK YOU
Paul Hoch, Principal Architect, TopDown Consulting
Steve Davis, Solution Architect, TopDown Consulting [email protected]