An Oracle Data Relationship Governance Journey ICAP Success Story Simon Leggate Jerome Marcq

Transcription

1 An Oracle Data Relationship Governance Journey ICAP Success Story Simon Leggate Jerome Marcq September 9 th 2014

2 Agenda The business drivers DRM/DRG implementation approach Using DRM to manage change Complex governance in a global organisation Lessons learnt & leading practices Q & A

3 But first, some introductions!

4 From ICAP Simon Leggate Systems Administrator Simon has 12 years experience working with the Hyperion product set and has been at ICAP for the last 4 years. He began as an Hyperion Enterprise administrator and now has a detailed understanding of HFM, FDM and Financial Reports. Simon s in depth understanding of ICAP s finance community, processes and challenges made him the ideal person to lead the DRM/DRG project in ICAP #Photo# ICAP plc is a leading markets operator and provider of post trade risk and information services. ICAP is an integral part of the global financial system, providing electronic execution, broking, risk mitigation, messaging and information services to wholesale market participants. The company is listed on the London Stock Exchange and is a constituent of the FTSE 250 Index.

5 From Seismi Jerome Marcq Director, Technology Jerome began his career working in business process management and integration. He has applied this detailed understanding of the importance of efficient processes to become a leader and innovator in financial systems integration and master data management. He complements his expertise in business process with a detailed understanding of a wide range of financial technologies and applications. #Photo# Seismi is a professional services company that specialises in delivering fully integrated financial solutions to corporate clients. Seismi s implementations are underpinned by efficient master data management leading to flexible, robust and automated solutions. Seismi provide consultancy, infrastructure, training and support services and have extensive product expertise in the Oracle-Hyperion suite.

6 Context ICAP s Financial System Roadmap ICAP initiated a comprehensive financial transformation programme for a number of reasons. We wanted to: update our Oracle Financials system which was end of life; refresh our chart of accounts to enhance reporting and analysis capabilities; consolidate our reporting tools; improve our master data management process; improve the end-to-end visibility of data; and increase our ability to automate data loads between applications. DRM and DRG were key components of the new toolset to help deliver against these objectives.

7 Agenda The business drivers DRM/DRG implementation approach Using DRM to manage change Complex governance in a global organisation Lessons learnt & leading practices Q & A

8 Master Data Management in ICAP Before DRM

9 Master Data Management in ICAP Before DRM Inefficient. Time consuming. Difficult to manage. Complex controls.

10 Master Data Management Objectives Efficient Transparent Robust Optimise Month-End Close - Through pro-active governance process Standardised Reports - Standard reports across multiple entities charts platforms Embedded controls - Reduce business risk by improving master data controls Empower Master Data Owners To make their changes within defined boundaries. Modeling - Understand changes before implementation Acquisition- Rapidly deploy standard EPM solutions to new acquisitions Standardise and Optimise Processes reduce complexity and clarify master data management processes Coherence Across Multiple Reporting Views - Enforce coherence of multiple, complex views (financial, management, operational etc.) Data Transparency - the ability to understand the transactions that underpin reported numbers Compliance - Meet audit & regulatory requirements Minimise Failure Points through enforcing consistency across platforms and interfaces Automation - Zero Touch or Lights out ETL process

11 Agenda The business drivers DRM/DRG implementation approach Using DRM to manage change Complex governance in a global organisation Lessons learnt & leading practices Q & A

12 Approach The roadmap was designed to help the transition from old financial systems to new with minimum impact to business operations.

13 Agenda The business drivers DRM/DRG implementation approach Using DRM to manage change Complex governance in a global organisation Lessons learnt & leading practices Q & A

14

15

16 Change Management Solution

17 Master Data Management Objectives Efficient Transparent Robust Optimise Month-End Close - Through pro-active governance process Standardised Reports - Standard reports across multiple entities charts platforms Embedded controls - Reduce business risk by improving master data controls Empower Master Data Owners To make their changes within defined boundaries. Modeling - Understand changes before implementation Acquisition - Rapidly deploy standard EPM solutions to new acquisitions Standardise and Optimise Processes reduce complexity and clarify master data management processes Data Transparency - the ability to understand the transactions that underpin reported number Minimise Failure Points through enforcing consistency across platforms and interfaces Coherence Across Multiple Reporting Views - Enforce coherence of multiple, complex views (financial, management, operational etc.) Compliance - Meet audit & regulatory requirements Automation - Zero Touch or Lights out ETL process Data Relationship Governance specific objectives

18 Agenda The business drivers DRM/DRG implementation approach Using DRM to manage change Complex governance in a global organisation Lessons learnt & leading practices Q & A

19 Statistics Chart of account with 8 segments. Multiple reporting hierarchies based on the chart of account segments. Approximately 50,000 nodes per version. More than 120 DRM users including 80 active DRG users around the world. 19 regional groups with local ownership of branches of hierarchies. An average of over 200 DRG requests a month.

20 Data Relationship Governance - Overview DRG coordinates and standardises master data workflow activities: Submit Business users initiate a change request with one or multiple items. Enrich Defined users modify items within a request by populating or modifying attributes. Approve Defined user(s) from one or multiple groups must sign off the request. The change is applied to the appropriate version. Commit Please note Any user at any stage can push back to previous stages, reject or add a comment against the request.

21 Standard Request Submit Simple approval path. Submitter does not always know the final node name on submission. Approve Required justification. Commit Validation on names, descriptions and attributes. All requests applied to the UAT Version.

22 Multiple reporting views New Accounts Submit Approve Simple approval path. US Statutory Additional steps to insert all new leaf nodes to multiple reporting hierarchies. US Regulatory Final Validation Commit Multiple validations at each step and one final step to re-run all validations.

23 Federated Hierarchies - Cost Centres Submit Submit Submit Regional submitters only have access to their section of the hierarchy Approve Approve Approve Approve Requests are then routed to the appropriate regional approvers Head Count All requests are then approved by Global Finance. By Product Final Validation Commit

24 High Priority Requests - IT Projects Submit Limited approval path. Approve New leaf IT projects are created directly in Production, bypassing monthly master data cycle. Automated process to copy new IT Projects from Production to UAT every night. Commit Other projects are maintained through standard processes.

25 Additional External Documentation - Companies Submit Approve Local Statutory Companies follow a standard approval process and can be inserted to reporting hierarchies. Final Validation Commit All companies must be linked to legal documentation on Sharepoint with all regulatory information.

26 Master Data Management Objectives Efficient Transparent Robust Optimise Month-End Close - Through pro-active governance process Standardised Reports - Standard reports across multiple entities charts platforms Embedded controls - Reduce business risk by improving master data controls Empower Master Data Owners To make their changes within defined boundaries. Modeling - Understand changes before implementation Acquisition - Rapidly deploy standard EPM solutions to new acquisitions Standardise and Optimise Processes reduce complexity and clarify master data management processes Data Transparency - the ability to understand the transactions that underpin reported numbers Minimise Failure Points through enforcing consistency across platforms and interfaces Coherence Across Multiple Reporting Views - Enforce coherence of multiple, complex views (financial, management, operational etc.) Compliance - Meet audit & regulatory requirements Automation - Zero Touch or Lights out ETL process

27 Agenda The business drivers DRM/DRG implementation approach Using DRM to manage change Complex governance in a global organisation Lessons learnt & leading practices Q & A

28 DRG Successful Practices Upgrade DRM Upgrading DRM in isolation with a new instance of Shared Services allowed us to deliver the benefits of DRG without requiring the upgrade of the full EPM suite. Encouraging business buy in to workflows By involving the business in very early testing and welcoming suggestions and requests, we encouraged buy in from key business users early in the implementation phase. This greatly enhanced the quality of the workflows and adoption by business users. Detailed and thorough test scripts Creating detailed test scripts going through as many different possible behaviour as possible greatly helped in delivering high quality workflows.

29 Challenge Lessons Learnt - DRM Lesson Learnt Not a backend tool DRM is sometimes perceived as a back end integration tool instead of a front end tool for Finance users. Business value To get the best business value out of DRM, get business analysts with experience of what the tool can deliver and your finance users together. Silo-ed development Although silo-ed development of EPM applications can appear more effective, it increases difficulty of adding governance and data integration afterwards and decreases quality of the overall solution. Integrated development EPM solutions designed and delivered with governance and data integration produce more robust and better quality solutions (e.g. GAA cubes and HPCM applications). Conventions Different application and users favour different conventions (prefix vs. suffix, separators, & vs. and ). Although DRM supports these differences easily, they still generate some confusion in reports. Standard convention Taking the time to define a standard set of conventions for name and description is easy and best done at the start of the program.

30 Challenge Lessons Learnt - DRG Lesson Learnt Fast Changing Requirements As business users got to know DRG, they increasingly added and adapted workflow requirements and expected fast turnaround. Continuous improvement Workflows are not static and will change as users and the organization changes. Independent tasks Time invested in creating separate tasks per workflow reduces complexity and risk around modifying workflows at a later date. Complex Requests Complex requests with multiple limb and leaves are slow and difficult to process. Either all items are approved or none. Prefer multiple simple requests By using multiple simple requests, users can collaborate in restructuring a hierarchy, take advantage of the copy request option, see the result in the UAT version as restructuring progresses and discuss and reject individual items without blocking the full restructuration. Validation design Some complex validations that can only run as batch in the classic interface can be run in real time in DRG. Validations design DRM validations must be designed from the start to be re-used in DRG.

31 Oracle DRG, coupled with Oracle DRM, has enabled us to control the release of master data changes to our production environment. We can test the impact of our master data changes on numbers in our preproduction environment to ensure they have the required affect. We can then release these changes using a controlled and automated process to our production environment. Manual activities have been dramatically reduced, rekeying has been eliminated and the inbuilt controls and validations have helped speed up the master data process. David Allen, Financial Systems Manager at ICAP

32 Oracle DRG, coupled with Oracle DRM, has enabled us to control the release of master data changes to our production environment. We can test the impact of our master data changes on numbers in our pre-production environment to ensure they have the required affect. We can then release these changes using a controlled and automated process to our production environment. Manual activities have been dramatically reduced, rekeying has been eliminated and the inbuilt controls and validations have helped speed up the master data process. David Allen, Financial Systems Manager at ICAP Q&A Simon Leggate simon.leggate@icap.com Jerome Marcq jerome.marcq@seismi.net