The Value of Oracle Hyperion Data Relationship Management at …dbmanagement.info/Books/MIX/Oracle_Hyperion_Data_Relationship... · The Value of Oracle Hyperion Data Relationship

The Value of Oracle Hyperion Data

Relationship Management at Alberta

Health Services

1

� Stu Fowler – Alberta Health Services

� Brian Healey – Edgewater Ranzal

Property of Edgewater Ranzal

Purpose/Agenda

� Purpose: Present how AHS is implementing DRM to provide a single

source of hierarchical structure to its business and reporting schemas

� Agenda

�Stu Fowler

�The business drivers that propelled AHS to implement DRM

�Some of the business challenges along the way

�Brian Healey�Brian Healey

�How to use Oracle Hyperion Data Relationship Management for

a single version of truth for company hierarchies.

�Discover how Oracle Hyperion Data Relationship Management

serves as a solution across the enterprise.

�Get best practices for implementing Oracle Hyperion Data

Relationship Management for maximum results.

�Questions

2


Map of Alberta

3


This is AHS

Announced: May 2008

Created: April 2009

Budget: $ 13 Billion

People: 117,000

Operational Structure: In addition to

North Zone

4

Operational Structure: In addition to Alberta Health Services, there are a few subsidiaries plus one additional service provider:

Calgary Lab Services

Capital Care

Care West

Covenant Health

Central Zone

Calgary

ZoneSouth

Zone

Edmonton

Zone


History of AHS

Regional Health Authorities:

1.Chinook Health

2.Palliser Health

3.Calgary Health

4.David Thompson Health

5.East Central Health

6.Capital Health

7.Aspen Health

Health Regions - prior to April 1, 2009

5

7.Aspen Health

8.Peace Country Health

9.Northern Lights Health

Additional Entities:

•Alberta Cancer Board

•Alberta Alcohol and Drug Abuse

Commission

•Alberta Mental Health Board


The Challenge

Complexity:

AHS

Former Health Entities

Processes, policies, practices,

Normal Merger/Acquisition:

BA +

AHS Approach:

�Few systems, processes, policies, practices, disciplines and measurement

capabilities that could scale and support AHS needs

�Mergers are predominantly one organization merging with another.

�It is exponentially more complex to merge 12 entities simultaneously.

AHSProcesses, policies, practices,

disciplines, measurement,

governance systems not

completely available from any of

the prior entities.

AB

Processes, policies, practices,

disciplines, measurement,

governance systems provided by

‘A’

6


The Challenge (cont)

� No Integrated Planning Process

� Alignment between the processes is manual and offline

� Critical KPI’s not aligned between the different systems

� No Actual Data to Support Detailed Variance Analysis

Planning Process Limitations

� No Actual Data to Support Detailed Variance Analysis

� Key Metrics and Drivers not Available Systemically – Example - Setting Targets

around Productivity without insight into Actual results

� Without access to these key data points, it is very difficult to ascertain trends

and accurately forecast.

7


Implementations

Timeline:

Merger

Announcement

May 8, 2008

Oracle 12.1.1

Implementation

February 2011

Hyperion

Implementation

April 2012

Oracle 12.1.3

Upgrade

December 2012

PeopleSoft

Calgary Zone

June 2011

PeopleSoft

North Zone

March 2013

DRM

Implementation

September 2012

Legal

Entity

April 1, 2009

OBIEE 10g

Implementation

March 2011

PeopleSoft

Edmonton Zone

October 2011

PeopleSoft

Central Zone

July 2012

PeopleSoft

South Zone

December 2012

OBIEE 11g

Upgrade

January 2013

8


The Decision for DRM

� Oracle Open World 2010 - Implementing eBusiness Suite

� No consolidated Hierarchy

� GL data coming together but reporting mechanisms missing

� eBusiness Suite vs. OBIAW

� Issues around alignment

� Issues around inheritance

9

� Issues around inheritance

� Manual processes provide tremendous opportunity for mistakes

and variance

� Maintenancee nightmare

� Opportunity to discuss our problems with industry leaders

� DRM provides the mechanism we need


Hierarchy Change Stats

eBusiness Suite Hierarchy Change Request Status

As of October 28, 2011

Service Type Sum of Completed

1-Add Position with Delegation of Financial Authority (BAS – Business Advisory Services) 1,145

Fluid organization with high degree of ongoing change

2-Add Requisitioner (BAS) 1,135

3-Change Position Data (BAS) 1,063

4-Change Employee Data (HR) 1,229

5-Requests from BAS 85,060

6-Investigated Issues 1,461

7-DOFA Exceptions (BAS) 490

Grand Total 91,583

10


Current State

� Multiple Systems

� Multiple Integrations

� Multiple versions of the truth

11


OrganizationData Governance Roles

Advise in implementation of

policiesData Owners▪ Owns Master Data

▪ Approves data definitions &

standards specification

▪ Authorize access to

information

▪ Reside in business

Enterprise Data Governance Council

Data Stewards▪ Define policies

▪ Advise in implementation of

policies

▪ Plan information requirements

▪ Ensure control of information

▪ Coordinate delivery efforts

Cooperatively determine data requirements

The data governance framework is supported by leadership and the four core data governance roles,

combining both the Business and IT to ensure that the policies, procedures and standards are met.

Communicate policies and seeks

improvement

Work together toward the delivery of

information

Share information about applications and

technology

Communicate information definition and seeks improvement ideas

▪ Reside in business ▪ Coordinate delivery efforts


Data Custodians▪ Capture, store, retain,

and dispose of information

per owner requirements

▪ Design technical infrastructure

to meet requirements

▪ Ensure security of information

▪ Reside in IT / business

Data Users▪ Select the best information

source

▪ Understand the information

accessed

▪ Comply with information

management policies

▪ Create data extract to meet

specific needs


data requirements

12


Governance ModelOrganization

Governance Groups

Master Data Entities

EmployeePosition & Position

RelationshipsItems Supplier COA ….

Finance Member Owner Member Owner Owner

CPSM Member Member Owner Member Member

HR Owner Member Informed Informed Member

The following table shows the scope of each initiative, based on a tentative composition of the Enterprise

Data Governance Council.

HR Owner

IT Member Member Member Member Member

▪ Owner – Primary data owner responsible for leading the governance of a particular data entity, also

serves on the Enterprise Data Governance Council

▪ Member – Data or attribute owner who participates whenever changes to data or attributes are

required

▪ Informed – Made aware of changes to subject area and provide feedback on the impact of changes

Hierarchies Assessment

and Governance Project

The CPSM/Finance Data

Governance projectOut of Scope

13


Data Governance

The following framework defines the data governance capabilities required to implement

Technology supports common

information exchange solutions

, workflow and business rules

functionality and user

presentation/ portal to enable

Data

Architecture

Organization

Organization, chartered with

administering information

management activities,

provides a responsible

network of dedicated and/or

virtual resources to deliver

information management &

governance capabilities

Policy refers to

information

Data Architecture includes

enterprise data standards, a

business information model,

metadata dictionary and

security & privacy

presentation/ portal to enable

the enforcement and

adherence to common data

standards

Tools &

Technology

Processes &

PracticesGovernance

Metrics

Policies,

Principles &

Standards

Data

Governance

Framework

Driven

by business

value

information

management

guidelines and

principles for enforcing

data standards, and

data governance

processesProcess & Practices establishes

guiding principles outlining how

data governance policies,

processes, standards, are

created, modified and

implemented, enabling

accurate data to be leveraged

across the enterprise

Governance Metrics

establishes measures for

monitoring information

management performance

and actions to continuously

improve enterprise data

14


Road Map

15


High Level Design

Oracle Business

Intelligence and

Data Warehouse

(aka MR)

Oracle Hyperion

Data Relationship

Management

Oracle Hyperion

Planning

(aka Budget/

Planning)

Accountability

HierarchyAccountability

Hierarchy

16

Oracle eBusiness

Suite R12.1.1

(aka P2P)

PeopleSoft v8.8

(aka ePeople)

Management

Position

Employee

COA

Position

Hierarchies

•Accountability

•Authority

Accountability

Hierarchy

Authority

Hierarchy

Supplier

Items

Hub and Spoke Model

EmployeePosition

COA


Intakes/Outputs Detail

17


Design Considerations

�PeopleSoft vs. Other HR systems

�Automated feeds vs. Spreadsheets

�Hierarchy Reconciliation

�Position and Employee Number Reconciliation

�Continuing PeopleSoft Conversions

�Working Title – eBusiness vs. PeopleSoft

�DOFA – Delegation of Financial Authority

18

�DOFA – Delegation of Financial Authority

�Dual Responsibility

�Siblings

�APIs: Position, Employee, Approval Group

�DIs - Dynamic Inserts

�Management Reporting Overrides


Three Objectives

� Objectives of DRM Session

�How to use Oracle Hyperion Data Relationship

Management for a single version of truth for

company hierarchies.company hierarchies.

�Discover how Oracle Hyperion Data Relationship Management




19


About Ranzal

� Founded in 1996, Ranzal has implemented Oracle / Hyperion solutions for over 700 companies (1,000+ projects)

� One of the largest Hyperion practices in the U.S. with global presence

� Oracle / Hyperion Platinum Partner - highest status for an EPM-only partner

� Vertical expertise with high-profile clients from coast to coast

20

� Vertical expertise with high-profile clients from coast to coast

� Cover all requirements from pre-implementation process design through infrastructure and training

� ONLY “One Stop Shop” for ALL EPM implementation needsProperty of Edgewater Ranzal

One Version of Truth� Data Governance

� Data Ownership

� Timing and Scope

� Collapse separate structures into a single maintenance structure

� Positions

� Employees

� Accounts

� Responsibility

� Authority

21

� Streamline change management – one place to make changes, one structure to update

� Created 1 hierarchy from

� Multiple systems

� Multiple versions and subsets of this hierarchy

� Immediate feedback to business users to enforce system constraints, business rules

� Validations

� Publish changes for each specific consuming system as needed, when needed

� Read-only user

� Exports and queries


Proposed Solution

� AHS has purchased the Oracle Hyperion product suite that contains Oracle’s Data

Relationship Management (DRM) module.

� DRM is the solution that builds consistency, integrity and accuracy within master

data assets despite endless changes within the underlying transactional and

22

data assets despite endless changes within the underlying transactional and

analytical systems.

� Specifically, the DRM provides a data model-agnostic master data management

solution built to enable financial and analytical master data management in

dynamic, fast-changing business environments.Property of Edgewater Ranzal

Data Governance

23


Data Flows

24


Oracle Business

Intelligence and Data

Warehouse (aka MR)

Oracle Hyperion Data

Relationship

Oracle Hyperion Planning

(aka Budget/ Planning)

Accountability

HierarchyAccountability

Hierarchy

Hub and Spoke Model

25

Oracle eBusiness Suite

R12.1.1

(aka P2P)

PeopleSoft v8.8 (aka

ePeople)

Relationship

Management

Position

Employee

COA

Position

Hierarchies

•Accountability

•Authority

Accountability

Hierarchy

Authority

Hierarchy

Supplier

Items

EmployeePosition

COA


Regions

26


Solution

Position

Employee

27

Employee

Functional Centre


Across the Enterprise


�How to use Oracle Hyperion Data Relationship Management for a

single version of truth for company hierarchies.

�Discover how Oracle Hyperion Data �Discover how Oracle Hyperion Data

Relationship Management serves as a

solution across the enterprise.



28


Expected Benefits

�Single trusted source of information

�Reduction in manual maintenance effort

�Higher data integrity (less errors)

� Increased transparency of processes

29

� Increased transparency of processes

�Better decision-making

�Reduced operational friction

�Standard, repeatable processes


Statistics

P2P Hierarchy Change Request Status

As of October 28,

2011

Service Type Sum of Completed

1-Add Position with Delegation of Financial Authority

(BAS) 1,145

2-Add Requisitioner (BAS) 1,1352-Add Requisitioner (BAS) 1,135

3-Change Position Data (BAS) 1,063

4-Change Employee Data (HR) 1,229

5-Requests from BAS 85,060

6-Investigated Issues 1,461

7-DOFA Exceptions (BAS) 490

Grand Total 91,583

30


Across the Enterprise

�DRM ensures that hierarchies and classifications are aligned

across the enterprise.

�Reports and totals agree across all systems.

�Dramatic reduction in reconciliation efforts.�Dramatic reduction in reconciliation efforts.

�Confidence with business users.

�Agreement among users from different business, units and

operating, functions.

31


Best Practices


�How to use Oracle Hyperion Data Relationship Management for a

single version of truth for company hierarchies.

�Discover how Oracle Hyperion Data Relationship Management �Discover how Oracle Hyperion Data Relationship Management


�Get best practices for implementing Oracle

Hyperion Data Relationship Management for

maximum results.

32


Products– DRM Features

� Key Features to focus on:

�Custom rules and validations

�Configurable exports

�Granular security�Granular security

�Read Only User 11.1.2.1+

33


Hierarchies

� Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum

results.

� Hierarchies:

� Tree Structure vs. Warehouse

� Alternate Hierarchies

34


Properties

� Get best practices for implementing Oracle Hyperion Data Relationship Management for

maximum results.

� Properties

� Challenges and solutions

� Types, Functions, examples

35


Exports

� Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum

results.

� Exports: Varieties, challenges and solutions

36


Audit

� Get best practices for implementing Oracle

Hyperion Data Relationship Management

for maximum results.

� Leverage product functionality

� Security

� Read-only

� Granular

� Audit

37


Best Practices: Re-use

� Get best practices for implementing Oracle Hyperion Data Relationship Management for

maximum results.

� Re-use Objects

� Alternate Hierarchies

� Property Categories

� Ex: BAS manager categories

� Properties� Properties

� SYS_ properties reused

� Prefixes

� Queries

� Re-use for common elements

� Exports

� System Export, filter

38


DRM Benefits

� Single Version

� Enables organizations to Generate trustworthy insight with high quality master data.

� Build consistency based on governance standards.

� Across the Enterprise

� Improve TCO with streamlined data maintenance.

� Manage change of business master data across enterprise applications.� Manage change of business master data across enterprise applications.

� Consolidate and rationalize structures across source systems.

� Conform dimensions and validate integrity of attributes and relationships.

� Synchronize alternate business views with corporate hierarchies.

� Best Practices

� Product Features, Leverage, and Re-use.

39


Questions?

40


Enables organizations to …

Contact Information:

Brian Healey

Principal

Ranzal

Enables organizations to …

Contact Information:

Stu Fowler

Systems Architect

AHS Ranzal

[email protected]

www.ranzal.com

41

AHS

[email protected]

http://www.albertahealthservices.ca


Documents

The Value of Oracle Hyperion Data Relationship Management at …dbmanagement.info/Books/MIX/Oracle_Hyperion_Data_Relationship... · The Value of Oracle Hyperion Data Relationship