Mastering Oracle® Hyperion EPM Metadata in a distributed organization

Mastering Oracle Hyperion EPM Metadata in a Distributed Organization

United Technologies Corporation Case Study

Conrad Chuang Orchestra Networks

Eric Belmont United Technologies

Corporation

l  Overview: Challenges and options for managing Oracle EPM Metadata

l  Case Study: Mastering EPM Metadata at United Technologies Corporation “How we manage over twenty HFM…”

l  Q&A

Today’s presentation

2

What’s a MDM/RDM vendor doing at an Oracle Development Tools User Group?

3

Customers wanted to use our MDM/RDM solution to manage our EPM and corporate finance master/reference data.

The metadata our customer wanted to manage

4

Identifiers

Attributes

Hierarchies

Identifiers, attributes and dimensions for account, entities…

Standard and Alternate Hierarchies

The challenges our customers wanted to address …

5

Managing a single instance and sync

between other instances

HFM

Essbase

Planning

ERP etc

Corporate HFM

BU 1 HFM BU 2 HFM

BU 2.1 HFM

Sharing between different applications

(EPM and non-EPM)?

As-of Current

Effective Dated

Maintaining past, present, future and what-

if versions?

What-if?

Many customers were trying to replace manual processes with excel, custom developed software, or Oracle DRM

(3) Export dimensions and update Hyperion applications via file (APP, XML), ETL-batch, or real-time

Our solution, EBX5 for Hyperion applications

6

(2) End users & EPM administrators maintain metadata/hierarchies using Browser-based User Interface with Built-in Workflow

(1) Import dimensions from HFM/Essbase/Planning via: file (APP, XML), ETL-batch, or real-time (ESB)

(1) Import other master data from

any source system ERP Essbase HFM HFM Essbase ERP Essbase Planning

Central MDM with pre-built dimension models

l  Systems integration with multiple versions of Oracle EPM applications and other enterprise applications

l  Governance with distributed workflow to manage change request process

l  Easy-to-use user interfaces and integration with Excel l  Support for past, present, future, and hypothetical

versions l  Tools to manage standard and alternate hierarchies l  Simplified pricing model with cost predictability

A summary of our customers top requests

7

One well-integrated, easy-to-use, cost-effective solution to master our EPM metadata

Case Study: Mastering EPM Metadata at United Technologies

Corporation

a.k.a. how is a customer actually using the EBX5 solution?

8

United Technologies (UTC) Overview

" Mul$ple  business  units  " 218,300  Employees  " 4,000  loca$ons  in  71  countries  " 1,000+  legal  en$$es  " Conducts  business  in  about  

180  countries  " 24th  largest  US  manufacturer  " 48th  largest  US  corpora$on  " 120th  largest  company  in  the  

world  

9

Building & Industrial Systems

Aerospace

Otis 20%

UTC Climate,

Controls & Security

26% Pratt & Whitney

23%

UTC Aerospace Systems

21%

Sikorsky 10%

Net Sales $63,394M

UTC Overview FY2013

10

Otis 27%

UTC Climate,

Controls & Security

27%

Pratt & Whitney

19%

UTC Aerospace Systems

21%

Sikorsky 6%

Operating Profit $9,668M

Our challenges

11

●  Request of changes from business units to Hyperion Center of Excellence (COE)

●  Mass Adds/Deletes/Changes ●  Mass Moves/Reorgs ●  Shared members/DUP!s ●  Business Unit confidence in the changes being

made ●  Upgrade from System 9 to System 11 ●  Quick HFM to EBX conversion

Hyperion Center of Excellence (COE)

COE/Shared service maintains Hyperion at the direction of the business units

12

Sikorsky

Climate, Controls, Security

UTC Aerospace Systems

Otis

Pratt & Whitney

UTC Corporate

Business units (BU) and the Hyperion Center of Excellence (COE) work together to maintain metadata. COE is a shared service

Business Units (BU)

The scale of the UTC Implementation

Production ●  (7) Hyperion Financial

Management App Servers

●  (6) IBM WebSphere Servers (SS, SV, WS)

●  (2) SQL Servers ●  (24) Production

Applications ●  (1) EBX5 MDM

13

Example change process: New Entities

14

Field request for new

entity(ies)

New Legal

Entity?

BU Controllers provide: •  GEMS ID & Inherit

Country

BU Tax Review & Approval

NO

Tag to existing LE parent in

LE Hierarchy (or NEW if unknown)

YES

WHQ Approve

New Entity

YES

Include new Rainbow file

Rainbow File

New entities

added to EBX5

HFM and Tax

Instances

Upload to HFM

New version required

?

Snapshot old and create new

version (dataspace)

2

3

1

“Requirements Template”

Was: Rely upon an spreadsheet to capture HFM metadata changes

15

No governance! No workflow! No comparison! DUP!s

“Rainbow file” used as a means of expressing what needs to be changed.

Now: Rainbow file generated by EBX5 is used to capture BU updates

16

1

l  Versioning was a delete of the original version, then a copy of the latest modified to the “Base” version.

l  After 3 years of use the versions were many and hard to find. Eventually to be deleted to clean the screen up of old versions

Was: Versioning

17

Now: EBX5 maintains all versions of our metadata

18

2

EBX5 maintains all versions: as-of, current, effective dated and pre-approval (hypothetical)

Now: EBX5 can be used to create comparison reports between versions

19

2

Was: Integration with HFM

20

After BU submitted the Excel template a UTC-maintained Excel Macro created the DRM Automator files

DRM

The DRM Automator file was loaded in to DRM where the changes were debugged, and verified

Automator

UTC maintained Books in DRM generates an APP file which was then loaded into HFM

APP File

Books

Now: EBX5 exports updates for HFM in an appropriate format

21

3

1. EBX5 generates a Rainbow XLS with the current metadata & hierarchies for the BU to edit.

2. Rainbow XLS is re-imported into a new version/staging area in EBX5

APP File

XML File

3. After verification, either an XML (11+) or APP file is created and loaded into HFM

4. Occasionally, data is re-imported into EXB5 from HFM to ensure synchronicity

Example M&A Use case

22

APP File

APP File

APP File

APP File

Accounts

Entities

Customs

A new HFM App for the acquisition or reorg is set up quickly through direct edit of the app files by the team

Consolidated App file is exported and imported into EBX5 to verify the changes

APP File

XML File

Final updates are exported by EBX5 and imported into HFM

Why we selected EBX5

•  The ability to make mass organizational changes using an excel export, modify, load process.

•  Ease of HFM to Dataspace Conversion. No downtime.

•  Handles moves, removes correctly (DUP!s) •  Change reporting- Confidence in changes. •  Workflow

23

Thank you!

24

Conrad Chuang Orchestra Networks conrad.chuang@ orchestranetworks.com

Eric Belmont United Technologies Corporation eric.belmont@utc.com