DRM on Steroids: Multi-Product Master Data Management for a $20B Hospital System

1. DRM on Steroids
Multi-Product Master Data Management
for a $20B Hospital System
Pete Puskar & Jeff Flak
Edgewater Ranzal

2. About Us

3. Our Services
Financial Close &
Consolidations
Business
Intelligence
Enterprise
Planning &
Analytics
Data Integration
Services
Training &
Support Services
Advisory ServicesInfrastructure
Costing &
Profitability
Mgmt
Data Integration Services
• FDMEE, ERPi & FDM Classic
• ERP Integration including EBS,
PeopleSoft & SAP
• Master Data Management (DRM)
• Automation

4. Agenda
Overview of MDM and DRM
Case Study: Current Situation Analysis
Case Study: Solution
Case Study: Results
Q&A

5.  Master Data Management (MDM) is a discipline used by
organizations to ensure uniformity of key reporting structures
across the Enterprise
 Key Organizational Benefits of MDM
● Central management of reporting structures for common definition and
consistent downstream system consumption
● Consistency across the organization for key reporting metrics
● Enforcement of organizational business rules for master data
Overview of MDM

6.  Oracle Data Relationship Management (DRM)
● Management of Common Dimensions
● Analysis of Master Data
● “What-If” Modeling
● Mappings Embedded in the Structure
● Rapid Expansion of DRM Footprint
● Workflow approval processes
Overview of DRM

7.  DRM can be used to manage common dimensions for ERP, EPM
and EDW systems
 GL segment structures can be authored and/or managed within
DRM
 The GL segment structures are used as a baseline for EPM and
EDW consumption
● The entire structure (or subset of the structure) can be sent to each
system depending on the granularity of their reporting requirements
Management of Common Dimensions

8. Management of Common Dimensions

9.  Search the hierarchies in order to understand the source of your
master data
 Compare current hierarchies to how they were structured at a
specific point in time
Analysis of Master Data

10.  Validate master data
using defined business
logic
 DRM provides powerful
audit capabilities to
allow insight into who
changed what and when
Analysis of Master Data

11.  DRM can facilitate “What-If” modeling related to
reorganizations and M&A activities
 DRM allows the latest version of the structures
to be copied and modified to model the
potential changes
● Current version of structures are still used in
production systems until the changes are approved
“What-If” Modeling

12.  Ancestor / Descendant mapping relationships are easily derived for
consumption
● Example: All base level Departments that report to a specific Vice
President
 Legacy GL is mapped to Corporate GL for loading data to
consolidation systems
Mappings Embedded in the Structure

13.  Once hierarchies exist in DRM, the effort to
create a feed for a new system is fairly quick
● Properties, Queries and Exports for the new feed
can generally be adapted from existing feeds
 The feed can be exported to flat file or staging
table, and formatted to meet any subscribing
system specifications
Rapid Expansion of DRM Footprint

14.  Data Relationship Governance (DRG) allows
for workflow approval processes to be
configured directly in DRM
 Validations and notifications can be included
Workflow Approval Processes

15. DRM UI: Home

16. DRM UI: Hierarchy Tree

17. Agenda
Overview of MDM and DRM
Case Study: Current Situation Analysis
Case Study: Solution
Case Study: Results
Q&A

18.  CHE Trinity Health: $20B hospital system
 Sources
● PeopleSoft GL
● PeopleSoft HR
● Lawson ERP
● Custom EDW
 Targets
● Hyperion Enterprise
● Eighty (80) Essbase cubes 7.x
● Financial Analysis cubes
● Flex Budget cubes
● Implant Spend cubes
● Inventory cubes
Case Study: Before Picture

19.  Essbase outlines out of sync with each other
 Enterprise COA out of sync with Essbase
 Manual outline edits not auditable
 Complex data load mappings embedded in hierarchies
had to be maintained manually
 Building Essbase cubes for new hospital systems was
very time consuming
Case Study: Known Challenges

20.  Improve administration time
 Improve consistency across all cubes
 Reduce manual and redundant maintenance
Case Study: Objectives

21. Agenda
Overview of MDM and DRM
Case Study: Results
Q&A
Case Study: Current Situation Analysis
Case Study: Solution

22.  Target applications
● Replace Hyperion Enterprise with HFM (EPMA)
● Upgrade Essbase 7.x to 11.x
 Data integration (FDM)
● Replace Hyperion Application Link (HAL), Essbase Integration
Services (EIS), and Essbase load rules
 Metadata integration (DRM)
● Replace HAL, EIS, Essbase load rules, and manual outline
edits via Essbase App Manager (Pre-EAS)
Case Study: Upgrade Project

23. Case Study: Post-Upgrade
PeopleSoft
GL
Custom
EDW
PeopleSoft
HR
Lawson
ERP
DRM
Financial
Essbase
Cubes
HR
Essbase
Cubes
EOQ
Essbase
Cubes
HFM
(EPMA)
Administrator
Enrichment
• Accounts
• Departments
• Accounts
• Departments
• Entities
• Segments
• Vendors
• Supplies
• Job Code
• Job Code
• Physicians
• Vendors
• Supplies
• Accounts
• Entities
FDM
• Mappings
Data
Metadata

24.  Automated CDC process provides the latest master data from the
source systems
 Application-specific properties facilitates subsets of the dimension
structures for each application as required
● Logic does most of the work, minimizing maintenance
● Administrator can make exceptions as needed
 Automated downstream integration pushes application-specific
dimensions to target applications
● Essbase: Import via load rules
● HFM: Import via import profile
Case Study: MDM Design

25. Case Study: Subscription Example

26.  Identify new nodes and property changes to
existing nodes, and load to DRM
 Examples
● A new account is added in PeopleSoft
● An existing account is moved in PeopleSoft
● An account’s description (member alias in Essbase)
changes in PeopleSoft
Case Study: CDC Design

27. Case Study: CDC Process

28. Agenda
Overview of MDM and DRM
Q&A
Case Study: Current Situation Analysis
Case Study: Solution
Case Study: Results

29.  Manual maintenance reduced
by nightly and on-demand
updates
 Avoid double-work by sharing
dimensions
Case Study: Results – Efficiency

30.  Shared dimensions eliminate disparity across
target applications
 Different parts of the business may leverage
the same master data source – no translation
required
Case Study: Results – Accuracy

31.  Everyone still kept their jobs
 Time better spent on value-added
activities
● Better support for end users
● TPS reports
Case Study: Results – Workforce

32.  CHE Trinity Health recently bought a new
hospital
● Now takes only 1-2 months to get fully integrated
with the organization on Essbase/HFM
● Formerly a 6-month process
● Leave the new hospital on current GL – just map to
the master COA
Case Study: Results – Example

33.  Finance and IT needs to be closely-
integrated yet abide by clearly-defined
roles
 Organizational change management is a
hurdle
Case Study: Lessons Learned

34.  Scott Nelson
● CHE Trinity Health
● Sr. Systems Applications Specialist
● nelsonsd@trinity-health.org
 “The opportunity to leverage these COAs for
other teams within the org is huge.”
 “DRM absolutely made our lives easier.”
Case Study: Client Contact

35. Agenda
Overview of MDM and DRM
Case Study: Results
Case Study: Current Situation Analysis
Case Study: Solution
Q&A

36. Pete Puskar
ppuskar@ranzal.com
Jeff Flak
jflak@ranzal.com
Edgewater Ranzal
Q&A