Your SlideShare is downloading. ×
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services (AHS)

3,440

Published on

Plagued by data inconsistencies, Alberta Health Services (AHS) lacked the necessary processes and tools to manage information. It opted to implement Oracle Hyperion Data Relationship Management to …

Plagued by data inconsistencies, Alberta Health Services (AHS) lacked the necessary processes and tools to manage information. It opted to implement Oracle Hyperion Data Relationship Management to address its needs. Edgewater Ranzal delivered a solution to manage information between Reporting, Oracle Hyperion Planning, and several other AHS services/groups. The solution enables financial and analytical master data management in AHS’s dynamic, fast-changing environment. The goal was to achieve a single trusted source of information, reduction in manual maintenance effort, higher data integrity, increased process transparency, improved decision-making, a decrease in operational friction, an overall reduction in costs, and improved effectiveness.

Published in: Technology
1 Comment
1 Like
Statistics
Notes
  • http://www.dbmanagement.info/Tutorials/DRM.htm
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
3,440
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
100
Comments
1
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The Value of Oracle Hyperion Data Relationship Management at Alberta Health Services nzal Ra at er ew E dg y of p ert P ro Stu Fowler – Alberta Health Services Brian Healey – Edgewater Ranzal1
  • 2. Purpose/Agenda Purpose: Present how AHS is implementing DRM to provide a single source of hierarchical structure to its business and reporting schemas al Agenda Stu Fowler nz Ra er The business drivers that propelled AHS to implement DRM at Some of the business challenges along the way ew dg Brian Healey E of How to use Oracle Hyperion Data Relationship Management for y ert a single version of truth for company hierarchies. ro p Discover how Oracle Hyperion Data Relationship Management P serves as a solution across the enterprise. Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results. Questions2
  • 3. Map of Alberta al nz Ra at er ew E dg y of p ert P ro3
  • 4. This is AHS Announced: May 2008 Created: April 2009 al Budget: $ 13 Billion nz Ra Zone People: 117,000 at er North ew Operational Structure: In addition to E dg of Alberta Health Services, there are a Edmonton rty few subsidiaries plus one additional Zone service provider: e Pr op Calgary Lab Services Central Zone Capital Care Calgary Care West Zone South Covenant Health Zone4
  • 5. History of AHS Regional Health Authorities: Health Regions - prior to April 1, 2009 1.Chinook Health al 2.Palliser Health 3.Calgary Health nz 4.David Thompson Health Ra 5.East Central Health at er 6.Capital Health ew 7.Aspen Health E dg 8.Peace Country Health y of ert 9.Northern Lights Health rop P Additional Entities: •Alberta Cancer Board •Alberta Alcohol and Drug Abuse Commission •Alberta Mental Health Board5
  • 6. The ChallengeComplexity: al Former Health Entities Normal Merger/Acquisition: AHS Approach: nz Ra er A + B at AHS ew Processes, policies, practices, E dg Processes, policies, practices, of B AHS A disciplines, measurement, disciplines, measurement, y governance systems not ert governance systems provided by ‘A’ completely available from any of p the prior entities. P ro 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.6
  • 7. The Challenge (cont)Planning Process Limitations al No Integrated Planning Process nz Ra Alignment between the processes is manual and offline er Critical KPI’s not aligned between the different systems at ew dg No Actual Data to Support Detailed Variance Analysis fE yo Key Metrics and Drivers not Available Systemically – Example - Setting Targets ertkey data points, it is very difficult to ascertain trends around Productivity without insight into Actual results Pr op Without access to these and accurately forecast.7
  • 8. ImplementationsTimeline: PeopleSoft DRM PeopleSoft Calgary Zone Implementation North Zone al June 2011 September 2012 March 2013 nz Ra Merger Oracle 12.1.1 Hyperion Oracle 12.1.3Announcement Implementation Implementation Upgrade er May 8, 2008 February 2011 April 2012 December 2012 at ew E dg y of p ert Legal P ro OBIEE 10g PeopleSoft OBIEE 11g Entity Implementation Central Zone Upgrade April 1, 2009 March 2011 July 2012 January 2013 PeopleSoft PeopleSoft Edmonton Zone South Zone October 2011 December 20128
  • 9. The Decision for DRM Oracle Open World 2010 - Implementing eBusiness Suite al No consolidated Hierarchy nz Ra GL data coming together but reporting mechanisms missing eBusiness Suite vs. OBIAW at er ew Issues around alignment E dg Issues around inheritance of Manual processes provide tremendous opportunity for mistakes y and variance p ert P ro Maintenancee nightmare Opportunity to discuss our problems with industry leaders DRM provides the mechanism we need9
  • 10. Hierarchy Change Stats Fluid organization with high degree of ongoing change eBusiness Suite Hierarchy Change Request As of October 28, Status al 2011 nz Ra Service Type Sum of Completed at 1-Add Position with Delegation of Financial er ew Authority (BAS – Business Advisory Services) 1,145 2-Add Requisitioner (BAS) E dg 1,135 y of ert (HR) 3-Change Position Data (BAS) 1,063 Pr op 4-Change Employee Data 1,229 5-Requests from BAS 85,060 6-Investigated Issues 1,461 7-DOFA Exceptions (BAS) 490 Grand Total 91,58310
  • 11. Current State Multiple Systems Multiple Integrations Multiple versions of the truth al nz Ra at er ew E dg y of p ert P ro11
  • 12. Organization Data Governance Roles 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. Enterprise Data Governance Council al nz Stewards Ra Advise in implementation of Data er Data Owners policies at ▪ Owns Master Data ▪ Define policies ▪ Approves data definitions & ▪ Advise in implementation of ew standards specification policies ▪ Authorize access to ▪ Plan information requirements dg Cooperatively determine ▪ Ensure control of information information data requirements ▪ Coordinate delivery efforts E ▪ Reside in business ▪ Reside in business y of ert Work together Communicate toward the p policies and seeks delivery of ro improvement information P Data Users ▪ Select the best information Communicate information definition and seeks Data Custodians source improvement ideas ▪ Capture, store, retain, ▪ Understand the information and dispose of information accessed per owner requirements ▪ Comply with information ▪ Design technical infrastructure management policies to meet requirements ▪ Create data extract to meet Share information ▪ Ensure security of information specific needs about applications and ▪ Reside in IT / business ▪ Reside in business technology12
  • 13. Governance Model Organization The following table shows the scope of each initiative, based on a tentative composition of the Enterprise Data Governance Council. Master Data Entities al Governance Position & Groups nz Employee Position Items Supplier COA …. Relationships Owner a ROwner Owner er Finance Member Member CPSM Member Member Owner at Member Member ew dg HR Owner Member Informed Informed Member fE yo IT Member Member Member Member Member rt ro pe ▪ Owner – Primary data owner responsible for leading the governance of a particular data entity, also P 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 The CPSM/Finance Data Out of Scope and Governance Project Governance project13
  • 14. Data Governance The following framework defines the data governance capabilities required to implement Organization, chartered with Data Architecture includes administering information enterprise data standards, a management activities, al business information model, provides a responsible nz metadata dictionary and network of dedicated and/or virtual resources to deliver Ra security & privacy information management & er Technology supports common Data governance capabilities at information exchange solutions Architecture ew , workflow and business rules Organization dg functionality and user Policy refers to presentation/ portal to enable information E Data of the enforcement and Tools & management adherence to common data Driven Technology guidelines and y Governance ert standards by business principles for enforcing value Framework Policies, data standards, and op Principles & data governance Pr Process & Practices establishes Standards processes guiding principles outlining how Processes & data governance policies, Practices processes, standards, are Governance created, modified and Metrics Governance Metrics implemented, enabling establishes measures for accurate data to be leveraged monitoring information across the enterprise management performance and actions to continuously improve enterprise data14
  • 15. Road Map al nz Ra at er ew E dg y of p ert P ro15
  • 16. High Level Design Oracle Business Oracle Hyperion Intelligence and Planning Data Warehouse (aka Budget/ al (aka MR) Planning) nz Ra Accountability Accountability er Hierarchy Hierarchy at ew Oracle Hyperion dg Data Relationship Management E of COA Employee Position y ert Position Hierarchies •Accountability op Oracle eBusiness PeopleSoft v8.8 Suite R12.1.1 •Authority (aka ePeople) Pr (aka P2P) Employee Items COA Position Supplier Authority Accountability Hierarchy Hierarchy Hub and Spoke Model16
  • 17. Intakes/Outputs Detail al nz Ra at er ew E dg y of p ert P ro17
  • 18. Design Considerations PeopleSoft vs. Other HR systems Automated feeds vs. Spreadsheets Hierarchy Reconciliation al nz Ra Position and Employee Number Reconciliation Continuing PeopleSoft Conversions er at ew Working Title – eBusiness vs. PeopleSoft dg fE DOFA – Delegation of Financial Authority Dual Responsibility o rty Siblings ro pe P APIs: Position, Employee, Approval Group DIs - Dynamic Inserts Management Reporting Overrides18
  • 19. Three Objectives Objectives of DRM Session al How to use Oracle Hyperion Dataanz Relationship rR ate Management for a single version of truth for company hierarchies. gew Ed of rty pe Discover how Oracle Hyperion Data Relationship Management ro serves as a solution across the enterprise. P Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results.19
  • 20. About Ranzal Founded in 1996, Ranzal has implemented Oracle / Hyperion solutions for over 700 companies (1,000+ projects) al nz One of the largest Hyperion practices in the U.S. with global presence Ra er Oracle / Hyperion Platinum Partner - highest status for an EPM-only partner at Vertical expertise with high-profile clients ew coast to coast g from Ed of infrastructure and training rty Cover all requirements from pre-implementation process design through pe ro for ALL EPM implementation needs P ONLY “One Stop Shop”20
  • 21. One Version of Truth Data Governance Data Ownership Timing and Scope Collapse separate structures into a single maintenance structure Positions al nz Ra Employees er Accounts Responsibility at ew dg Authority E Streamline change management – one place to make changes, one structure to update Created 1 hierarchy from y of ert Multiple systems ro p Multiple versions and subsets of this hierarchy P 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 queries21
  • 22. Proposed Solution al AHS has purchased the Oracle Hyperion product suite that contains Oracle’s Data nz Ra Relationship Management (DRM) module. at er and accuracy within master data assets despite endless changes withinew underlying transactional and DRM is the solution that builds consistency, integrity g the Ed of analytical systems. rtya data model-agnostic master data management ro pe Specifically, the DRM provides P solution built to enable financial and analytical master data management in dynamic, fast-changing business environments.22
  • 23. Data Governance al nz Ra at er ew E dg y of p ert P ro23
  • 24. Data Flows al nz Ra at er ew E dg y of p ert P ro24
  • 25. Hub and Spoke Model Oracle Business Oracle Hyperion Planning Intelligence and Data (aka Budget/ Planning) al Warehouse (aka MR) nz Ra er Accountability Accountability at Hierarchy Hierarchy ew dg Oracle Hyperion Data Relationship E Management of COA Employee rty Position Position pe Hierarchies ro Oracle eBusiness Suite •Accountability PeopleSoft v8.8 (aka R12.1.1 •Authority ePeople) P (aka P2P) Employee Items COA Position Supplier Authority Accountability Hierarchy Hierarchy25
  • 26. Regions al nz Ra at er ew E dg y of p ert P ro26
  • 27. Solution al nzPosition Ra at er ew Employee E dg y of ertFunctional Centre rop P27
  • 28. Across the Enterprise Objectives of DRM Session al nz How to use Oracle Hyperion Data Relationship Management for a a rR single version of truth for company hierarchies. wate eHyperion Data Discover how Oracledg Relationshipty o fE Management serves as a p er the enterprise. solutionoacross Pr Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results.28
  • 29. Expected Benefits Single trusted source of information Reduction in manual maintenance effort al a nz r Higher data integrity (less errors) R ate Increased transparency ofw ge processes Ed of rty Better decision-making ro pe P Reduced operational friction Standard, repeatable processes29
  • 30. Statistics As of October 28, P2P Hierarchy Change Request Status l aof Completed 2011 nz Ra Service Type Sum at er 1-Add Position with Delegation of Financial Authority ew (BAS) 1,145 2-Add Requisitioner (BAS) 3-Change Position Data (BAS) f E dg 1,135 yo 1,063 4-Change Employee Datat(HR) er 1,229 Pr 5-Requests from BASop 85,060 6-Investigated Issues 1,461 7-DOFA Exceptions (BAS) 490 Grand Total 91,58330
  • 31. Across the Enterprise DRM ensures that hierarchies and classifications are aligned across the enterprise. al nz Reports and totals agree across all systems.a rR ate ew dg Dramatic reduction in reconciliation efforts. E f users. yo Confidence with business ert Pr op Agreement among users from different business, units and operating, functions.31
  • 32. Best Practices Objectives of DRM Session al nz How to use Oracle Hyperion Data Relationship Management for a a rR single version of truth for company hierarchies. ate Discover how Oracle Hyperionw ge Data Relationship Management Ed of serves as a solution across the enterprise. rty ro pe P Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results.32
  • 33. Products– DRM Features al nz Key Features to focus on: Ra er Custom rules and validations at ew Configurable exports dg fE Granular security yo ert Read Only User 11.1.2.1+ rop P33
  • 34. Hierarchies Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results. Hierarchies: al nz Tree Structure vs. Warehouse Ra Alternate Hierarchies at er ew E dg y of p ert P ro34
  • 35. Properties Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results. al Properties nz Challenges and solutions Ra Types, Functions, examples at er ew E dg y of p ert P ro35
  • 36. Exports Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results. Exports: Varieties, challenges and solutions al nz Ra at er ew E dg y of p ert P ro36
  • 37. Audit Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results. Leverage product functionality al nz Security Ra Read-only er Granular at ew Audit E dg y of p ert P ro37
  • 38. Best Practices: Re-use Get best practices for implementing Oracle Hyperion Data Relationship Management for maximum results. al Re-use Objects nz Ra Alternate Hierarchies er Property Categories Ex: BAS manager categories at ew dg Properties E of SYS_ properties reused y ert Prefixes Queries ro p P Re-use for common elements Exports System Export, filter38
  • 39. DRM Benefits Single Version Enables organizations to Generate trustworthy insight with high quality master data. al nz Build consistency based on governance standards. Ra er Across the Enterprise Improve TCO with streamlined data maintenance. at w eenterprise applications. dg fE Manage change of business master data across yo Consolidate and rationalize structures across source systems. ert op views with corporate hierarchies. Conform dimensions and validate integrity of attributes and relationships. Pr Synchronize alternate business Best Practices Product Features, Leverage, and Re-use.39
  • 40. Questions? al nz Ra at er ew E dg y of p ert P ro40
  • 41. al nz Enables organizations to … Enables organizations to … Contact Information: Ra Contact Information: Stu Fowler at erBrian Healey Systems Architect ew Principal AHS E dg Ranzal y of Stu.fowler@albertahealthservices.ca bhealey@ranzal.com p ert http://www.albertahealthservices.ca www.ranzal.com P ro41

×