The Experian DRM Journey

Size: px
Start display at page:

Download "The Experian DRM Journey"

Transcription

1 The Experian DRM Journey Oracle Open World InterContinental Ballroom A 23 rd September pm Richard Harwood and Mariana Venter richard.harwood@uk.experian.com mariana.venter@uk.experian.com 2013 Experian Limited. All rights reserved. Experian and the marks used herein are service marks or registered trademarks of Experian Limited. Other products and company names mentioned may be the trademarks of their respective owners. No part of this copyrighted work may be reproduced, modified, or distributed in any form or manner without prior written permission of Experian Limited.

2 2 Presenter introductions 9 years at Experian Richard Harwood Global Transaction Reporting and Data Quality Manager CIMA & ACMA qualified accountant Various finance roles at Experian Currently, responsible for: o Managing Global Chart of Accounts o Driving consistency across the group o Various project engagements o Business Intelligence 2 years at Experian Mariana Venter Global Financial Systems Manager Accounting and Information Technology degree 13 years experience in developing, consulting and implementing Hyperion Essbase, Planning and DRM applications

3 Experian PLC overview Revenue: US$4.7 billion EBIT: US$1.3 billion Market Capitalisation*: c. 12 billion In top 50 of FTSE-100 Employees: c.17,000 Offices in 40 countries Largest markets: US, Brazil, UK Corporate headquarters: Dublin Leading global information services company, providing data and analytical tools to clients around the world 2013 Experian Limited. All rights reserved. For the year ending 31 March 2013 * At 9 May

4 4 Session content The Power of Oracle Hyperion Data Relationship Management at Experian [CON6122] Experian before DRM Initial DRM deployment DRM expansion Current projects Next steps for DRM at Experian DRM benefits Critical success factors

5 5 Experian: October 2008 Non-standard local chart of accounts In-country transaction processing OFA Disparate local financial systems Excelbased local reporting Multiple local bank accounts Outlook Soft Inconsistent processes Highly manual regional/global reporting OSA The key drivers for Global Finance Transformation Project Gemstone

6 6 Project Gemstone (live January 2010) SAPPHIRE Global finance system & optimised processes DIAMOND Global finance shared services RUBY Global finance reporting and analytics Single global instance of Oracle EBS R12 Global Chart of Accounts design & implementation Standard finance processes 3 regional finance shared service centres Global finance shared services organisation Global CR process Hyperion HFM, Planning, Essbase, OBIEE & OBAW Integrated with EBS leveraging DRM & FDQM Global finance CoE Emerald Rationalisation of legal entities Opal Tax efficiency optimisation Glass Functional currency Topaz Order to Cash Optimisation (US)

7 7 System configuration overview January 2010 Oracle EBS R Hyperion Oracle i- Procurement Non Oracle Ledgers Oracle Human Resources Oracle i- Expenses Oracle Payroll Oracle Accounts Payable (AP) Oracle GL Oracle Fixed Assets balances balances FDQM HFM (Consolidation) eliminations Hyperion Reporting (ESSRPT) Oracle Billing CoA metadata DRM Budget/MMC/Forecast Non-Oracle Billing Oracle Accounts Receivable (AR) Oracle Cash Management Hyperion Planning Oracle OBIEE (Transactional Reporting) Hyperion Reporting Systems Daily operations and SSC reporting Month-End / Year-End Reporting etc.

8 8 DRM and the Chart of Accounts change process Business Users 2 days Oracle EBS CoA data master Create / update Standard hierarchies Global Data Quality Team (3) 5 days DRM Additional hierarchies Property setting CoA documentation (after test cycle) Reject Change review board (meets monthly) Approve Downstream applications Downstream applications Downstream applications

9 9 Hyperion Essbase properties set in DRM DRM properties and hierarchies used to populate Essbase metadata o o o o o o o Export to application Alias Consolidation operator UDA Alternative hierarchies Store Data Formula One central place to update for all applications

10 10 Hyperion Planning properties set in DRM All Planning properties are set in DRM: Alias, Account Type, Variance Reporting, Time Balance, Skip, Smart Lists, Data Type etc.

11 Support team and volumes CoA Segment Total Values Hierarchies Company Country Business Unit Cost Centre Natural Account Sub-Account Sub-Analysis Intercompany TOTAL The long run average is 165 CoA changes per month Experian is a dynamic organisation Organic growth, geographical expansion and acquisition Central team of 3 employees Monthly process is c. 20 person days 2013 Experian Limited. All rights reserved. 11

12 Evolution of DRM Oct-08 1.Pre Gemstone Jan-10 2.CoA metadata 3.Customer 4.Automation 5.Current Initiatives No DRM deployment Disparate local CoA No central control Very limited support documentation Difficult group consolidation Longer close times Lack of comparability Inflexible reporting Manual/Excel data collection processes No standardisation 2013 Experian Limited. All rights reserved. DRM deployed for CoA metadata Central CoA control in CoE team Use of DRM to push CoA data and properties to Hyperion systems Standard CoA data across all finance reporting systems Common language/terms Centralised control Standard monthly change process Benefits of DRM hierarchy management 12

13 13 Customer and Account Manager dimensions Sales Insight UK&I (Feb 2010) Add Customer and Account Manager hierarchies Daily loads from UK&I Billing system Sales Insight EMEA & APAC (Nov 2012) Add Customer and Account Managers Daily loads from Oracle AR system for new Customers and Account Managers DRM changes required to support Sales Insight Additional o o o Customer Account Manager Vertical Market Additional alternative hierarchies Additional 120,000 nodes

14 14 Automation Manage daily batches through DRM DRM version used as front end Manage by end user Logs Tracking alerts

15 15 Manage Batches through DRM

16 16 DRM connections today Daily DRM processes Feeds from Oracle AR and Billing Feeds to Oracle AR and Billing Exports to Staging Layer Essbase Studio build cubes Monthly DRM processes Feeds from Oracle EBS Exports to Staging Layer Batch load Hyperion Hyperion

17 17 Evolution of DRM Oct-08 1.Pre Gemstone Jan-10 2.CoA metadata Feb-10 Nov-12 3.Customer Nov-12 4.Automation Sep-13 5.Current initiatives No DRM deployment DRM deployed for CoA metadata DRM deployed for Sales Insight DRM as frontend for batch processes New applications and dimensions Disparate local CoA No central control Very limited support documentation Difficult group consolidation Longer close times Lack of comparability Inflexible reporting Manual/Excel data collection processes No standardisation DRM to push CoA data and properties to Hyperion systems Central CoA control in CoE team Standard CoA data across all finance reporting systems Common language/terms Centralised control Standard monthly change process Benefits of DRM hierarchy management UK&I, EMEA and APAC regions CoA, Customer and Account Managers to Essbase and OBIEE Manage customers from 50+ Billing systems Report revenue by sales team and account manager Report revenue by vertical markets Globally consistent vertical market LoVs DRM batch client User front end COE to manage batch process Live tracking of batch processing Automated alerts Workforce Planning Budget and forecasting by position\employee for UK and NA regions CoA updates to WFP Sales Insight North America Approx. 20+ Billing systems into Oracle AR NA customers and account managers Capital Expenditure Reporting Monthly by project CoA and additional project hierarchy Actuals from Oracle Fixed Asset Register and GL

18 18 What next? CURRENT Oracle EBS Problems with current process Oracle Data Relationship Manual set-up in Oracle EBS Governance (DRG) DRM Elements of dual keying Difficult hierarchy management Front-end workflow for DRM End-users propose changes Timing difficulties in process Approvals routing Downstream applications Downstream applications Downstream applications Inflexible/inefficient what if? Automated value creation FUTURE DRM Benefits of future process New applications Easy what if? modelling CAPEX planning Downstream applications Oracle EBS Downstream applications Simultaneous app. updates Auto upload limit dual-keying OPEX planning Leverage existing dimensions

19 19 Benefits of DRM at Experian Single source of metadata for downstream systems Flexible reporting solutions; calculations & hierarchies Helps to facilitate central governance model and timings Can be administered by non-technical users Drag and drop hierarchies, property settings etc. Version control allows appropriate testing and roll back Ability to leverage existing structures in new applications

20 20 Critical success factors and lessons learned Project DRM implementation Resourcing: Get the right business/consultancy mix Senior stakeholder sponsorship and engagement Excellent intra-team communications Involvement of post implementation support team Technical Use appropriate prefixes to identify application Re-use exports/queries/properties wherever possible Leverage existing hierarchies for new applications Consider EPM version (EBS control, DRG implementation) Governance process & data quality Full CoA documentation think about process driven support rather than a dry list of definitions Set appropriate calendar for metadata changes Empowerment of governance team to own the application

21 21 Questions?

22 22